`CVE-2000-0760` Apache Tomcat

Affected software	Apache Tomcat
Severity	6.4 Medium CVSS 2.0
Published	20 Oct 2000
Updated	16 Jun 2026

Description

The Snoop servlet in Jakarta Tomcat 3.1 and 3.0 under Apache reveals sensitive system information when a remote attacker requests a nonexistent URL with a .snp extension.

Exploitation status

Working exploit published

A reviewed exploit catalogue lists ready-to-run exploit code for this CVE.

CISA KEV not listed
VulnCheck KEV not listed
CISA Vulnrichment no assessment published
Indexed PoC 2 indexed Published artifacts you can open, in Exploit-DB, Nuclei; first seen 2000-07-20.
EPSS 62% chance in 30 days A model's forecast, not a report of exploitation. Higher than 99% of all scored CVEs.

Index	Artifact	Stars	First seen
Exploit-DB	Tomcat 3.0/3.1 Snoop Servlet - Information Disclosure		2000-07-20
Nuclei	Jakarta Tomcat 3.1 and 3.0 - Information Disclosure

Index

Artifact

Stars

First seen

Exploit-DB

Tomcat 3.0/3.1 Snoop Servlet - Information Disclosure

2000-07-20

Nuclei

Jakarta Tomcat 3.1 and 3.0 - Information Disclosure

Waratek protection

Mitigation candidate

A kind of vulnerability Waratek's rules address, with exploit code published or exploitation reported. No rule exists and none is planned yet. The decision below says what we found to build a rule from.

Protection none
Action unverified
Review automated Inferred
Record active

Decided by	An indexed exploit clearing the evidence bar to reverse-engineer, where there is no source to read
Finding	Mitigation candidate: 2 public proof-of-concept exploit(s) are indexed for this CVE (exploit-db, nuclei), but the affected code is not open source. That makes an ARMR patch rule a candidate rather than a plan. The exploit gives a reproducible entry point to trace inward from and a test to validate a hook against, which is what makes reverse engineering tractable at all. No rule exists and none is scheduled: the hook point must be recovered by decompiling the affected code, and a closer look may find none that ARMR can act on.

Decided by

An indexed exploit clearing the evidence bar to reverse-engineer, where there is no source to read

Finding

Mitigation candidate: 2 public proof-of-concept exploit(s) are indexed for this CVE (exploit-db, nuclei), but the affected code is not open source. That makes an ARMR patch rule a candidate rather than a plan. The exploit gives a reproducible entry point to trace inward from and a test to validate a hook against, which is what makes reverse engineering tractable at all. No rule exists and none is scheduled: the hook point must be recovered by decompiling the affected code, and a closer look may find none that ARMR can act on.

Affected software and releases

Products and versions

1 product, 2 version entries

Source	Vendor	Product	Scheme	Affected versions
nvd	apache	tomcat	generic	3.0 · 3.1

Source

Vendor

Product

Scheme

Affected versions

nvd

apache

tomcat

generic

3.0 · 3.1

References

URL	Tags
http://www.securityfocus.com/bid/1532	Exploit, Vendor Advisory
http://www.securityfocus.com/frames/?content=/templates/archive.pike%3Flist%3D1%26date%3D2000-07-15%26msg%3DPine.SUN.3.96.1000719235404.24004A-100000%40grex.cyberspace.org

URL

Timeline

Published	2000-10-20	By the CVE Program.
NVD record modified	2026-06-16	NVD's own last-modified date for this record.

Published

2000-10-20

By the CVE Program.

NVD record modified

2026-06-16

NVD's own last-modified date for this record.

How VRT decided (19 of 24 rules ran)

19 of 24 rules ran. The rest didn't run because an earlier rule had already settled the CVE.

# Rule Outcome Status Detail

identity: Does this identifier describe a vulnerability at all? the first rule that matches decides

1 rejected no match CVE Program withdrawal of this identifier

scope: Is it a vulnerability Waratek protects? the first rule that matches decides

2 armr-patch-file no match An ARMR patch file on disk for this CVE

3 armr-secure-rule-file no match An ARMR security-rule template on disk for this CVE

4 manual-classification no match A researcher's recorded decision for this specific CVE

5 manual classification no match Manual classification of this CVE in the legacy dataset

6 non-java-upstream no match A root cause in non-Java code: an OS kernel, a C library, or a bundled runtime

7 oracle-component no match The defect being in a component of a tracked product the agent does not reach: JavaFX, the Java SE installer, the JInitiator browser plug-in, the native WebLogic proxy plug-in, or a native part of Oracle Application Server or Collaboration Suite (HTTP Server, Web Cache, Internet Directory, mail and calendar servers). Oracle gives these no CPE of their own and names them only in the description.

8 java-client-side no match Oracle's own risk-matrix note saying the CVE is reached only through untrusted code in the Java sandbox (applets, Web Start) or only through a client installation of Java, so a server running its own trusted code is not exposed

9 osv-maven no match An OSV.dev record of this CVE affecting a package published to Maven Central. When every such package is one business applications do not use (Minecraft mods and launchers, Fastjson) and no tracked product is named by CPE, it settles the CVE as Outside Waratek scope instead

10 cna-maven-package no match An affected Maven artifact named by the CNA itself

11 known-cpe-product matched In scope Matches known products: apache/tomcat

12 cna-cpe-product not reached A CPE the CNA published naming a tracked product. Oracle publishes these on advisory day, months before NVD.

13 oracle-advisory-family not reached A tracked product family named in Oracle's own risk matrix. CPE cannot carry a suite name, only a module.

14 cna-named-product not reached A tracked product named in words by the CVE's own CNA, on a record with no CPE yet. Apache and Eclipse publish these on advisory day, before NVD adds CPE data.

15 non-deployable-product not reached The only affected product being a sealed appliance image, where Java runs but no -javaagent can be attached

16 unmatched-product not reached No tracked product matched above, and none present at all

disposition: What do we do about one that is? every rule runs

17 patch-hint no match A reference pointing at the upstream fix: a commit, a PR, a Red Hat bug

18 open-source-maven no match The affected package being open source on Maven, so the fix can be read

19 poc-derivable decided it matched Mitigation candidate 2 public PoC(s) indexed in exploit-db, nuclei, with no public source. The exploit is a starting point for deriving an ARMR patch rule by reverse engineering; nothing here establishes a hook point exists.

20 no-exploit skipped Nothing to build a rule from yet: no published exploit, no CISA record of exploitation and no source-level change to read

21 secure-rule-match no match A vulnerability class already blocked by an ARMR security rule

22 exploited-no-fix-or-poc skipped Somebody exploiting this CVE (a CISA or VulnCheck KEV listing, or a CISA verdict of active exploitation), with no fix, source code or PoC to build a rule from

23 below-action-threshold withheld Has 2 known POC(s) clearing the evidence bar — requires review despite MEDIUM severity

24 no-exploit-published no match A CISA or VulnCheck KEV listing, a CISA verdict of active exploitation, a reviewed exploit catalogue, or a GitHub PoC with 5 or more stars carries this CVE — exploit code is in use or published, so it stays a candidate

Products the scope rules checked

The products this CVE's record names, and whether VRT tracks each one. The scope rules decided on these.

Vendor Product Tracked CPE Source

apache tomcat tracked cpe:2.3:a:apache:tomcat:3.0:*:*:*:*:*:*:* yaml

NVD ↗ · CVE.org ↗