CVE-2019-1003049
published 2019-04-10CVE-2019-1003049: 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…
PriorityP346high8.1CVSS 3.1
AVNACHPRNUINSUCHIHAH
EPSS
2.11%
79.7th percentile
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.
Affected
7 ranges
| Vendor | Product | Version range | Fixed in |
|---|---|---|---|
| jenkins | jenkins | <= 2.164.1 | — |
| jenkins | jenkins | <= 2.171 | — |
| jenkins | jenkins_core | — | — |
| jenkins | jenkins_lts | — | — |
| jenkins | jenkins_weekly | — | — |
| oracle | communications_cloud_native_core_automated_test_suite | — | — |
| redhat | openshift_container_platform | — | — |
CVSS provenance
nvdv3.18.1HIGHCVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H
nvdv2.06.8MEDIUMAV:N/AC:M/Au:N/C:P/I:P/A:P
ghsa7.2HIGH
osv7.2HIGH
vendor_redhat7.2HIGH
Stop checking back — get the weekly exploitation signal.
Every Monday: what got weaponized or added to CISA KEV in the last seven days — each CVE cross-linked to its PoC, Nuclei template, and detection rule. Free, one email a week, unsubscribe in one click.
OSV
Insufficient Session Expiration in Jenkins
osv·2022-05-13·CVSS 7.2
CVE-2019-1003049 [HIGH] Insufficient Session Expiration in Jenkins
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.
GHSA
Insufficient Session Expiration in Jenkins
ghsa·2022-05-13·CVSS 7.2
CVE-2019-1003049 [HIGH] CWE-613 Insufficient Session Expiration in Jenkins
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.
Red Hat
jenkins: Jenkins accepted cached legacy CLI authentication
vendor_redhat·2019-04-10·CVSS 7.2
CVE-2019-1003049 [HIGH] CWE-287 jenkins: Jenkins accepted cached legacy CLI authentication
jenkins: Jenkins accepted cached legacy CLI authentication
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.
Package: jenkins (Red Hat OpenShift Container Platform 3.10) - Will not fix
Package: jenkins (Red Hat OpenShift Container Platform 3.4) - Out of support scope
Package: jenkins (Red Hat OpenShift Container Platform 3.5) - Out of support scope
Package: jenkins (Red Hat OpenShift Container Platform 3.6) - Will not fix
Package: jenkins (Red Hat OpenShift Container Platform 3.7) - Will not fix
Package: jenkins
Jenkins
Jenkins Security Advisory 2019-04-10
vendor_jenkins·2019-04-10·CVSS 8.1
CVE-2019-1003049 [HIGH] Jenkins Security Advisory 2019-04-10
Title: Jenkins Security Advisory 2019-04-10
Jenkins Security Advisory 2019-04-10
Jenkins Security Home
For Administrators
Overview
Terminology
Vulnerabilities and Scoring
Security Advisories
Security Issues
Advisory Schedule
Vulnerabilities in Plugins
How We Fix Security Issues
For Reporters
Reporting Vulnerabilities
Jenkins CNA
For Maintainers
Overview
Vulnerabilities in Plugins
Jenkins Security Team
About
Contributions
This advisory announces vulnerabilities in the following Jenkins deliverables:
Jenkins (core)
Descriptions
Jenkins accepted cached legacy CLI authentication
SECURITY-1289
/
CVE-2019-1003049
Severity (CVSS):
Medium
Description:
The fix for SECURITY-901 in J
No detection rules found.
No public exploits indexed.
Bugzilla
CVE-2019-1003049 jenkins: Jenkins accepted cached legacy CLI authentication
bugzilla·2019-04-15·CVSS 7.2
CVE-2019-1003049 [HIGH] CVE-2019-1003049 jenkins: Jenkins accepted cached legacy CLI authentication
CVE-2019-1003049 jenkins: Jenkins accepted cached legacy CLI authentication
The fix for SECURITY-901/CVE-2019-1003004 in Jenkins 2.150.2 and 2.160 did not reject existing remoting-based CLI authentication caches.
This means that users who cached their CLI authentication before Jenkins was updated to 2.150.2 and newer, or 2.160 and newer, would remain authenticated.
Support for the remoting-based CLI was dropped in Jenkins 2.165, so newer weekly releases are not affected. Jenkins 2.164.2 no longer supports legacy CLI authentication caches from before 2.150.2/2.160, and these users will be considered logged out.
External References:
https://jenkins.io/security/advisory/2019-04-10/#SECURITY-1289
Discussion:
Created jenkins tracking bugs for this issue:
Affects: fedora-all [bug 169970
Bugzilla
CVE-2019-1003049 jenkins: Jenkins accepted cached legacy CLI authentication [fedora-all]
bugzilla·2019-04-15·CVSS 8.1
CVE-2019-1003049 [HIGH] CVE-2019-1003049 jenkins: Jenkins accepted cached legacy CLI authentication [fedora-all]
CVE-2019-1003049 jenkins: Jenkins accepted cached legacy CLI authentication [fedora-all]
This is an automatically created tracking bug! It was created to ensure
that one or more security vulnerabilities are fixed in affected versions
of fedora-all.
For comments that are specific to the vulnerability please use bugs filed
against the "Security Response" product referenced in the "Blocks" field.
For more information see:
http://fedoraproject.org/wiki/Security/TrackingBugs
When submitting as an update, use the fedpkg template provided in the next
comment(s). This will include the bug IDs of this tracking bug as well as
the relevant top-level CVE bugs.
Please also mention the CVE IDs being fixed in the RPM changelog and the
fedpkg commit message.
NOTE: this issue affects multiple support
http://www.securityfocus.com/bid/107901https://access.redhat.com/errata/RHBA-2019:1605https://jenkins.io/security/advisory/2019-04-10/#SECURITY-1289https://www.oracle.com/security-alerts/cpuapr2022.htmlhttp://www.securityfocus.com/bid/107901https://access.redhat.com/errata/RHBA-2019:1605https://jenkins.io/security/advisory/2019-04-10/#SECURITY-1289https://www.oracle.com/security-alerts/cpuapr2022.html
2019-04-10
Published