CVE-2002-1816

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.8EG
EchelonGraph verdictMitigate this weekExploitation is likely or a public exploit exists.
  • Public exploit code is available (Exploit-DB (verified), epss top5pct, public exploit)
CISA-KEV: Not listedEPSS PROB: 9.0%CVSS: 9.8Exploit: Exploit-DB (verified) · epss top5pct · public exploitExposed services: Not assessed

A fix is referenced (a reference tagged "Patch", often a source commit), but no release containing it is confirmed — find the release that contains it; until it is applied, mitigate (WAF / firewall / segmentation).

Off-by-one buffer overflow in the sock_gets function in sockhelp.c for ATPhttpd 0.4b and earlier allows remote attackers to execute arbitrary code via a long HTTP GET request.

CVSS v3
9.8
EG Score
9.8CRITICALmedium confidence
EG Risk
85
EG Risk 85/100CISA SSVC

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
Severity98% × 45%
Exploitation65% × 40%
Automatability100% × 15%
CISA SSVC: Track at low or medium mission impact; Attend at high (mission-essential systems).
Action: A fix is referenced, but no release containing it is confirmed. Check the referenced fix and the vendor's advisory for a release that contains it and apply that within your standard update timelines at low or medium mission impact and sooner than that at high; until then, restrict network exposure of the affected system or apply the vendor's mitigation.
EPSS PROB
9.0%
EPSS %ILE
95th
KEV
Not listed

CISA SSVCTrack at low or medium mission impact; Attend at high (mission-essential systems).

A fix is referenced, but no release containing it is confirmed. Check the referenced fix and the vendor's advisory for a release that contains it and apply that within your standard update timelines at low or medium mission impact and sooner than that at high; until then, restrict network exposure of the affected system or apply the vendor's mitigation.

Exploitation none (CISA Vulnrichment) · Automatable yes (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). Mission impact is CISA's Mission & Well-being decision point, and only you can judge it: high means the affected system is essential to your organisation's mission, or its compromise could cause irreversible harm to people. CISA's decision table

Published

December 31, 2002

Last Modified

June 16, 2026

Advisory Details (2)

Auto-updated Oct 8, 2026
Fix referenced — no release confirmed yet.
generic

CVE-2002-1816 - PSIRT.COM

http://www.securityfocus.com/bid/5956
generic

Secunia Research & Vulnerability Insights | Flexera

http://secunia.com/advisories/7293

Weakness Classification(1)

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

Data Freshness Timeline

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

    ATP HTTPd 0.4 - Single Byte Buffer Overflow

    Open source ↗

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2002-1816?
CVE-2002-1816 is a critical vulnerability published on December 31, 2002. Off-by-one buffer overflow in the sock_gets function in sockhelp.c for ATPhttpd 0.4b and earlier allows remote attackers to execute arbitrary code via a long HTTP GET request.
When was CVE-2002-1816 disclosed?
CVE-2002-1816 was first published on December 31, 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-1816 actively exploited?
CVE-2002-1816 is not currently on CISA's Known Exploited Vulnerabilities catalog. EchelonGraph's EG-KEV model classifies it as weaponized: a functional public exploit exists. FIRST EPSS estimates a 9.0% probability of exploitation in the next 30 days (95th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2002-1816?
CVE-2002-1816 has a CVSS v3 base score of 9.8 (NVD).
How do I remediate CVE-2002-1816?
A fix for CVE-2002-1816 is referenced (a reference tagged "Patch", often a source commit), but EchelonGraph has no release containing it on record. Check that reference and the vendor's advisory for a release that contains the fix and update to it; until then, restrict network exposure of the affected system or apply the vendor's mitigation.

Dependency Blast Radius

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

Explore →

Is Your Infrastructure Affected by CVE-2002-1816?

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

Book a Demo →Browse All CVEs