Apache Tomcat: Bypass longest prefix security constraint
Apache Software Foundation Apache Tomcat
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| org.apache.tomcat:tomcat Maven |
|
|
Apache Software Foundation Apache Tomcat
| Product | Affected | Fixed in |
|---|---|---|
| org.apache.tomcat:tomcat Maven |
|
|
| org.apache.tomcat:tomcat-catalina Maven |
|
|
| org.apache.tomcat.embed:tomcat-embed-core Maven |
|
|
Improper Access Control, Incorrect Authorization vulnerability in Apache Tomcat leads to security constraint bypass if a constraint for a longer path is specified before a more restrictive constraint for a shorter sub-path.
This issue affects Apache Tomcat: from 11.0.0-M1 through 11.0.24, from 10.1.0-M1 through 10.1.57, from 9.0.0.M1 through 9.0.120, from 8.5.0 through 8.5.100, from 7.0.0 through 7.0.109.
Users are recommended to upgrade to version 11.0.25, 10.1.58, 9.0.121, which fixes the issue.
From the CVE record · apache
Apache Tomcat can incorrectly apply security constraints when a constraint for a longer path is specified before a more restrictive constraint for a shorter sub-path. An attacker can bypass the more restrictive constraint in that configuration. The input does not specify whether authentication or user interaction is required.
Teams running Apache Tomcat or the listed Maven packages should check versions 11.0.0-M1–11.0.24, 10.1.0-M1–10.1.57, 9.0.0-M1–9.0.120, 8.5.0–8.5.100, and 7.0.0–7.0.109.