CVE-2016-9879
HighSummary
An issue was discovered in Pivotal Spring Security before version 3.2.10, 4.1.x before 4.1.4, and 4.2.x before 4.2.1 regarding the lack of consideration for URL path parameters when processing security constraints. An attacker may bypass these constraints by adding an encoded '/' parameter to a request.
Risk Assessment
Organizations may be exposed to unauthorized access to resources, potentially leading to serious security breaches. Specifically, the ability to bypass security constraints poses a risk to data integrity.
Recommendation
It is recommended to update Pivotal Spring Security to the latest version to mitigate this vulnerability. Additionally, conducting a security audit of applications using this library is advisable.
Other vulnerabilities in Pivotal Spring Security
Original NVD description (English source)
An issue was discovered in Pivotal Spring Security before 3.2.10, 4.1.x before 4.1.4, and 4.2.x before 4.2.1. Spring Security does not consider URL path parameters when processing security constraints. By adding a URL path parameter with an encoded "/" to a request, an attacker may be able to bypass a security constraint. The root cause of this issue is a lack of clarity regarding the handling of path parameters in the Servlet Specification. Some Servlet containers include path parameters in the value returned for getPathInfo() and some do not. Spring Security uses the value returned by getPathInfo() as part of the process of mapping requests to security constraints. The unexpected presence of path parameters can cause a constraint to be bypassed. Users of Apache Tomcat (all current versions) are not affected by this vulnerability since Tomcat follows the guidance previously provided by the Servlet Expert group and strips path parameters from the value returned by getContextPath(), get