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.
Metrics
Affected Vendors & Products
Advisories
| Source | ID | Title |
|---|---|---|
EUVD |
EUVD-2022-2908 | 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. |
Github GHSA |
GHSA-742j-jcfr-23w3 | Insufficient Session Expiration in Jenkins |
Fixes
Solution
No solution given by the vendor.
Workaround
No workaround given by the vendor.
References
History
No history.
Status: PUBLISHED
Assigner: jenkins
Published:
Updated: 2024-08-05T03:07:18.205Z
Reserved: 2019-04-10T00:00:00
Link: CVE-2019-1003049
No data.
Status : Modified
Published: 2019-04-10T21:29:01.480
Modified: 2024-11-21T04:17:48.607
Link: CVE-2019-1003049
OpenCVE Enrichment
No data.
EUVD
Github GHSA