CVE-2001-0830

HIGHNVD 7.57.5—
EchelonGraph scoreMEDIUM confidence

This high-severity CVE scores 7.5 under NVD CVSS v3. EPSS exploit probability: 9.0%, top 7% of all CVEs by exploit prediction. GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).

Triggered by: NVD CVSS baseline
Sources: epss, nvd
Weaponized
7.5
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS: 6%CVSS: 7.5Exploit: NoneExposed: 0

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

6tunnel 0.08 and earlier does not properly close sockets that were initiated by a client, which allows remote attackers to cause a denial of service (resource exhaustion) by repeatedly connecting to and disconnecting from the server.

CVSS v3
7.5
EG Score
7.5(medium)
EPSS
92.1%
KEV
Not listed

Published

December 6, 2001

Last Modified

June 16, 2026

Advisory Details (3)

Auto-updated May 31, 2026
No patch confirmed yet.
generic

IBM X-Force Exchange

https://exchange.xforce.ibmcloud.com/vulnerabilities/7337
generic
http://www.securityfocus.com/bid/3467
generic

'Remote DoS in 6tunnel' - MARC

http://marc.info/?l=bugtraq&m=100386451702966&w=2

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 4× in last 7d / 18× 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-15 16:53 UTCEPSS rescore
  2. 2026-07-15 01:55 UTCEPSS rescore
  3. 2026-07-13 06:07 UTCEPSS rescore
  4. 2026-07-11 08:22 UTCEPSS rescore
  5. 2026-07-08 15:08 UTCEPSS rescore
  6. 2026-07-04 06:26 UTCEPSS rescore
  7. 2026-07-02 14:00 UTCEPSS rescore
  8. 2026-06-29 14:02 UTCEPSS rescore
  9. 2026-06-27 03:04 UTCEPSS rescore
  10. 2026-06-24 14:01 UTCEPSS rescore
  11. 2026-06-23 21:29 UTCEPSS rescore
  12. 2026-06-22 14:22 UTCEPSS rescore
  13. 2026-06-21 01:56 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-16 17:49 UTCEPSS rescore
  19. 2026-06-13 22:56 UTCEPSS rescore
  20. 2026-06-12 23:07 UTCEPSS rescore
  21. 2026-06-11 13:55 UTCEPSS rescore
  22. 2026-06-10 22:13 UTCEPSS rescore
  23. 2026-06-10 13:17 UTCEPSS rescore
  24. 2026-06-08 14:13 UTCEPSS rescore
  25. 2026-06-07 15:21 UTCEPSS rescore
Show 28 more
  1. 2026-06-06 13:44 UTCEPSS rescore
  2. 2026-06-05 06:07 UTCEPSS rescore
  3. 2026-06-04 13:09 UTCEPSS rescore
  4. 2026-06-02 20:10 UTCEPSS rescore
  5. 2026-06-01 13:48 UTCEPSS rescore
  6. 2026-05-31 22:27 UTCEPSS rescore
  7. 2026-05-31 19:53 UTCEG score recompute
  8. 2026-05-31 19:53 UTCGHSA enrichment
  9. 2026-05-31 00:13 UTCEPSS rescore
  10. 2026-05-31 00:13 UTCEPSS rescore
  11. 2026-05-29 13:40 UTCEPSS rescore
  12. 2026-05-28 13:42 UTCEPSS rescore
  13. 2026-05-28 13:42 UTCEPSS rescore
  14. 2026-05-28 13:42 UTCEPSS rescore
  15. 2026-05-28 13:42 UTCEPSS rescore
  16. 2026-05-27 13:37 UTCEPSS rescore
  17. 2026-05-27 13:37 UTCEPSS rescore
  18. 2026-05-26 13:41 UTCEPSS rescore
  19. 2026-05-26 13:41 UTCEPSS rescore
  20. 2026-05-26 13:41 UTCEPSS rescore
  21. 2026-05-24 16:42 UTCEPSS rescore
  22. 2026-05-22 21:15 UTCEPSS rescore
  23. 2026-05-21 22:38 UTCEPSS rescore
  24. 2026-05-20 22:36 UTCEPSS rescore
  25. 2026-05-20 11:20 UTCEPSS rescore
  26. 2026-05-20 11:20 UTCEPSS rescore
  27. 2026-05-18 21:29 UTCEPSS rescore
  28. 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-21126✓ verified
    First seen Oct 23, 2001

    6Tunnel 0.6/0.7/0.8 - Connection Close State Denial of Service

    Open source ↗

Frequently asked(5)

What is CVE-2001-0830?
CVE-2001-0830 is a high vulnerability published on December 6, 2001. 6tunnel 0.08 and earlier does not properly close sockets that were initiated by a client, which allows remote attackers to cause a denial of service (resource exhaustion) by repeatedly connecting to and disconnecting from the server.
When was CVE-2001-0830 disclosed?
CVE-2001-0830 was first published in the National Vulnerability Database on December 6, 2001, 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-2001-0830 actively exploited?
CVE-2001-0830 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 92.1% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2001-0830?
CVE-2001-0830 has a CVSS v3 base score of 7.5 (NVD).
How do I remediate CVE-2001-0830?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2001-0830, 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-2001-0830

Explore →

Is Your Infrastructure Affected by CVE-2001-0830?

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

Start Free Scan →Browse All CVEs