Atomicorp WAF Research Note: CVE-2025-24813

Apache Tomcat Path Equivalence - Remote Code Execution

CVE Details

• Already protected by existing Atomicorp WAF rules
• Protection status: Understanding Atomicorp WAF Protection Status
• CVE: CVE-2025-24813
• Name: Apache Tomcat Path Equivalence - Remote Code Execution
• Severity: Critical
• CVSS: 9.8 (v3.1) (Critical)
• CVSS version: 3.1
• CVSS source: NVD
• CVSS vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
  • Attack vector: Network
  • Attack complexity: Low
  • Privileges required: None
  • User interaction: None
  • Scope: Unchanged
  • Confidentiality impact: High
  • Integrity impact: High
  • Availability impact: High
• CWE: CWE-44 — Path Equivalence: ‘file.name’ (Internal Dot), CWE-502 — Deserialization of Untrusted Data, CWE-706 — Use of Incorrectly-Resolved Name or Reference
• Related CAPEC attack patterns (via MITRE CWE relationships): CAPEC-159 (opens in a new tab) , CAPEC-177 (opens in a new tab) , CAPEC-48 (opens in a new tab) , CAPEC-586 (opens in a new tab) , CAPEC-641 (opens in a new tab)
• Vendor: apache
• Vulnerable products: tomcat , debian linux , bootstrap os
• CVE published: 2025-03-10
• CVE last modified: 2026-06-17
• Affected versions (NVD configurations):
  • tomcat: < 9.0.99
  • tomcat: >= 10.1.1, < 10.1.35
  • tomcat: >= 11.0.1, < 11.0.3
  • tomcat: 10.1.0 milestone1
  • tomcat: 10.1.0 milestone10
  • tomcat: 10.1.0 milestone11
  • tomcat: 10.1.0 milestone12
  • tomcat: 10.1.0 milestone13
  • tomcat: 10.1.0 milestone14
  • tomcat: 10.1.0 milestone15
  • tomcat: 10.1.0 milestone16
  • tomcat: 10.1.0 milestone17
  • tomcat: 10.1.0 milestone18
  • tomcat: 10.1.0 milestone19
  • tomcat: 10.1.0 milestone2
  • tomcat: 10.1.0 milestone20
  • tomcat: 10.1.0 milestone3
  • tomcat: 10.1.0 milestone4
  • tomcat: 10.1.0 milestone5
  • tomcat: 10.1.0 milestone6
  • tomcat: 10.1.0 milestone7
  • tomcat: 10.1.0 milestone8
  • tomcat: 10.1.0 milestone9
  • tomcat: 11.0.0 milestone1
  • tomcat: 11.0.0 milestone10
  • tomcat: 11.0.0 milestone11
  • tomcat: 11.0.0 milestone12
  • tomcat: 11.0.0 milestone13
  • tomcat: 11.0.0 milestone14
  • tomcat: 11.0.0 milestone15
  • tomcat: 11.0.0 milestone16
  • tomcat: 11.0.0 milestone17
  • tomcat: 11.0.0 milestone18
  • tomcat: 11.0.0 milestone19
  • tomcat: 11.0.0 milestone2
  • tomcat: 11.0.0 milestone20
  • tomcat: 11.0.0 milestone21
  • tomcat: 11.0.0 milestone22
  • tomcat: 11.0.0 milestone23
  • tomcat: 11.0.0 milestone24
  • tomcat: 11.0.0 milestone25
  • tomcat: 11.0.0 milestone3
  • tomcat: 11.0.0 milestone4
  • tomcat: 11.0.0 milestone5
  • tomcat: 11.0.0 milestone6
  • tomcat: 11.0.0 milestone7
  • tomcat: 11.0.0 milestone8
  • tomcat: 11.0.0 milestone9
  • debian linux: 11.0
  • bootstrap os
• EPSS: 0.9993; 100.0th percentile (FIRST (opens in a new tab) )
• CISA KEV: Listed (added 2025-04-01)
  • Known ransomware campaign use: Unknown
• Latest Update: 2026-09-06
• Selected Rule IDs observed: 392301
• Matching rules: 1; rules with blocking actions: 1
• Would-block Rule IDs: 392301
• Request surfaces inspected: Request headers

Vulnerability Description

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.

Recommended Actions

1. Maintain the observed Atomicorp protections. Keep your Atomicorp commercial rules current and confirm that the selected observed rules (392301 ) have not been locally disabled. Atomicorp commercial rules are enabled by default. If you use Atomic WAF, review the applicable policy and rule settings.

