CVE-2002-0392

HIGHCVSS v2 · 7.57.5—
EchelonGraph scoreLOW confidence

This CVE was only ever scored under CVSS v2.0. NVD CVSS v2.0 base 7.5 — v2 rates that HIGH (v2 bands: LOW 0.0–3.9 / MEDIUM 4.0–6.9 / HIGH 7.0–10.0; v2 has no CRITICAL band). Vector AV:N/AC:L/Au:N/C:P/I:P/A:P. CVSS v2 is an older, coarser metric than v3.1/v4.0 (no Scope, no User Interaction, no Attack Requirements), so it is not directly comparable to a v3 or v4 score. NVD has never re-scored this record under v3. EPSS predicts 95.0% exploitation probability in the next 30 days, which is reflected in EG Risk but does not lift the v2 base. Confidence: LOW.

Sources: epss, nvd_v2
Weaponized
7.5EG
EchelonGraph verdictPatch this weekExploitation is likely or a public exploit exists.
  • 2 internet-exposed hosts are running an affected version right now
  • High exploitation likelihood — EPSS 95%
  • Public exploit code is available (Metasploit, Exploit-DB (verified), epss top5pct, epss high, public exploit)
CISA-KEV: Not listedEPSS PROB: 95%CVSS v2: 7.5Exploit: Metasploit · Exploit-DB (verified) · epss top5pct · epss high · public exploitExposed: 2

A fix is available — apply it.

Apache 1.3 through 1.3.24, and Apache 2.0 through 2.0.36, allows remote attackers to cause a denial of service and possibly execute arbitrary code via a chunk-encoded HTTP request that causes Apache to use an incorrect size.

Live · internet exposure

2 internet-exposed hosts are running an affected version of CVE-2002-0392 right now.

across 2 countries (China, Taiwan)top: http_server
See the live KEV-Exposure radar →Found passively from public internet-scan data — aggregate, host-redacted.

EchelonGraph is the only CVE feed that fuses live vulnerability intelligence with its own live internet-exposure radar — so you see not just that a CVE is exploited, but how much of the internet is exposed to it right now.

CVSS v2.0 (legacy)
7.5HIGHNVD never assigned a CVSS v3 rating to this CVE
EG Score
7.5(low)
EG Risk
76(Track)
EG Risk 76/100SSVC: Track

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity75% × 45%
Exploitation95% × 40%
Automatability30% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
95%
EPSS %ILE
100%
KEV
Not listed

Published

July 3, 2002

Last Modified

June 16, 2026

References (90)

Patch Availability(6)

Vendor / EcosystemFixed in / PatchReleasedSource
redhatpatch2003-04-22redhat
redhatpatch2002-07-31redhat
redhatpatch2002-07-12redhat
redhatpatch2002-06-30redhat
redhatpatch2002-06-20redhat
redhatpatch2002-06-19redhat

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

Affected Packages

(4 across 4 ecosystems)
Debian:11(1)
PackageVulnerable rangeFixed inDependents
apache2—2.0.37—
Debian:12(1)
PackageVulnerable rangeFixed inDependents
apache2—2.0.37—
Debian:13(1)
PackageVulnerable rangeFixed inDependents
apache2—2.0.37—
Debian:14(1)
PackageVulnerable rangeFixed inDependents
apache2—2.0.37—

All Vendor Advisories

(6)

Every vendor that published an advisory referencing this CVE — pulled from our cve_vendor_advisories aggregation. Click any row for the vendor's original advisory page.

Data Freshness Timeline

