Potential remote code execution in Apache Tomcat
Apache Tomcat
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| org.apache.tomcat:tomcat-catalina Maven |
|
|
Apache Tomcat
| Product | Affected | Fixed in |
|---|---|---|
| org.apache.tomcat:tomcat-catalina Maven |
|
|
| org.apache.tomcat.embed:tomcat-embed-core Maven |
|
|
When using Apache Tomcat versions 10.0.0-M1 to 10.0.0-M4, 9.0.0.M1 to 9.0.34, 8.5.0 to 8.5.54 and 7.0.0 to 7.0.103 if a) an attacker is able to control the contents and name of a file on the server; and b) the server is configured to use the PersistenceManager with a FileStore; and c) the PersistenceManager is configured with sessionAttributeValueClassNameFilter="null" (the default unless a SecurityManager is used) or a sufficiently lax filter to allow the attacker provided object to be deserialized; and d) the attacker knows the relative file path from the storage location used by FileStore to the file the attacker has control over; then, using a specifically crafted request, the attacker will be able to trigger remote code execution via deserialization of the file under their control. Note that all of conditions a) to d) must be true for the attack to succeed.
From the CVE record · apache
Apache Tomcat can deserialize an attacker-controlled file when PersistenceManager uses a FileStore and its session attribute class-name filter is null or sufficiently lax. A crafted remote request can trigger code execution only if the attacker controls the file’s name and contents on the server and knows its relative path from the FileStore storage location.
Check deployments using Apache Tomcat or the Maven packages tomcat-catalina and tomcat-embed-core in versions 10.0.0-M1 through 10.0.0-M4, 9.0.0 through 9.0.34, 8.0.0 through 8.5.54, or 7.0.0 through 7.0.103.