CVE-2001-0609

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: 18%CVSS: 9.8Exploit: NoneExposed: 0

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

Format string vulnerability in Infodrom cfingerd 1.4.3 and earlier allows a remote attacker to gain additional privileges via a malformed ident reply that is passed to the syslog function.

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

Published

August 2, 2001

Last Modified

June 16, 2026

Advisory Details (2)

Auto-updated Jun 21, 2026
No patch confirmed yet.
generic

IBM X-Force Exchange

https://exchange.xforce.ibmcloud.com/vulnerabilities/6364
generic
http://www.securityfocus.com/bid/2576

Weakness Classification(1)

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

Data Freshness Timeline

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

Publicly available exploits

(2 references)

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

  • Exploit-DBEDB-20749✓ verified
    First seen Apr 16, 2001

    cfingerd 1.4 - Format String (2)

    Open source ↗
  • Exploit-DBEDB-20748✓ verified
    First seen Apr 11, 2001

    cfingerd 1.4 - Format String (1)

    Open source ↗

Frequently asked(5)

What is CVE-2001-0609?
CVE-2001-0609 is a critical vulnerability published on August 2, 2001. Format string vulnerability in Infodrom cfingerd 1.4.3 and earlier allows a remote attacker to gain additional privileges via a malformed ident reply that is passed to the syslog function.
When was CVE-2001-0609 disclosed?
CVE-2001-0609 was first published in the National Vulnerability Database on August 2, 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-0609 actively exploited?
CVE-2001-0609 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 96.9% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2001-0609?
CVE-2001-0609 has a CVSS v3 base score of 9.8 (NVD).
How do I remediate CVE-2001-0609?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2001-0609, 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-0609

Explore →

Is Your Infrastructure Affected by CVE-2001-0609?

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

Start Free Scan →Browse All CVEs