2. Apply the vendor’s remediation. WAF protection is defense in depth and does not replace upgrading or following the affected vendor’s guidance.

   • Affected versions: Apache Software Foundation Apache Tomcat versions through 11.0.2.
   • Affected versions: Apache Software Foundation Apache Tomcat versions through 10.1.34.
   • Affected versions: Apache Software Foundation Apache Tomcat versions through 9.0.98.
   • Affected versions: Apache Software Foundation Apache Tomcat versions through 8.5.100.
   • Versions reported unknown: Apache Software Foundation Apache Tomcat versions earlier than 8.5.0.
   • Versions reported unknown: Apache Software Foundation Apache Tomcat versions through 10.0.27.
   • No specific CNA/vendor solution or workaround is included in the current CVE Record (opens in a new tab) . Review the vendor’s security advisories and supported-release guidance before making changes.
   • CISA KEV required action: Apply mitigations per vendor instructions, follow applicable BOD 22-01 guidance for cloud services, or discontinue use of the product if mitigations are unavailable.
   • CISA KEV federal remediation due date: 2025-04-22

3. Validate after changes. Confirm rule updates are current, review WAF events for the affected application, and test application behavior after vendor upgrades, mitigations, or local policy changes.

Research Notes

Atomicorp WAF protections are designed around attack techniques and exploit behaviors, allowing existing protections to apply across multiple vulnerabilities without requiring a unique rule for every CVE.

Public Vulnerability References

• NVD (opens in a new tab)
• CVE Record (opens in a new tab)
• Vendor advisory: https://lists.apache.org/thread/j5fkjv2k477os90nczf2v9l61fb0kkgq (opens in a new tab)
• Exploit or technical research: http://www.openwall.com/lists/oss-security/2025/03/10/5 (opens in a new tab)
• Exploit or technical research: https://lists.debian.org/debian-lts-announce/2025/04/msg00003.html (opens in a new tab)
• Exploit or technical research: https://security.netapp.com/advisory/ntap-20250321-0001/ (opens in a new tab)
• CVE authority reference: https://www.vicarius.io/vsociety/posts/cve-2025-24813-detect-apache-tomcat-rce (opens in a new tab)
• CVE authority reference: https://www.vicarius.io/vsociety/posts/cve-2025-24813-mitigate-apache-tomcat-rce (opens in a new tab)
• CVE authority reference: https://www.vicarius.io/vsociety/posts/cve-2025-24813-tomcat-detect-vulnerability (opens in a new tab)
• CVE authority reference: https://www.vicarius.io/vsociety/posts/cve-2025-24813-tomcat-mitigation-vulnerability (opens in a new tab)
• Exploit or technical research: https://github.com/absholi7ly/POC-CVE-2025-24813/blob/main/README.md (opens in a new tab)
• Exploit or technical research: https://www.cisa.gov/known-exploited-vulnerabilities-catalog?field_cve=CVE-2025-24813 (opens in a new tab)

Test or Research Source

• Source: http/cves/2025/CVE-2025-24813.yaml (opens in a new tab)
• Tags: apache, cve, cve2025, intrusive, kev, rce, tomcat, vkev, vuln

Research Note Context

This research note documents exploit-technique analysis associated with this vulnerability and references Atomicorp WAF protections observed during engineering review, testing, or validation activities.

Atomicorp security controls are generally designed to identify and mitigate attack techniques and exploit behaviors rather than individual CVE identifiers. As a result, protections developed for one vulnerability may also apply to related attack variants and future vulnerabilities using similar techniques.

Learn More

Atomicorp develops commercially supported security technologies for web applications, servers, endpoints, workloads, and legacy enterprise platforms.

Organizations interested in protecting systems against exploit techniques associated with vulnerabilities such as this one can learn more about:

• Atomic ModSecurity Rules: commercially maintained WAF rules for ModSecurity deployments, including protections for web attacks, bots, scanners, malware, exploitation attempts, and emerging vulnerability classes.
• Atomic WAF: an enterprise web application firewall with Atomicorp rules, centralized management, reporting, authentication controls, and operational tooling.
• Atomic ModSecurity Integrator: a special licensing option for MSPs, MSSPs, OEMs, VARs, reverse proxy providers, and other integrators who want to incorporate Atomicorp ModSecurity rule technology into their own products or services.
• Atomic OSSEC: an enterprise OSSEC-based intrusion detection, compliance, and security monitoring platform.
• Atomic Protector: workload protection for Linux, web, cloud, data center, and hybrid environments.

For additional information, product evaluations, or technical discussions, visit https://www.atomicorp.com/ or https://modsecurity.io/ (opens in a new tab) .