CVE-2002-1484

CRITICALNVD 9.89.8—
EchelonGraph scoreMEDIUM confidence

Score 9.8 from GitHub Security Advisory (severity: HIGH) published 2022-04-30. NVD baseline CVSS 9.8; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, nvd
Weaponized
9.8
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS: 14%CVSS: 9.8Exploit: NoneExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

DB4Web server, when configured to use verbose debug messages, allows remote attackers to use DB4Web as a proxy and attempt TCP connections to other systems (port scan) via a request for a URL that specifies the target IP address and port, which produces a connection status in the resulting error message.

CVSS v3
9.8
EG Score
9.8(medium)
EPSS
96.0%
KEV
Not listed

Published

April 22, 2003

Last Modified

June 16, 2026

Advisory Details (1)

Auto-updated Jun 23, 2026
No patch confirmed yet.
generic
http://www.securityfocus.com/bid/5725

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 3× in last 7d / 23× 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-07-11 08:22 UTCEPSS rescore
  2. 2026-07-11 08:22 UTCEPSS rescore
  3. 2026-07-08 15:09 UTCEPSS rescore
  4. 2026-07-06 02:19 UTCEPSS rescore
  5. 2026-07-04 06:26 UTCEPSS rescore
  6. 2026-07-02 14:00 UTCEPSS rescore
  7. 2026-06-29 14:02 UTCEPSS rescore
  8. 2026-06-29 14:02 UTCEPSS rescore
  9. 2026-06-28 04:52 UTCEPSS rescore
  10. 2026-06-27 03:04 UTCEPSS rescore
  11. 2026-06-23 21:29 UTCEPSS rescore
  12. 2026-06-21 01:56 UTCEPSS rescore
  13. 2026-06-19 19:22 UTCEPSS rescore
  14. 2026-06-19 19:22 UTCEPSS rescore
  15. 2026-06-18 17:49 UTCEPSS rescore
  16. 2026-06-18 17:49 UTCEPSS rescore
  17. 2026-06-17 17:49 UTCEPSS rescore
  18. 2026-06-17 17:49 UTCEPSS rescore
  19. 2026-06-16 17:49 UTCEPSS rescore
  20. 2026-06-16 17:49 UTCEPSS rescore
  21. 2026-06-15 17:43 UTCEPSS rescore
  22. 2026-06-14 23:13 UTCEPSS rescore
  23. 2026-06-14 23:13 UTCEPSS rescore
  24. 2026-06-13 22:56 UTCEPSS rescore
  25. 2026-06-12 23:08 UTCEPSS rescore
Show 50 more
  1. 2026-06-11 13:55 UTCEPSS rescore
  2. 2026-06-10 22:13 UTCEPSS rescore
  3. 2026-06-10 13:17 UTCEPSS rescore
  4. 2026-06-07 15:21 UTCEPSS rescore
  5. 2026-06-06 13:44 UTCEPSS rescore
  6. 2026-06-06 13:44 UTCEPSS rescore
  7. 2026-06-06 13:44 UTCEPSS rescore
  8. 2026-06-05 22:43 UTCEPSS rescore
  9. 2026-06-05 22:43 UTCEPSS rescore
  10. 2026-06-05 06:07 UTCEPSS rescore
  11. 2026-06-04 13:09 UTCEPSS rescore
  12. 2026-06-02 20:10 UTCEPSS rescore
  13. 2026-06-01 13:49 UTCEPSS rescore
  14. 2026-06-01 13:49 UTCEPSS rescore
  15. 2026-05-31 22:28 UTCEPSS rescore
  16. 2026-05-31 00:13 UTCEPSS rescore
  17. 2026-05-31 00:13 UTCEPSS rescore
  18. 2026-05-29 13:40 UTCEPSS rescore
  19. 2026-05-29 13:40 UTCEPSS rescore
  20. 2026-05-28 13:42 UTCEPSS rescore
  21. 2026-05-28 13:42 UTCEPSS rescore
  22. 2026-05-28 13:42 UTCEPSS rescore
  23. 2026-05-27 13:37 UTCEPSS rescore
  24. 2026-05-26 13:41 UTCEPSS rescore
  25. 2026-05-26 13:41 UTCEPSS rescore
  26. 2026-05-26 07:16 UTCEPSS rescore
  27. 2026-05-26 07:16 UTCEPSS rescore
  28. 2026-05-24 16:42 UTCEPSS rescore
  29. 2026-05-22 21:15 UTCEPSS rescore
  30. 2026-05-20 22:36 UTCEPSS rescore
  31. 2026-05-20 11:20 UTCEPSS rescore
  32. 2026-05-20 11:20 UTCEPSS rescore
  33. 2026-05-20 08:29 UTCEG score recompute
  34. 2026-05-20 08:29 UTCGHSA enrichment
  35. 2026-05-20 04:05 UTCEG score recompute
  36. 2026-05-20 04:05 UTCGHSA enrichment
  37. 2026-05-19 23:41 UTCEG score recompute
  38. 2026-05-19 23:41 UTCGHSA enrichment
  39. 2026-05-19 19:21 UTCEG score recompute
  40. 2026-05-19 19:21 UTCGHSA enrichment
  41. 2026-05-19 15:01 UTCEG score recompute
  42. 2026-05-19 15:01 UTCGHSA enrichment
  43. 2026-05-19 10:41 UTCEG score recompute
  44. 2026-05-19 10:41 UTCGHSA enrichment
  45. 2026-05-19 06:20 UTCEG score recompute
  46. 2026-05-19 06:20 UTCGHSA enrichment
  47. 2026-05-19 02:00 UTCEG score recompute
  48. 2026-05-19 02:00 UTCGHSA enrichment
  49. 2026-05-18 21:29 UTCEPSS rescore
  50. 2026-05-18 21:29 UTCEPSS rescore

Publicly available exploits

(1 reference)

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

  • Exploit-DBEDB-21801✓ verified
    First seen Sep 17, 2002

    DB4Web 3.4/3.6 - Connection Proxy

    Open source ↗

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2002-1484?
CVE-2002-1484 is a critical vulnerability published on April 22, 2003. DB4Web server, when configured to use verbose debug messages, allows remote attackers to use DB4Web as a proxy and attempt TCP connections to other systems (port scan) via a request for a URL that specifies the target IP address and port, which produces a connection status in the resulting error…
When was CVE-2002-1484 disclosed?
CVE-2002-1484 was first published in the National Vulnerability Database on April 22, 2003, 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-1484 actively exploited?
CVE-2002-1484 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 96.0% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2002-1484?
CVE-2002-1484 has a CVSS v3 base score of 9.8 (NVD).
How do I remediate CVE-2002-1484?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2002-1484, 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

Explore the affected products and dependency analysis for CVE-2002-1484

Explore →

Is Your Infrastructure Affected by CVE-2002-1484?

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

Start Free Scan →Browse All CVEs