How severe is CVE-2000-1210?

No CVSS score has been assigned to CVE-2000-1210 yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by CVE-2000-1210?

CVE-2000-1210 affects the following packages: org.apache.tomcat:tomcat (Maven). Ecosystems affected: Maven.

How do I fix CVE-2000-1210?

The records we use list no patched version of org.apache.tomcat:tomcat for CVE-2000-1210. Check the maintainer's advisory, and where your build allows, override or pin the dependency away from the vulnerable range.

How do I detect CVE-2000-1210 in my Maven dependencies?

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.

How do I mitigate CVE-2000-1210 if there is no patch (or I can't update yet)?

Resolve every user-supplied path to its canonical form and reject anything that escapes the intended directory, and run the component under an account that has no read or write access outside the directory it legitimately serves.

Is CVE-2000-1210 actively exploited in the wild?

No public exploit code has been indexed for CVE-2000-1210 yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

What is the EPSS score for CVE-2000-1210?

CVE-2000-1210 has an EPSS (Exploit Prediction Scoring System) score of 3.5%, placing it in the 89th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. This score indicates relatively lower exploitation probability, though the CVSS severity should still guide your patching priority.

When was CVE-2000-1210 published, and has it been updated?

CVE-2000-1210 was published on April 30, 2022 and was last updated on November 8, 2023. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

☕ Maven

Not in CISA KEV

CVE-2000-1210 — tomcat

CVE-2000-1210 is a security vulnerability in org.apache.tomcat:tomcat. The records list no fixed version yet; check the vendor advisory below and apply the mitigations in the meantime.

Apache Tomcat Directory Traversal

Published

Apr 30, 2022

Updated

Nov 8, 2023

Affected

1 pkg

Patched

See advisory

Exploits

None indexed

Exploitation data as of Nov 5, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

EPSS Exploitation Probability

via FIRST.org ↗

3.5%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs89th percentile — riskier than 89% of all scored CVEsHighest risk

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

Real-World Exposure

1 pkg affected

☕org.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

Directory traversal vulnerability in source.jsp of Apache Tomcat before 3.1 allows remote attackers to read arbitrary files via a .. (dot dot) in the argument to source.jsp.

Affected Packages

1 total

Ecosystem	Package	Vulnerable range	Fix
☕Maven	`org.apache.tomcat:tomcat`	all versions	No fix

Affected Products

1 product · 1 configurations

Application

tomcatapache

≤ 3.1

range

Detection & mitigation playbook

Open-source dependency

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.
Remediation status
The records we use list no patched version of org.apache.tomcat:tomcat for CVE-2000-1210. Check the maintainer's advisory, and where your build allows, override or pin the dependency away from the vulnerable range.
Mitigate without a patch
Resolve every user-supplied path to its canonical form and reject anything that escapes the intended directory, and run the component under an account that has no read or write access outside the directory it legitimately serves.

Frequently Asked Questions

Directory traversal vulnerability in source.jsp of Apache Tomcat before 3.1 allows remote attackers to read arbitrary files via a `..` (dot dot) in the argument to source.jsp.

O3 Security · Impact-Aware SCA

Is CVE-2000-1210 in your dependencies?

Find it across Maven, including transitive dependencies.

Scan my dependencies How O3 SCA works