Strix
26.1K

CVE-2016-5007

UnknownEPSS 2.78%

Last modified

CVE-2016-5007 is a vulnerability of currently unknown severity. 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 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. EPSS estimates a 2.78% chance of exploitation in the next 30 days.

Description

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 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.

Metrics

EPSS Probability
2.78%

84.5th percentile

Probability of exploitation in the next 30 days. Learn more

Weakness Enumeration

Affected Software

VendorProductVersions
Pivotal SoftwareSpring Framework3.2.0
Pivotal SoftwareSpring Framework4.0.0
Pivotal SoftwareSpring Framework4.1.0
Pivotal SoftwareSpring Framework4.2.0
VmwareSpring Framework3.2.1
VmwareSpring Framework3.2.2
VmwareSpring Framework3.2.3
VmwareSpring Framework3.2.4
VmwareSpring Framework3.2.5
VmwareSpring Framework3.2.6
VmwareSpring Framework3.2.7
VmwareSpring Framework3.2.8
VmwareSpring Framework3.2.9
VmwareSpring Framework3.2.10
VmwareSpring Framework3.2.11
VmwareSpring Framework3.2.12
VmwareSpring Framework3.2.13
VmwareSpring Framework3.2.14
VmwareSpring Framework3.2.15
VmwareSpring Framework3.2.16
VmwareSpring Framework3.2.17
VmwareSpring Framework3.2.18
VmwareSpring Framework4.0.1
VmwareSpring Framework4.0.2
VmwareSpring Framework4.0.3
VmwareSpring Framework4.0.4
VmwareSpring Framework4.0.5
VmwareSpring Framework4.0.6
VmwareSpring Framework4.0.7
VmwareSpring Framework4.0.8
VmwareSpring Framework4.0.9
VmwareSpring Framework4.1.1
VmwareSpring Framework4.1.2
VmwareSpring Framework4.1.3
VmwareSpring Framework4.1.4
VmwareSpring Framework4.1.5
VmwareSpring Framework4.1.6
VmwareSpring Framework4.1.7
VmwareSpring Framework4.1.8
VmwareSpring Framework4.1.9
VmwareSpring Framework4.2.1
VmwareSpring Framework4.2.2
VmwareSpring Framework4.2.3
VmwareSpring Framework4.2.4
VmwareSpring Framework4.2.5
VmwareSpring Framework4.2.6
VmwareSpring Framework4.2.7
VmwareSpring Framework4.2.8
VmwareSpring Framework4.2.9
VmwareSpring Security3.2.0

Showing 50 of 66 affected configurations. See NVD for the full list.

References

Timeline

Published
Last Modified
Status
Modified

Frequently Asked Questions

What is 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 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.
How severe is CVE-2016-5007?
Severity scoring for CVE-2016-5007 is pending analysis. The EPSS model estimates a 2.78% probability of exploitation in the next 30 days.
How do I fix CVE-2016-5007?
Check the vendor references and advisories linked above for patched versions and mitigation guidance. You can also run a Strix scan to test if your systems are affected.

Are you affected by CVE-2016-5007?

Run a free Strix scan to check your systems for this vulnerability.

Scan your code now

Source: NVD / NIST