CVE-2019-1003049 — Users who cached their CLI authentication before Jenkins was updated to 2

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 existi

01What is this vulnerability?

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.

02Affected products

Vendor	Product	Versions
Jenkins project	Jenkins	2.171 and earlier, LTS 2.164.1 and earlier

03Active exploitation status

Not currently listed on the CISA Known Exploited Vulnerabilities (KEV) catalog. EPSS is the best forward-looking signal — see the EPSS row above.

04Recommended remediation

• Patch to a fixed version listed in the vendor advisory (see references below).
• Mitigate with WAF rules, network egress filters, or feature flags where the patch is not yet available.
• Hunt historical logs for exploitation indicators — see Detection signatures below.

05Technical details

For the full vendor write-up, exploit chains, and reference implementations, see the references list in section 09.

06Detection signatures

Ask SARA in chat to draft a starting detection for this CVE in your stack of choice.

07Related CVEs

08Timeline

• Published: 2019-04-10T20:12:29.000Z
• Last modified: 2024-08-05T03:07:18.205Z

09References

• www.securityfocus.com — http://www.securityfocus.com/bid/107901
• access.redhat.com — https://access.redhat.com/errata/RHBA-2019:1605
• www.oracle.com — https://www.oracle.com/security-alerts/cpuapr2022.html
• jenkins.io — https://jenkins.io/security/advisory/2019-04-10/#SECURITY-1289