CVE-2018-1000013: CSRF
Published 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.
Affected Software
2 affected componentsFixes available
maven/org.jenkins-ci.plugins:release<2.10
2.10
Jenkins Release Jenkins<=2.9
Event History
Jan 23, 2018
CVE Published
via MITRE·02:00 PM
Data Sourced
via MITRE·02:00 PM
Description
May 14, 2022
Advisory Published
via GitHub·03:45 AM
Frequently Asked Questions
1
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.
2
How do I fix CVE-2018-1000013?
To mitigate CVE-2018-1000013, upgrade the Jenkins Release Plugin to version 2.10 or later.
3
What type of vulnerability is CVE-2018-1000013?
CVE-2018-1000013 is a Cross-Site Request Forgery (CSRF) vulnerability.
4
Which versions are affected by CVE-2018-1000013?
CVE-2018-1000013 affects Jenkins Release Plugin versions up to 2.9 inclusive.
5
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.