Authentication Bypass Using an Alternate Path or Channel in Apache Tomcat
Apache Software Foundation Apache Tomcat
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| org.apache.tomcat:tomcat-jasper Maven |
|
|
Apache Software Foundation Apache Tomcat
| Product | Affected | Fixed in |
|---|---|---|
| org.apache.tomcat:tomcat-jasper Maven |
|
|
| org.apache.tomcat:jasper Maven |
|
|
| org.apache.tomcat.embed:tomcat-embed-jasper Maven |
|
|
In Apache Tomcat 9.0.0.M1 to 9.0.0.M9, 8.5.0 to 8.5.4, 8.0.0.RC1 to 8.0.36, 7.0.0 to 7.0.70 and 6.0.0 to 6.0.45 a malicious web application was able to bypass a configured SecurityManager via a Tomcat utility method that was accessible to web applications.
From the CVE record · apache
A Tomcat utility method accessible to web applications can let a malicious web application bypass a configured SecurityManager. Exploitation requires the malicious web application to be present and a SecurityManager to be configured; the input does not specify authentication or user-interaction requirements.
Engineers running Apache Tomcat or using affected Maven versions of tomcat-jasper, jasper, or tomcat-embed-jasper should check their dependencies: affected versions span 9.0.0.M1–9.0.0.M9, 8.5.0–8.5.4, 8.0.0RC1–8.0.36, 7.0.0–7.0.71, and, where applicable, 6.0.0–6.0.46.