CVE-2018-1000013: CSRF
First published: Tue Jan 23 2018(Updated: )
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.
Credit: cve@mitre.org cve@mitre.org
| Affected Software | Affected Version | How to fix |
|---|---|---|
| Jenkins Release | <=2.9 | |
| maven/org.jenkins-ci.plugins:release | <2.10 | 2.10 |
| <=2.9 |
Never miss a vulnerability like this again
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
Reference Links
Frequently Asked Questions
What is the severity of CVE-2018-1000013?
CVE-2018-1000013 is considered a medium severity vulnerability due to its potential exploitation for unauthorized actions.
How do I fix CVE-2018-1000013?
To mitigate CVE-2018-1000013, upgrade the Jenkins Release Plugin to version 2.10 or later.
What type of vulnerability is CVE-2018-1000013?
CVE-2018-1000013 is a Cross-Site Request Forgery (CSRF) vulnerability.
Which versions are affected by CVE-2018-1000013?
CVE-2018-1000013 affects Jenkins Release Plugin versions up to 2.9 inclusive.
Who is affected by CVE-2018-1000013?
Any user running Jenkins Release Plugin version 2.9 or earlier is at risk of CVE-2018-1000013.
- collector/nvd-index
- agent/type
- collector/github-advisory-latest
- source/GitHub
- alias/GHSA-j2h6-j34w-g5vp
- alias/CVE-2018-1000013
- agent/software-canonical-lookup
- agent/weakness
- agent/severity
- agent/references
- agent/description
- agent/author
- agent/softwarecombine
- collector/nvd-cve
- source/NVD
- collector/mitre-cve
- source/MITRE
- agent/last-modified-date
- agent/first-publish-date
- agent/event
- agent/trending
- agent/tags
- agent/source
- vendor/jenkins
- canonical/jenkins release
- version/jenkins release/2.9
- package-manager/maven