CVE-2018-1000013 CSRF vulnerability in Jenkins Release plugin
Attackers can trigger unauthorized release builds in Jenkins via CSRF due to missing POST method enforcement in the Release Plugin.
- Exploited in the wild
- Not known
- Login needed
- Not needed
- Attackable
- Over the internet
- Victim action needed
- A user has to click or open something
- Fix
- Available
What is CVE-2018-1000013?
CVE-2018-1000013 is a high-severity vulnerability in n/a, published on 23 Jan 2018. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Official description
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.
Weakness: CWE-352
Which versions are affected by CVE-2018-1000013?
2 open source packages ship an affected version, including org.jenkins-ci.plugins:release. It affects 1 product.
| Package | Affected | Fixed in |
|---|---|---|
org.jenkins-ci.plugins:release Maven | All versions | 2.10 |
org.jenkins-ci.plugins:release Maven | All versions | 2.10 |
Products include Jenkins Release.
How do I fix CVE-2018-1000013?
Upgrade org.jenkins-ci.plugins:release to 2.10 or later.
Is CVE-2018-1000013 being exploited?
There is no known exploitation of CVE-2018-1000013 in the wild and no public exploit code.
Other vulnerabilities in n/a
Sources
Also known as GHSA-j2h6-j34w-g5vp.