Insufficient Session Expiration in Jenkins
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.
01
describes (1)
Related CVEs.
| ID | severity | exploitable | ||
|---|---|---|---|---|
| CVE-2019-1003049US | high8.1 | — | ||
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 L… | ||||
02
references
External citations — patches, advisories, analysis.
- http://www.securityfocus.com/bid/107901WEB
- https://access.redhat.com/errata/RHBA-2019:1605WEB
- https://github.com/jenkinsci/jenkinsPACKAGE
- https://github.com/jenkinsci/jenkins/commit/0eeaa087aac192fb39f52928be5a5bbf16627ea6WEB
- https://jenkins.io/security/advisory/2019-04-10/#SECURITY-1289WEB
- https://nvd.nist.gov/vuln/detail/CVE-2019-1003049ADVISORY
- https://www.oracle.com/security-alerts/cpuapr2022.htmlWEB
scry
Advisories like this name the exposed products attackers go after on your perimeter. See what is exposed on your perimeter with a free passive scan.
Free scan