Description
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.
Remediation
References
https://access.redhat.com/errata/RHSA-2018:2405
https://lists.apache.org/thread.html/4ed49b103f64a0cecb38064f26cbf1389afc12124653da2d35166dbe%40%3Cissues.activemq.apache.org%3E
https://lists.apache.org/thread.html/ab825fcade0b49becfa30235b3d54f4a51bb74ea96b6c9adb5d1378c%40%3Cissues.activemq.apache.org%3E
https://lists.apache.org/thread.html/dcf8599b80e43a6b60482607adb76c64672772dc2d9209ae2170f369%40%3Cissues.activemq.apache.org%3E
https://pivotal.io/security/cve-2018-1199
https://www.oracle.com/security-alerts/cpujul2020.html
Related Vulnerabilities
CVE-2018-16472 Vulnerability in maven package org.webjars.npm:cached-path-relative
CVE-2016-5005 Vulnerability in maven package org.apache.archiva:archiva-webapp
CVE-2022-24999 Vulnerability in maven package org.webjars.npm:qs
CVE-2017-15712 Vulnerability in maven package org.apache.oozie:oozie-core
CVE-2020-1963 Vulnerability in maven package org.apache.ignite:ignite-core