`CVE-2000-0652`

5.0 Medium Mitigation candidate

Description

IBM WebSphere allows remote attackers to read source code for executable web files by directly calling the default InvokerServlet using a URL which contains the "/servlet/file" string.

Exploitation Status

Working exploit published

A reviewed exploit catalogue carries this CVE. Somebody has published code a stranger can run.

CVSS E:P

CISA KEV not listed
CISA Vulnrichment no assessment published
Indexed PoC 1 indexed Published artifacts you can open, in Exploit-DB; first seen 2000-07-24.
EPSS 8.0% chance in 30 days

Index	Artifact	Stars	First seen
Exploit-DB	IBM Websphere Application Server 2.0./3.0/3.0.2.1 - Showcode		2000-07-24

Index

Artifact

Stars

First seen

Exploit-DB

IBM Websphere Application Server 2.0./3.0/3.0.2.1 - Showcode

2000-07-24

Waratek Defense Posture

Mitigation candidate

A defect of the type ARMR addresses, with a fix path to work from and a working exploit already published. This is a claim on attention, not a scheduling commitment: no rule exists and none is scheduled.

Protection none
Action unverified patch rule
Review automated inferred
Record active

Decided by poc-derivable : An indexed exploit to reverse-engineer, where there is no source to read

Finding Promoted to MITIGATION-CANDIDATE: 1 public proof-of-concept exploit(s) are indexed for this CVE (exploit-db), 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	`poc-derivable` : An indexed exploit to reverse-engineer, where there is no source to read
Finding	Promoted to MITIGATION-CANDIDATE: 1 public proof-of-concept exploit(s) are indexed for this CVE (exploit-db), 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.

CVSS

5.0 v2.0 AV:N/AC:L/Au:N/C:P/I:N/A:N 1 metric

VRT selects the newest version's highest entry and publishes it as cvssScore, newest rather than largest because scores are not comparable across versions, and highest rather than first because the first entry is frequently a CNA placeholder scoring 0.0 over NVD's own analysis.

Version Score Band Vector Assigner Type

CVSS 2.0 5.0 no band published AV:N/AC:L/Au:N/C:P/I:N/A:N NVD Primary published

Version	Score	Band	Vector	Assigner	Type
CVSS 2.0	5.0	no band published	`AV:N/AC:L/Au:N/C:P/I:N/A:N`	NVD	Primary	published

Affected Software & Releases

🖥️ Product CPEs & Version Ranges

1 product(s) over 3 version claims (uncapped)

Source	Vendor	Product	Scheme	Affected Versions
nvd	ibm	websphere application server	generic	2.0 · 3.0 · 3.0.21

Source

Vendor

Product

Scheme

Affected Versions

nvd

ibm

websphere application server

generic

2.0 · 3.0 · 3.0.21

References

URL	Tags
http://archives.neohapsis.com/archives/bugtraq/2000-07/0342.html	Exploit, Patch, Vendor Advisory
http://www.securityfocus.com/bid/1500	Exploit, Patch, Vendor Advisory
https://exchange.xforce.ibmcloud.com/vulnerabilities/5012

URL

Timeline

Published 2000-07-24 Last modified 2026-06-16

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

Published

2000-07-24

By the CVE Program.

NVD record modified

2026-06-16

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

Pipeline policy audit (17 of 21 rules evaluated)

17 of 21 rules ran. The rest were never reached, because an earlier stage settled the CVE, a distinct claim from a rule that ran and found nothing.

# Rule Outcome Status Detail

identity: Does this identifier describe a vulnerability at all? first match wins

1 rejected no-match CVE Program withdrawal of this identifier

scope: Is the vulnerability ARMR's to address? first match wins

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 native WebLogic proxy plug-in. Oracle gives these no CPE of their own and names them only in the description.

8 osv-maven no-match An OSV.dev record of this CVE affecting a package published to Maven Central

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

10 known-cpe-product matched Queued for review Matches known products: ibm/websphere_application_server

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

12 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.

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

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

disposition: What do we do about one that is? cumulative: every rule gets a turn

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

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

17 poc-derivable decided it matched Mitigation candidate 1 public PoC(s) indexed in exploit-db, 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.

18 no-exploit skipped With no fix path, a public exploit, or a CISA record of one

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

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

21 no-exploit-published no-match A KEV listing, a CISA verdict of active exploitation, or a reviewed exploit catalogue carries this CVE — somebody has published a working exploit, so it stays a candidate

What the scope rules read

The products the record named, and whether known-products.yaml tracks them. This is the evidence the scope stage decided on.

Vendor Product Tracked CPE Source

ibm websphere_application_server tracked cpe:2.3:a:ibm:websphere_application_server:2.0:*:*:*:*:*:*:* yaml

Raw stored JSON document for this CVE ↗ · NVD ↗ · CVE.org ↗