Potential remote code execution in Apache Tomcat
High severity
GitHub Reviewed
Published
May 21, 2020
to the GitHub Advisory Database
•
Updated Mar 11, 2024
Package
Affected versions
>= 10.0.0-M1, <= 10.0.0-M4
>= 9.0.0, < 9.0.35
>= 8.0.0, < 8.5.55
>= 7.0.0, < 7.0.104
Patched versions
10.0.0-M5
9.0.35
8.5.55
7.0.104
Description
Published by the National Vulnerability Database
May 20, 2020
Reviewed
May 21, 2020
Published to the GitHub Advisory Database
May 21, 2020
Last updated
Mar 11, 2024
Credits
-
sunSUNQ Analyst
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.
References