Vulnerabilities · 2016 · Pivotal Software
CVE-2016-5007
Pivotal Software Spring Framework vulnerability
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.
Affected products
Spring Framework, Spring Security. The exact versions are in the references.
What to do now
- Check your exposureFind out whether Pivotal Software Spring Framework runs anywhere in your environment, including systems of suppliers.
- UpdateInstall the version in which the vendor fixed the vulnerability. The references lead to the advisory.
- Limit access until thenIf you cannot update at once, take the system off the internet or restrict who can reach it.
References
- pivotal.io/security/cve-2016-5007 · Vendor Advisory
- www.securityfocus.com/bid/91687 · Third Party Advisory
- www.oracle.com/technetwork/security-advisory/cpuapr2018-3678067.html
- www.oracle.com/technetwork/security-advisory/cpujul2019-5072835.html
- nvd.nist.gov/vuln/detail/CVE-2016-5007
- cve.org/CVERecord?id=CVE-2016-5007
More vulnerabilities in Pivotal Software products
Data: CVE list and the NVD. This product uses data from the NVD API but is not endorsed or certified by the NVD.