CVE-2019-10437 json
Jenkins CRX Content Package Deployer Plugin subject to Cross-Site Request Forgery
published 2019-10-16 7 y ago modified 2026-06-17 4 mo ago also GHSA-62fp-j75q-mqhc , EUVD-2022-2687
- cvss
- 8.8
- version 3.1, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.9%
- EPSS 0.9% chance of exploitation in 30 days, percentile 58%
- public exploits
- 0
- none known
Summary
A cross-site request forgery vulnerability in Jenkins CRX Content Package Deployer Plugin 1.8.1 and earlier allowed attackers 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
Exploit prediction
0.86% chance of exploitation in the next 30 days, higher than 58% of all scored CVEs (FIRST EPSS, 2026-11-08).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 3.1 | 8.8 | CVSS:3.1/AV:N/AC:L/PR:N/UI:R/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.8 | CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H |
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
- Weakness
-
- CWE-352 Cross-Site Request Forgery
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-10437
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-10437
- GitHub Advisory GHSA-62fp-j75q-mqhc
- NVD CVE-2019-10437
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.