CVE-2019-10405 json
Exposure of Sensitive Information to an Unauthorized Actor in Jenkins
published 7y ago modified 4mo ago also GHSA-47wc-p5cp-w7pw , EUVD-2022-2334
- cvss
- 5.4
- version 3.1, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 65.3%
- EPSS 65.3% chance of exploitation in 30 days, percentile 99.2%
- public exploits
- 0
- none known, plus a Nuclei check
Summary
Jenkins 2.196 and earlier, LTS 2.176.3 and earlier printed the value of the "Cookie" HTTP request header on the /whoAmI/ URL, allowing attackers exploiting another XSS vulnerability to obtain the HTTP session cookie despite it being marked HttpOnly.
Patch / fix
- maven org.jenkins-ci.main:jenkins-core 2.176.4, 2.197
- jenkins openshift 4.3 2.204.1.1578490170-1.el7
- openshift openshift 4.3 4.3.0-202001131753.git.0.0aee6a8.el7
- openshift openshift 4.3 4.3.0-202001131753.git.0.0aee6a8.el8
- openshift-hyperkube openshift 4.3 4.3.0-202001131753.git.0.0aee6a8.el7
- openshift-hyperkube openshift 4.3 4.3.0-202001131753.git.0.0aee6a8.el8
- jenkins openshift 3.11 2.176.4.1578402941-1.el7
red hat advisories RHBA-2020:0063RHBA-2020:0017
- jenkins Alpine 3.10 2.199-r0
alpine advisories ALPINE-CVE-2019-10405
Alpine secdb © Alpine Linux, from https://secdb.alpinelinux.org via OSV; changed: normalised to fixed package versions per release. CC BY-SA 4.0
Is CVE-2019-10405 in your dependencies? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.
Check with FencerVendor 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-10405 updated cvss 4.4
jenkins: Diagnostic web page exposed Cookie HTTP header
-
Red Hat OpenShift Container Platform 3.9 jenkins Red Hat OpenShift Container Platform 3.10 jenkinsaffected: no fix planned “Out of support scope”
-
Red Hat OpenShift Container Platform 3.11 jenkins 2.176.4.1578402941-1.el7fixed: vendor fix RHBA-2020:0017
-
Red Hat OpenShift Container Platform 4.3 jenkins 2.204.1.1578490170-1.el7fixed: vendor fix RHBA-2020:0063
-
Red Hat OpenShift Container Platform 3.11 jenkins-2-plugins 3.11.1577428005-1.el7, prometheus 3.11.161-1.git.1.3f7d286.el7, openshift-kuryr 3.11.161-1.git.1.33697e5.el7, atomic-openshift 3.11.161-1.git.0.4ccbe25.el7, openshift-ansible 3.11.161-2.git.5.029d67f.el7, openshift-kuryr-cni 3.11.161-1.git.1.33697e5.el7, +35 more Red Hat OpenShift Container Platform 4.3 jq 1.6-2.el7, apb 2.0.3-2.el7, faq 0.0.6-4.el7, conmon 2.0.8-2.el7, conmon 2.0.9-1.el8, fb303 0.9.1-15.el7, +206 morenot 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
65.29% chance of exploitation in the next 30 days, higher than 99.2% of all scored CVEs (FIRST EPSS, 2026-11-09).
Exploits and checks
- Nuclei template Jenkins <=2.196 - Cookie Exposure nuclei detection template
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 3.1 | 5.4 | CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:N |
| NVD | 2.0 | 3.5 | AV:N/AC:M/Au:S/C:N/I:P/A:N |
| GitHub | 3.1 | 4.3 | CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N |
Affected packages
| ecosystem | package | affected | fixed in |
|---|---|---|---|
| maven | org.jenkins-ci.main:jenkins-core | <2.176.4 >=2.177, <2.197 |
2.176.4 2.197 |
Affected products
- Jenkins project Jenkins
Classification
- Weakness
- Technology feeds
References
-
github.com
/jenkinsci/jenkins/commit/560ee832b41814660c5632ea36ad1a1c977177bf
web
-
jenkins.io
/security/advisory/2019-09-25/#SECURITY-1505
web, vendor-advisory
-
openwall.com
/lists/oss-security/2019/09/25/3
mailing-list, web, third-party-advisory
-
nvd.nist.gov
/vuln/detail/CVE-2019-10405
advisory
Sources
- CVE List CVE-2019-10405
- GitHub Advisory GHSA-47wc-p5cp-w7pw
- NVD CVE-2019-10405
Fencer Intel 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.