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. The following versions were EOL at the time the CVE was created but are known to be affected: 8.5.0 though 8.5.100. Other, older, EOL versions may also be affected. 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.99, which fixes the issue.
This vulnerability carries a CRITICAL severity rating with a CVSS v3.1 score of 9.8, indicating it can be exploited remotely over the network with relatively low complexity without requiring user interaction and does not require pre-existing privileges . The vulnerability impacts confidentiality (data exposure), integrity (unauthorized modifications), and availability (service disruption) for affected systems. Impacting 4 products from apache, from debian, from netapp and 1 other, organizations running these solutions should prioritize assessment and patching.
Reported in 2025, this vulnerability emerged during an era marked by increased sophistication in supply chain attacks, cloud infrastructure vulnerabilities, and software-as-a-service (SaaS) security challenges. Security practices during this period emphasized zero-trust architectures, container security, and API protection.
2025-03-10T17:15:35.067
2025-10-23T14:49:29.133
Analyzed
CVSSv3.1: 9.8 (CRITICAL)
| Type | Vendor | Product | Version/Range | Vulnerable? |
|---|---|---|---|---|
| Application | apache | tomcat | < 9.0.99 | Yes |
| Application | apache | tomcat | < 10.1.35 | Yes |
| Application | apache | tomcat | < 11.0.3 | Yes |
| Application | apache | tomcat | 10.1.0 | Yes |
| Application | apache | tomcat | 10.1.0 | Yes |
| Application | apache | tomcat | 10.1.0 | Yes |
| Application | apache | tomcat | 10.1.0 | Yes |
| Application | apache | tomcat | 10.1.0 | Yes |
| Application | apache | tomcat | 10.1.0 | Yes |
| Application | apache | tomcat | 10.1.0 | Yes |
| Application | apache | tomcat | 10.1.0 | Yes |
| Application | apache | tomcat | 10.1.0 | Yes |
| Application | apache | tomcat | 10.1.0 | Yes |
| Application | apache | tomcat | 10.1.0 | Yes |
| Application | apache | tomcat | 10.1.0 | Yes |
| Application | apache | tomcat | 10.1.0 | Yes |
| Application | apache | tomcat | 10.1.0 | Yes |
| Application | apache | tomcat | 10.1.0 | Yes |
| Application | apache | tomcat | 10.1.0 | Yes |
| Application | apache | tomcat | 10.1.0 | Yes |
| Application | apache | tomcat | 10.1.0 | Yes |
| Application | apache | tomcat | 10.1.0 | Yes |
| Application | apache | tomcat | 10.1.0 | Yes |
| Application | apache | tomcat | 11.0.0 | Yes |
| Application | apache | tomcat | 11.0.0 | Yes |
| Application | apache | tomcat | 11.0.0 | Yes |
| Application | apache | tomcat | 11.0.0 | Yes |
| Application | apache | tomcat | 11.0.0 | Yes |
| Application | apache | tomcat | 11.0.0 | Yes |
| Application | apache | tomcat | 11.0.0 | Yes |
| Application | apache | tomcat | 11.0.0 | Yes |
| Application | apache | tomcat | 11.0.0 | Yes |
| Application | apache | tomcat | 11.0.0 | Yes |
| Application | apache | tomcat | 11.0.0 | Yes |
| Application | apache | tomcat | 11.0.0 | Yes |
| Application | apache | tomcat | 11.0.0 | Yes |
| Application | apache | tomcat | 11.0.0 | Yes |
| Application | apache | tomcat | 11.0.0 | Yes |
| Application | apache | tomcat | 11.0.0 | Yes |
| Application | apache | tomcat | 11.0.0 | Yes |
| Application | apache | tomcat | 11.0.0 | Yes |
| Application | apache | tomcat | 11.0.0 | Yes |
| Application | apache | tomcat | 11.0.0 | Yes |
| Application | apache | tomcat | 11.0.0 | Yes |
| Application | apache | tomcat | 11.0.0 | Yes |
| Application | apache | tomcat | 11.0.0 | Yes |
| Application | apache | tomcat | 11.0.0 | Yes |
| Application | apache | tomcat | 11.0.0 | Yes |
| Operating System | debian | debian_linux | 11.0 | Yes |
| Operating System | netapp | bootstrap_os | - | Yes |
| Hardware | netapp | hci_compute_node | - | No |
SecUtils normalizes and enriches National Vulnerability Database (NVD) records by standardizing vendor and product identifiers, aggregating vulnerability metadata from both NVD and MITRE sources, and providing structured context for security teams. For apache's affected products, we extract Common Platform Enumeration (CPE) data, Common Weakness Enumeration (CWE) classifications, CVSS severity metrics, and reference data to enable rapid vulnerability prioritization and asset correlation. This record contains no exploit code, proof-of-concept instructions, or attack methodologies—only defensive intelligence necessary for patch management, risk assessment, and security operations.