CVE-2001-1339

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

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

Beck IPC GmbH IPC@CHIP telnet service does not delay or disconnect users from the service when bad passwords are entered, which makes it easier for remote attackers to conduct brute force password guessing attacks.

CVSS v3
9.8
EG Score
9.8(medium)
EG Risk
75(Track*)
EG Risk 75/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
Severity98% × 45%
Exploitation65% × 40%
Automatability30% × 15%
Action: Watch closely — could escalate to Attend.
EPSS
93.8%
KEV
Not listed

Published

May 24, 2001

Last Modified

June 16, 2026

Advisory Details (3)

Auto-updated Jun 20, 2026
No patch confirmed yet. Sources: cert.
generic
http://www.securityfocus.com/bid/2771
generic
http://www.securityfocus.com/archive/1/186418
cert

VU#198979 - Beck GmbH IPC@Chip TelnetD vulnerable to brute-force password attack

http://www.kb.cert.org/vuls/id/198979

Weakness Classification(1)

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

Data Freshness Timeline

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

    Beck IPC GmbH IPC@CHIP - TelnetD Login Account Brute Force

    Open source ↗

Frequently asked(5)

What is CVE-2001-1339?
CVE-2001-1339 is a critical vulnerability published on May 24, 2001. Beck IPC GmbH IPC@CHIP telnet service does not delay or disconnect users from the service when bad passwords are entered, which makes it easier for remote attackers to conduct brute force password guessing attacks.
When was CVE-2001-1339 disclosed?
CVE-2001-1339 was first published in the National Vulnerability Database on May 24, 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-1339 actively exploited?
CVE-2001-1339 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 93.8% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2001-1339?
CVE-2001-1339 has a CVSS v3 base score of 9.8 (NVD).
How do I remediate CVE-2001-1339?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2001-1339, 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-1339

Explore →

Is Your Infrastructure Affected by CVE-2001-1339?

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

Start Free Scan →Browse All CVEs