(refreshed 0× in last 7d / 1× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

  1. 2026-09-12 05:40 UTCOSV refresh
  2. 2026-08-24 11:12 UTCOSV refresh
  3. 2026-08-08 07:26 UTCOSV refresh
  4. 2026-07-26 13:21 UTCEG score recompute▲ 7.50
  5. 2026-07-23 00:44 UTCEG score recompute
  6. 2026-07-23 00:30 UTCVendor advisory
  7. 2026-07-23 00:30 UTCGHSA enrichment
  8. 2026-07-23 00:27 UTCVendor advisory
  9. 2026-07-23 00:27 UTCGHSA enrichment
  10. 2026-07-23 00:26 UTCVendor advisory
  11. 2026-07-23 00:25 UTCGHSA enrichment
  12. 2026-07-23 00:25 UTCEG score recompute▼ 9.00
  13. 2026-07-22 23:48 UTCEG score recompute
  14. 2026-07-22 21:21 UTCEG score recompute▲ 9.00
  15. 2026-07-22 21:21 UTCVendor advisory
  16. 2026-07-22 21:21 UTCGHSA enrichment
  17. 2026-07-16 16:58 UTCEPSS rescore
  18. 2026-07-09 13:46 UTCOSV refresh
  19. 2026-06-29 14:02 UTCEPSS rescore
  20. 2026-06-24 14:01 UTCEPSS rescore
  21. 2026-06-23 21:29 UTCEPSS rescore
  22. 2026-06-22 14:22 UTCEPSS rescore
  23. 2026-06-21 02:16 UTCOSV refresh
  24. 2026-06-21 01:56 UTCEPSS rescore
  25. 2026-06-14 23:13 UTCEPSS rescore
Show 31 more
  1. 2026-06-13 22:56 UTCEPSS rescore
  2. 2026-06-12 23:07 UTCEPSS rescore
  3. 2026-06-11 13:55 UTCEPSS rescore
  4. 2026-06-10 22:13 UTCEPSS rescore
  5. 2026-06-08 14:13 UTCEPSS rescore
  6. 2026-06-05 06:07 UTCEPSS rescore
  7. 2026-06-04 13:09 UTCEPSS rescore
  8. 2026-06-02 20:10 UTCEPSS rescore
  9. 2026-05-31 22:27 UTCEPSS rescore
  10. 2026-05-31 19:22 UTCEG score recompute
  11. 2026-05-31 19:22 UTCVendor advisory
  12. 2026-05-31 19:22 UTCGHSA enrichment
  13. 2026-05-31 00:13 UTCEPSS rescore
  14. 2026-05-31 00:13 UTCEPSS rescore
  15. 2026-05-29 13:40 UTCEPSS rescore
  16. 2026-05-28 13:42 UTCEPSS rescore
  17. 2026-05-28 13:42 UTCEPSS rescore
  18. 2026-05-28 13:42 UTCEPSS rescore
  19. 2026-05-28 13:42 UTCEPSS rescore
  20. 2026-05-27 13:37 UTCEPSS rescore
  21. 2026-05-27 13:37 UTCEPSS rescore
  22. 2026-05-26 07:16 UTCEPSS rescore
  23. 2026-05-26 07:16 UTCEPSS rescore
  24. 2026-05-23 00:37 UTCOSV refresh
  25. 2026-05-22 21:15 UTCEPSS rescore
  26. 2026-05-21 22:38 UTCEPSS rescore
  27. 2026-05-20 22:36 UTCEPSS rescore
  28. 2026-05-20 11:20 UTCEPSS rescore
  29. 2026-05-20 11:20 UTCEPSS rescore
  30. 2026-05-18 21:29 UTCEPSS rescore
  31. 2026-05-18 21:29 UTCEPSS rescore

Publicly available exploits

(4 references)

Working exploit code is in the public domain (1 Metasploit module) (3 Exploit-DB entries). Defenders should treat patch urgency accordingly — public PoCs typically lead to mass-exploitation within 24-72 hours.

  • Exploit-DBEDB-16782✓ verified
    First seen Jul 7, 2010

    Apache (Windows x86) - Chunked Encoding (Metasploit)

    Open source ↗
  • Metasploitexploit/windows/http/apache_chunked✓ verified
    First seen Jun 19, 2002

    Apache Win32 Chunked Encoding

    Open source ↗
  • Exploit-DBEDB-21559✓ verified
    First seen Jun 17, 2002

    Apache 1.x/2.0.x - Chunked-Encoding Memory Corruption (1)

    Open source ↗
  • Exploit-DBEDB-21560✓ verified
    First seen Jun 17, 2002

    Apache 1.x/2.0.x - Chunked-Encoding Memory Corruption (2)

    Open source ↗

Related CVEs(same product + same vendor)

Frequently asked(4)

What is CVE-2002-0392?
CVE-2002-0392 is a high vulnerability published on July 3, 2002. Apache 1.3 through 1.3.24, and Apache 2.0 through 2.0.36, allows remote attackers to cause a denial of service and possibly execute arbitrary code via a chunk-encoded HTTP request that causes Apache to use an incorrect size.
When was CVE-2002-0392 disclosed?
CVE-2002-0392 was first published in the National Vulnerability Database on July 3, 2002, with the most recent update on June 16, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2002-0392 actively exploited?
CVE-2002-0392 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 95% probability of exploitation in the next 30 days, which ranks it in the top 0.1% of all scored CVEs.
How do I remediate CVE-2002-0392?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2002-0392, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2002-0392

Explore →

Is Your Infrastructure Affected by CVE-2002-0392?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Book a Demo →Browse All CVEs