CVE-2019-10438 json
Jenkins CRX Content Package Deployer Plugin subject to Missing Authorization
published 7y ago modified 4mo ago also GHSA-jww4-2793-9gmg , EUVD-2022-4454
- cvss
- 6.5
- version 3.1, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 1.0%
- EPSS 1.0% chance of exploitation in 30 days, percentile 64%
- public exploits
- 0
- none known
Summary
A missing permission check in Jenkins CRX Content Package Deployer Plugin 1.8.1 and earlier allowed attackers with Overall/Read permission to connect to an attacker-specified URL using attacker-specified credentials IDs obtained through another method, capturing credentials stored in Jenkins.
Patch / fix
- maven org.jenkins-ci.plugins:crx-content-package-deployer 1.9
Is CVE-2019-10438 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 FencerExploit prediction
1.03% chance of exploitation in the next 30 days, higher than 64% of all scored CVEs (FIRST EPSS, 2026-11-09).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 3.1 | 6.5 | CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N |
| NVD | 2.0 | 4.0 | AV:N/AC:L/Au:S/C:P/I:N/A:N |
| GitHub | 3.1 | 6.5 | CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N |
Affected packages
| ecosystem | package | affected | fixed in |
|---|---|---|---|
| maven | org.jenkins-ci.plugins:crx-content-package-deployer | <1.9 |
1.9 |
Affected products
- Jenkins project Jenkins CRX Content Package Deployer Plugin
Classification
References
-
github.com
/jenkinsci/crx-content-package-deployer-plugin/commit/1313c422170a064dab0f9359324ff27e30a9f4a5
web
- jenkins.io /security/advisory/2019-10-16/#SECURITY-1006%20%281%29
-
nvd.nist.gov
/vuln/detail/CVE-2019-10438
advisory
-
github.com
/jenkinsci/crx-content-package-deployer-plugin
web
-
jenkins.io
/security/advisory/2019-10-16/#SECURITY-1006%20(1)
web
Sources
- CVE List CVE-2019-10438
- GitHub Advisory GHSA-jww4-2793-9gmg
- NVD CVE-2019-10438
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.