GHSA-v596-fwhq-8x48 Improper Input Validation in org.springframework.security:spring-security-core, org.springframework.security:spring-security-core , and org.springframework:spring-core

• Maven org.springframework.security:spring-security-core: >= 4.2.0, < 4.2.4 → fixed in 4.2.4 • Maven org.springframework.security:spring-security-core: >= 5.0.0, < 5.0.1 → fixed in 5.0.1 • Maven org.springframework:spring-core: >= 4.3.0, < 4.3.14 → fixed in 4.3.14 • Maven org.springframework:spring-core: >= 5.0.0, < 5.0.3 → fixed in 5.0.3 • Maven org.springframework.security:spring-security-core: >= 4.1.0, < 4.1.5 → fixed in 4.1.5

Spring Security (Spring Security 4.1.x before 4.1.5, 4.2.x before 4.2.4, and 5.0.x before 5.0.1; and Spring Framework 4.3.x before 4.3.14 and 5.0.x before 5.0.3) does not consider URL path parameters when processing security constraints. By adding a URL path parameter with special encodings, 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. In this particular attack, different character encodings used in path parameters allows secured Spring MVC static resource URLs to be bypassed.