CVE-2016-5007

Both Spring Security 3.2.x, 4.0.x, 4.1.0 and the Spring Framework 3.2.x, 4.0.x, 4.1.x, 4.2.x (as well as other unsupported versions) rely on URL pattern mappings for authorization and for mapping requests to controllers respectively. Differences in the strictness of the pattern matching mechanisms, for example with regards to space trimming in path segments, can lead Spring Security to not recognize certain paths as not protected that are in fact mapped to Spring MVC controllers that should be protected. The problem is compounded by the fact that the Spring Framework provides richer features with regards to pattern matching as well as by the fact that pattern matching in each Spring Security and the Spring Framework can easily be customized creating additional differences.

CVE-2016-5007 has a CVSS score of 7.5 (High). The vector is network-reachable, no privileges required, and no user interaction. A CVSS score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether this affects your application depends on whether the vulnerable code is present and reachable in your environment. A fixed version is available (4.3.1, 4.1.1); upgrading removes the vulnerable code path.

Kodem intelligence

1. What is CVE-2016-5007? CVE-2016-5007 is a high-severity security vulnerability in org.springframework:spring-core (maven), affecting versions < 4.3.1. It is fixed in 4.3.1, 4.1.1.
2. How severe is CVE-2016-5007? CVE-2016-5007 has a CVSS score of 7.5 (High). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.
3. Which packages are affected by CVE-2016-5007?
   • org.springframework:spring-core (maven) (versions < 4.3.1)
   • org.springframework.security:spring-security-core (maven) (versions < 4.1.1)
4. Is there a fix for CVE-2016-5007? Yes. CVE-2016-5007 is fixed in 4.3.1, 4.1.1. Upgrade to this version or later.
5. Is CVE-2016-5007 exploitable, and should I be worried? Whether CVE-2016-5007 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
6. What actually determines whether CVE-2016-5007 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.
7. How do I fix CVE-2016-5007?
   • Upgrade org.springframework:spring-core to 4.3.1 or later
   • Upgrade org.springframework.security:spring-security-core to 4.1.1 or later