high
7.5
CWE
264
Advisory Published
Advisory Published
Updated

CVE-2016-5007

First published: Thu May 25 2017(Updated: )

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.

Credit: security_alert@emc.com

Affected SoftwareAffected VersionHow to fix
maven/org.springframework.security:spring-security-core<4.1.1
4.1.1
maven/org.springframework:spring-core<4.3.1
4.3.1
Spring Framework=3.2.0
Spring Framework=4.0.0
Spring Framework=4.1.0
Spring Framework=4.2.0
VMware Spring Framework=3.2.1
VMware Spring Framework=3.2.2
VMware Spring Framework=3.2.3
VMware Spring Framework=3.2.4
VMware Spring Framework=3.2.5
VMware Spring Framework=3.2.6
VMware Spring Framework=3.2.7
VMware Spring Framework=3.2.8
VMware Spring Framework=3.2.9
VMware Spring Framework=3.2.10
VMware Spring Framework=3.2.11
VMware Spring Framework=3.2.12
VMware Spring Framework=3.2.13
VMware Spring Framework=3.2.14
VMware Spring Framework=3.2.15
VMware Spring Framework=3.2.16
VMware Spring Framework=3.2.17
VMware Spring Framework=3.2.18
VMware Spring Framework=4.0.1
VMware Spring Framework=4.0.2
VMware Spring Framework=4.0.3
VMware Spring Framework=4.0.4
VMware Spring Framework=4.0.5
VMware Spring Framework=4.0.6
VMware Spring Framework=4.0.7
VMware Spring Framework=4.0.8
VMware Spring Framework=4.0.9
VMware Spring Framework=4.1.1
VMware Spring Framework=4.1.2
VMware Spring Framework=4.1.3
VMware Spring Framework=4.1.4
VMware Spring Framework=4.1.5
VMware Spring Framework=4.1.6
VMware Spring Framework=4.1.7
VMware Spring Framework=4.1.8
VMware Spring Framework=4.1.9
VMware Spring Framework=4.2.1
VMware Spring Framework=4.2.2
VMware Spring Framework=4.2.3
VMware Spring Framework=4.2.4
VMware Spring Framework=4.2.5
VMware Spring Framework=4.2.6
VMware Spring Framework=4.2.7
VMware Spring Framework=4.2.8
VMware Spring Framework=4.2.9
Spring Security=3.2.0
Spring Security=3.2.1
Spring Security=3.2.2
Spring Security=3.2.3
Spring Security=3.2.4
Spring Security=3.2.5
Spring Security=3.2.6
Spring Security=3.2.7
Spring Security=3.2.8
Spring Security=3.2.9
Spring Security=3.2.10
Spring Security=4.0.0
Spring Security=4.0.1
Spring Security=4.0.2
Spring Security=4.0.3
Spring Security=4.0.4
Spring Security=4.1.0

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.

Read MoreStart Free Trial

Reference Links

Frequently Asked Questions

  • What is the severity of CVE-2016-5007?

    CVE-2016-5007 is considered a high-severity vulnerability due to potential authorization bypass.

  • How do I fix CVE-2016-5007?

    To fix CVE-2016-5007, upgrade Spring Security to version 4.1.1 or later, and Spring Framework to version 4.3.1 or later.

  • Which versions are affected by CVE-2016-5007?

    CVE-2016-5007 affects Spring Security versions 3.2.x and 4.0.x to 4.1.x, as well as Spring Framework versions 3.2.x to 4.2.x.

  • What type of vulnerability is CVE-2016-5007?

    CVE-2016-5007 is an authorization bypass vulnerability resulting from inconsistent URL pattern mappings.

  • Who is impacted by CVE-2016-5007?

    Users and developers utilizing affected versions of Spring Security and Spring Framework are at risk due to CVE-2016-5007.

Company

Resources

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2025 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203