CVE-2019-1003049 json
Insufficient Session Expiration in Jenkins
published 2019-04-10 7 y ago modified 2026-06-17 4 mo ago also GHSA-742j-jcfr-23w3 , EUVD-2022-2908
- cvss
- 8.1
- version 3.1, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 2.1%
- EPSS 2.1% chance of exploitation in 30 days, percentile 81%
- public exploits
- 0
- none known
Summary
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.
Patch / fix
- maven org.jenkins-ci.main:jenkins-core 2.164.2, 2.172
- cri-o openshift 3.11 1.11.14-1.rhaos3.11.gitd56660e.el7
- jenkins openshift 3.11 2.164.2.1555422716-1.el7
- prometheus openshift 3.11 3.11.117-1.git.1.f52d417.el7
- jenkins-2-plugins openshift 3.11 3.11.1559667994-1.el7
- openshift-ansible openshift 3.11 3.11.123-1.git.0.db681ba.el7
- openshift-ansible-test openshift 3.11 3.11.123-1.git.0.db681ba.el7
- openshift-ansible-roles openshift 3.11 3.11.123-1.git.0.db681ba.el7
- prometheus-alertmanager openshift 3.11 3.11.117-1.git.1.207ef35.el7
red hat advisories RHBA-2019:1605
- jenkins Alpine 3.9 2.164.2-r0
alpine advisories ALPINE-CVE-2019-1003049
Alpine secdb © Alpine Linux, from https://secdb.alpinelinux.org via OSV; changed: normalised to fixed package versions per release. CC BY-SA 4.0
- jenkins Arch Linux 2.172-1
arch linux advisories AVG-948
Vendor advisories
What the vendors themselves say about their products: affected, fixed or not affected, and what to do.
red hat product security vex CVE-2019-1003049 updated cvss 5.0
jenkins: Jenkins accepted cached legacy CLI authentication
-
Red Hat OpenShift Container Platform 3.4 jenkins Red Hat OpenShift Container Platform 3.5 jenkinsaffected: no fix planned “Out of support scope”
-
Red Hat OpenShift Container Platform 3.6 jenkins Red Hat OpenShift Container Platform 3.7 jenkins Red Hat OpenShift Container Platform 3.9 jenkins Red Hat OpenShift Container Platform 3.10 jenkinsaffected: no fix planned “Will not fix”
-
Red Hat OpenShift Container Platform 3.11 jenkins 2.164.2.1555422716-1.el7, jenkins-2-plugins 3.11.1559667994-1.el7, prometheus 3.11.117-1.git.1.f52d417.el7, cri-o 1.11.14-1.rhaos3.11.gitd56660e.el7, openshift-ansible 3.11.123-1.git.0.db681ba.el7, openshift-ansible-test 3.11.123-1.git.0.db681ba.el7, +19 morefixed: vendor fix RHBA-2019:1605
-
Red Hat OpenShift Container Platform 4 jenkinsnot affected: vulnerable code not present
Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf
Exploit prediction
2.11% chance of exploitation in the next 30 days, higher than 81% of all scored CVEs (FIRST EPSS, 2026-11-08).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 3.1 | 8.1 | CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H |
| NVD | 2.0 | 6.8 | AV:N/AC:M/Au:N/C:P/I:P/A:P |
| GitHub | 3.1 | 8.1 | CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H |
Affected packages
| ecosystem | package | affected | fixed in |
|---|---|---|---|
| maven | org.jenkins-ci.main:jenkins-core | <2.164.2 >=2.165, <2.172 |
2.164.2 2.172 |
Affected products
- Jenkins project Jenkins
Classification
- Weakness
-
- CWE-613 DEPRECATED: Insufficient Session Expiration
- Technology feeds
References
-
oracle.com
/security-alerts/cpuapr2022.html
web, patch, third-party-advisory
-
github.com
/jenkinsci/jenkins/commit/0eeaa087aac192fb39f52928be5a5bbf16627ea6
web
-
access.redhat.com
/errata/RHBA-2019:1605
vendor-advisory, web, third-party-advisory
-
jenkins.io
/security/advisory/2019-04-10/#SECURITY-1289
web, vendor-advisory
-
securityfocus.com
/bid/107901
vdb-entry, web, broken-link
-
nvd.nist.gov
/vuln/detail/CVE-2019-1003049
advisory
-
github.com
/jenkinsci/jenkins
package
Sources
- CVE List CVE-2019-1003049
- GitHub Advisory GHSA-742j-jcfr-23w3
- NVD CVE-2019-1003049
Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.