Users who cached their CLI authentication before Jenkins was updated to 2.150.2 and newer, or 2.160 and newer, would remain authenticated in Jenkins 2.171 and earlier and Jenkins LTS 2.164.1 and earlier, because the fix for CVE-2019-1003004 in these releases did not reject existing remoting-based CLI authentication caches.
References
Link | Resource |
---|---|
https://jenkins.io/security/advisory/2019-04-10/#SECURITY-1289 | Vendor Advisory |
http://www.securityfocus.com/bid/107901 | Broken Link |
https://access.redhat.com/errata/RHBA-2019:1605 | Third Party Advisory |
https://www.oracle.com/security-alerts/cpuapr2022.html | Patch Third Party Advisory |
Configurations
Configuration 1 (hide)
|
Configuration 2 (hide)
|
Configuration 3 (hide)
|
Configuration 4 (hide)
|
Information
Published : 2019-04-10 14:29
Updated : 2022-06-13 11:36
NVD link : CVE-2019-1003049
Mitre link : CVE-2019-1003049
JSON object : View
CWE
CWE-613
Insufficient Session Expiration
Products Affected
redhat
- openshift_container_platform
oracle
- communications_cloud_native_core_automated_test_suite
jenkins
- jenkins