CVE-2018-1000013 json
CSRF vulnerability in Jenkins Release plugin
published 8y ago modified 4mo ago also GHSA-j2h6-j34w-g5vp , EUVD-2022-4258
- cvss
- 8.8
- version 3.0, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 1.0%
- EPSS 1.0% chance of exploitation in 30 days, percentile 63%
- public exploits
- 0
- none known
Summary
Jenkins Release Plugin 2.9 and earlier did not require form submissions to be submitted via POST, resulting in a CSRF vulnerability allowing attackers to trigger release builds.
Patch / fix
- maven org.jenkins-ci.plugins:release 2.10
Is CVE-2018-1000013 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.02% chance of exploitation in the next 30 days, higher than 63% of all scored CVEs (FIRST EPSS, 2026-11-09).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 3.0 | 8.8 | CVSS:3.0/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.0 | 8.8 | CVSS:3.0/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:release | <2.10 |
2.10 |
Classification
- Weakness
-
- CWE-352 Cross-Site Request Forgery
References
-
jenkins.io
/security/advisory/2018-01-22/
vendor-advisory
-
securityfocus.com
/bid/102834
vdb-entry, web, third-party-advisory
-
nvd.nist.gov
/vuln/detail/CVE-2018-1000013
advisory
-
jenkins.io
/security/advisory/2018-01-22
web
Sources
- CVE List CVE-2018-1000013
- GitHub Advisory GHSA-j2h6-j34w-g5vp
- NVD CVE-2018-1000013
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.