Summary
Jenkins before 1.638 and LTS before 1.625.2 uses a publicly accessible salt to generate CSRF protection tokens, which makes it easier for remote attackers to bypass the CSRF protection mechanism via a brute force attack.
Impact
A victim's authenticated browser session is used to submit forged requests to an application that cannot distinguish them from legitimate ones. Typical impact: state-changing actions performed as the victim without their consent.
Affected versions
Security releases
Kodem intelligence
Severity tells you how bad this could be in the worst case. It does not tell you whether you are exposed. Exploitability and impact are functions of runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A vulnerable package can sit in your dependency tree and never run.
Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter. Kodem's runtime-powered SCA identifies whether this CVE is reachable in your applications.
Remediation advice
org.jenkins-ci.main:jenkins-core to 1.625.2 or later; org.jenkins-ci.main:jenkins-core to 1.638 or later
Kodem Kai can prioritize this vulnerability in your dependency tree and generate a fix recommendation.
Frequently Asked Questions
- What is CVE-2015-5318? CVE-2015-5318 is a low-severity cross-site request forgery (CSRF) vulnerability in org.jenkins-ci.main:jenkins-core (maven), affecting versions < 1.625.2. It is fixed in 1.625.2, 1.638. A victim's authenticated browser session is used to submit forged requests to an application that cannot distinguish them from legitimate ones.
- Which versions of org.jenkins-ci.main:jenkins-core are affected by CVE-2015-5318? org.jenkins-ci.main:jenkins-core (maven) versions < 1.625.2 is affected.
- Is there a fix for CVE-2015-5318? Yes. CVE-2015-5318 is fixed in 1.625.2, 1.638. Upgrade to this version or later.
- Is CVE-2015-5318 exploitable, and should I be worried? Whether CVE-2015-5318 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
- What actually determines whether CVE-2015-5318 is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
- How do I fix CVE-2015-5318?
- Upgrade
org.jenkins-ci.main:jenkins-coreto 1.625.2 or later - Upgrade
org.jenkins-ci.main:jenkins-coreto 1.638 or later
- Upgrade