First published: Mon Mar 10 2025(Updated: )
Path Equivalence: 'file.Name' (Internal Dot) leading to Remote Code Execution and/or Information disclosure and/or malicious content added to uploaded files via write enabled Default Servlet in Apache Tomcat. This issue affects Apache Tomcat: from 11.0.0-M1 through 11.0.2, from 10.1.0-M1 through 10.1.34, from 9.0.0.M1 through 9.0.98. If all of the following were true, a malicious user was able to view security sensitive files and/or inject content into those files: - writes enabled for the default servlet (disabled by default) - support for partial PUT (enabled by default) - a target URL for security sensitive uploads that was a sub-directory of a target URL for public uploads - attacker knowledge of the names of security sensitive files being uploaded - the security sensitive files also being uploaded via partial PUT If all of the following were true, a malicious user was able to perform remote code execution: - writes enabled for the default servlet (disabled by default) - support for partial PUT (enabled by default) - application was using Tomcat's file based session persistence with the default storage location - application included a library that may be leveraged in a deserialization attack Users are recommended to upgrade to version 11.0.3, 10.1.35 or 9.0.98, which fixes the issue.
Affected Software | Affected Version | How to fix |
---|---|---|
Tomcat | >=11.0.0-M1<11.0.2>=10.1.0-M1<10.1.34>=9.0.0.M1<9.0.98 |
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
REDHAT-BUG-2351129 has a high severity due to its potential for remote code execution and information disclosure.
To address REDHAT-BUG-2351129, upgrade Apache Tomcat to a version above 11.0.2, 10.1.34, or 9.0.98 depending on your current version.
REDHAT-BUG-2351129 affects Apache Tomcat versions from 11.0.0-M1 to 11.0.2, 10.1.0-M1 to 10.1.34, and 9.0.0-M1 to 9.0.98.
The potential impacts of REDHAT-BUG-2351129 include remote code execution, information disclosure, and malicious content being added to uploaded files.
While upgrading is the recommended solution, a temporary workaround could involve restricting write access to the Default Servlet.