Your RSA-2048 keys break in 2030. Find every one of them before attackers do.
Maven
Not in CISA KEV
MEDIUM severity

CVE-2008-5515 tomcat

MEDIUMFix: apache/tomcat@6b61911

CVE-2008-5515 is a medium-severity (CVSS 5.3) Path Traversal vulnerability in org.apache.tomcat:tomcat. EPSS puts its 30-day exploitation probability at 18.7% (97th percentile). A fix is available for org.apache.tomcat:tomcat — see the affected versions and patch details below.

Directory Traversal in Apache Tomcat

Published
May 14, 2022
Updated
Feb 21, 2024
Affected
3 pkgs
Patched
3 / 3
Exploits
None indexed
Exploitation data as of Sep 21, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

EPSS Exploitation Probability

via FIRST.org ↗
18.7%probability of exploitation in next 30 days
Moderate Risk0.00%
Lower risk than most CVEs97th percentile — riskier than 97% of all scored CVEsHighest risk

EPSS (Exploit Prediction Scoring System) is a daily probability model maintained by FIRST.org. It estimates the likelihood a CVE will be exploited in production environments within the next 30 days, derived from real-world threat intelligence signals.

How urgent is this, really

CVE-2008-5515 plotted by exploitation likelihood (EPSS) against impact (CVSS). The shaded corner — EPSS 50%+ and CVSS 7.0+ — is where this CVE doesn't sit, though severity or exploitability alone can still warrant action.

Where this sits among everything scored

Of 377,636 CVEs with a current EPSS score, this one falls in the 10–50% band (highlighted). Real counts from FIRST.org, not a sample — log-scaled since the landscape is heavily right-skewed.

Real-World Exposure

3 pkgs affected
org.apache.tomcat:tomcatorg.apache.tomcat:tomcatorg.apache.tomcat:tomcat

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects Maven packages — download data is not available via public APIs for these ecosystems.

Description

Apache Tomcat 4.1.0 through 4.1.39, 5.5.0 through 5.5.27, 6.0.0 through 6.0.18, and possibly earlier versions normalizes the target pathname before filtering the query string when using the RequestDispatcher method, which allows remote attackers to bypass intended access restrictions and conduct directory traversal attacks via .. (dot dot) sequences and the WEB-INF directory in a Request.

Affected Packages

3 total 3 fixed
EcosystemPackageVulnerable rangeFix
Mavenorg.apache.tomcat:tomcat4.1.0&&< 4.1.404.1.40org.apache.tomcat:tomcat:4.1.40
Mavenorg.apache.tomcat:tomcat5.5.0&&< 5.5.285.5.28org.apache.tomcat:tomcat:5.5.28
Mavenorg.apache.tomcat:tomcat6.0.0&&< 6.0.206.0.20org.apache.tomcat:tomcat:6.0.20

Detection & mitigation playbook

Open-source dependency
  1. Detect

    Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for org.apache.tomcat:tomcat, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

  2. Fix

    Update org.apache.tomcat:tomcat to 4.1.40 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2008-5515 is resolved across your whole dependency graph.

  3. Workarounds

    If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

  4. How O3 protects you

    O3 Security's impact-aware SCA analyses which vulnerable code paths your application actually calls, so a match like CVE-2008-5515 can be triaged on real exposure rather than presence alone.

Tailored to CVE-2008-5515. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Fixing This On Your OS

If you run this on a Linux distribution, patch through your package manager against the distro's own security advisory below — it tracks the exact backported fix for your release, which can ship on a different timeline (and sometimes a different severity) than the upstream project.

Red HatImportant
ProductFixed inAdvisory
JBEAP 4.2.0 for RHEL 4hibernate3-1:3.2.4-1.SP1_CP08.0jpp.ep1.2.el4RHSA-2009:1144
JBEAP 4.2.0 for RHEL 5hibernate3-1:3.2.4-1.SP1_CP08.0jpp.ep1.2.3.el5RHSA-2009:1143
JBEWS 1.0 for RHEL 4tomcat5-0:5.5.23-1.patch07.19.ep5.el4RHSA-2009:1454
JBEWS 1.0 for RHEL 4tomcat6-0:6.0.18-11.3.ep5.el4RHSA-2009:1506
Red Hat Certificate System 7.3ant-0:1.6.5-1jpp_1rhRHSA-2010:0602
Red Hat Developer Suite V.3tomcat5-0:5.5.23-0jpp_18rhRHSA-2009:1563
Red Hat Enterprise Linux 5tomcat5-0:5.5.23-0jpp.7.el5_3.2RHSA-2009:1164
Red Hat JBoss Enterprise Application Platform 4.3 for RHEL 4glassfish-jaxb-0:2.1.4-1.11.ep1.el4RHSA-2009:1146

Frequently Asked Questions

Apache Tomcat 4.1.0 through 4.1.39, 5.5.0 through 5.5.27, 6.0.0 through 6.0.18, and possibly earlier versions normalizes the target pathname before filtering the query string when using the RequestDispatcher method, which allows remote attackers to bypass intended access restrictions and conduct directory traversal attacks via .. (dot dot) sequences and the WEB-INF directory in a Request.
O3 Security · Impact-Aware SCA

Is CVE-2008-5515 in your dependencies?

O3 Security finds CVE-2008-5515 across Maven dependencies, including transitive ones, and its impact-aware SCA ranks findings by whether your code actually calls the vulnerable path.

CVE-2008-5515: tomcat (Medium 5.3) | O3 Security