Improper Verification of Source of a Communication Channel in Apache Tomcat
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| org.apache.tomcat:tomcat Maven |
|
|
| Product | Affected | Fixed in |
|---|---|---|
| org.apache.tomcat:tomcat Maven |
|
|
The setGlobalContext method in org/apache/naming/factory/ResourceLinkFactory.java in Apache Tomcat 7.x before 7.0.68, 8.x before 8.0.31, and 9.x before 9.0.0.M3 does not consider whether ResourceLinkFactory.setGlobalContext callers are authorized, which allows remote authenticated users to bypass intended SecurityManager restrictions and read or write to arbitrary application data, or cause a denial of service (application disruption), via a web application that sets a crafted global context.
From the CVE record · redhat
Apache Tomcat's ResourceLinkFactory does not check whether callers are authorized to set the global context. A remote authenticated user can use a web application that sets a crafted global context to bypass SecurityManager restrictions, read or write arbitrary application data, or disrupt the application.
Check Maven org.apache.tomcat:tomcat deployments running 7.0.0 through 7.0.67, 8.0.0 through 8.0.31, or 9.0.0.M1 through before 9.0.0.M3.