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 security_alert@emc.com
Affected Software | Affected Version | How 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 | |
Spring Framework | =3.2.1 | |
Spring Framework | =3.2.2 | |
Spring Framework | =3.2.3 | |
Spring Framework | =3.2.4 | |
Spring Framework | =3.2.5 | |
Spring Framework | =3.2.6 | |
Spring Framework | =3.2.7 | |
Spring Framework | =3.2.8 | |
Spring Framework | =3.2.9 | |
Spring Framework | =3.2.10 | |
Spring Framework | =3.2.11 | |
Spring Framework | =3.2.12 | |
Spring Framework | =3.2.13 | |
Spring Framework | =3.2.14 | |
Spring Framework | =3.2.15 | |
Spring Framework | =3.2.16 | |
Spring Framework | =3.2.17 | |
Spring Framework | =3.2.18 | |
Spring Framework | =4.0.1 | |
Spring Framework | =4.0.2 | |
Spring Framework | =4.0.3 | |
Spring Framework | =4.0.4 | |
Spring Framework | =4.0.5 | |
Spring Framework | =4.0.6 | |
Spring Framework | =4.0.7 | |
Spring Framework | =4.0.8 | |
Spring Framework | =4.0.9 | |
Spring Framework | =4.1.1 | |
Spring Framework | =4.1.2 | |
Spring Framework | =4.1.3 | |
Spring Framework | =4.1.4 | |
Spring Framework | =4.1.5 | |
Spring Framework | =4.1.6 | |
Spring Framework | =4.1.7 | |
Spring Framework | =4.1.8 | |
Spring Framework | =4.1.9 | |
Spring Framework | =4.2.1 | |
Spring Framework | =4.2.2 | |
Spring Framework | =4.2.3 | |
Spring Framework | =4.2.4 | |
Spring Framework | =4.2.5 | |
Spring Framework | =4.2.6 | |
Spring Framework | =4.2.7 | |
Spring Framework | =4.2.8 | |
Spring Framework | =4.2.9 | |
VMware Spring Security | =3.2.0 | |
VMware Spring Security | =3.2.1 | |
VMware Spring Security | =3.2.2 | |
VMware Spring Security | =3.2.3 | |
VMware Spring Security | =3.2.4 | |
VMware Spring Security | =3.2.5 | |
VMware Spring Security | =3.2.6 | |
VMware Spring Security | =3.2.7 | |
VMware Spring Security | =3.2.8 | |
VMware Spring Security | =3.2.9 | |
VMware Spring Security | =3.2.10 | |
VMware Spring Security | =4.0.0 | |
VMware Spring Security | =4.0.1 | |
VMware Spring Security | =4.0.2 | |
VMware Spring Security | =4.0.3 | |
VMware Spring Security | =4.0.4 | |
VMware Spring Security | =4.1.0 |
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
CVE-2016-5007 is considered a high-severity vulnerability due to potential authorization bypass.
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.
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.
CVE-2016-5007 is an authorization bypass vulnerability resulting from inconsistent URL pattern mappings.
Users and developers utilizing affected versions of Spring Security and Spring Framework are at risk due to CVE-2016-5007.