CVE-2000-1221

HIGHCVSS v2 · 10.010.0
EchelonGraph scoreLOW confidence

“—” beside the score: it is equal to NVD's CVSS v2 base score.

This CVE was only ever scored under CVSS v2.0. NVD CVSS v2.0 base 10.0 — NVD rates that HIGH (NVD's v2 bands: LOW 0.0–3.9 / MEDIUM 4.0–6.9 / HIGH 7.0–10.0; no CRITICAL band). Vector AV:N/AC:L/Au:N/C:C/I:C/A:C. CVSS v2 is an older, coarser metric than v3.1/v4.0 (no Scope, no User Interaction, no Attack Requirements), so it is not directly comparable to a v3 or v4 score. NVD has never re-scored this record under v3. EPSS predicts 17% exploitation probability in the next 30 days; it does not lift the v2 base. EchelonGraph's fixed weight for EG-KEV Tier 2 (Weaponized) sets EG Risk's exploitation input, not EPSS. Confidence: LOW.

Triggered by: NVD CVSS v2.0 (legacy fallback)
Sources: NVD CVSS v2.0
Trending — 3 sources updated this weekWeaponized
10.0EG
EchelonGraph verdictPlan a fixRemediate within your standard update timelines at low or medium mission impact and sooner than that at high (the SSVC decision on this page).
  • Public exploit code is available (Exploit-DB, marked verified by Exploit-DB)
CISA-KEV: Not listedEPSS PROB: 17%CVSS v2: 10.0Exploit: Exploit-DB (verified)Exposed services: Not assessed

A fix is available — apply it.

The line printer daemon (lpd) in the lpr package in multiple Linux operating systems authenticates by comparing the reverse-resolved hostname of the local machine to the hostname of the print server as returned by gethostname, which allows remote attackers to bypass intended access controls by modifying the DNS for the attacking IP.

CVSS v2.0 (legacy)
10.0HIGHNVD never assigned a CVSS v3 rating to this CVE
EG Score
10.0HIGHlow confidence
EG Risk
71
EG Risk 71/100

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 (value × EchelonGraph’s weight)
Severity100% × 45%
The EG Score, 10.0 of 10.
Exploitation65% × 40%
EchelonGraph's fixed weight for EG-KEV Tier 2 (Weaponized): a constant, not a probability.
Automatability0% × 15%
CISA's BOD 26-04 default: no one has published Automatable for this CVE, and CISA treats it as “no” for a CVE not in KEV.
SSVC (CISA's decision table, applied by EchelonGraph): Track at low, Track* at medium and Attend at high mission impact.
Exploitation public PoC (exploit code on record) · Automatable no (CISA's BOD 26-04 default) · Technical impact total (CISA's BOD 26-04 default). EchelonGraph holds no SSVC assessment of this CVE from CISA: none of these inputs is from Vulnrichment. EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE.
Action: A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.
EPSS PROB
17%
EPSS %ILE
96th
KEV
Not listed

SSVC (CISA's decision table, applied by EchelonGraph)Track at low, Track* at medium and Attend at high mission impact.

A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.

Exploitation public PoC (exploit code on record) · Automatable no (CISA's BOD 26-04 default) · Technical impact total (CISA's BOD 26-04 default). EchelonGraph holds no SSVC assessment of this CVE from CISA: none of these inputs is from Vulnrichment. EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE. Mission impact is CISA's Mission & Well-being decision point, and only you can judge it. CISA's table makes it high when Mission Prevalence is Essential — the vulnerable component "directly provides capabilities that constitute at least one MEF for at least one entity" (MEF: mission essential function) — or when Public Well-Being Impact is Irreversible: "multiple fatalities are likely", the cyber-physical system "is likely lost or destroyed", "extreme or serious externalities" are imposed on other parties, or social systems such as elections or the financial grid "are destabilized and potentially collapse". CISA's decision table

BOD 26-04 (CISA's remediation timeline, Table 1)14 days if the affected system is publicly exposed; Fix on system upgrade if it is not.

In CISA KEV no (CISA's KEV catalog) · Automatable no (CISA's BOD 26-04 default) · Technical impact total (CISA's BOD 26-04 default). Where an input reads “CISA's BOD 26-04 default”, no one has published it for this CVE, and CISA's implementation guidance says: “If “Automatable” and “Technical Impact” information items about a CVE ID are not available and the CVE ID is not in the KEV Catalog, CISA will treat its values as “no” and “total,” respectively, until CISA or a third party provides metadata about the CVE ID. CISA will always provide the Vulnrichment data for a CVE ID listed in the KEV Catalog.” Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it

Published

January 8, 2000

Last Modified

June 16, 2026

References (8)

Affected Packages

(4 across 4 ecosystems)
Debian:11(1)
PackageVulnerable rangeFix by version rangeDependents
lpr—
  • every version up to 1:0.48-1: fixed in 1:0.48-1
—
Debian:12(1)
PackageVulnerable rangeFix by version rangeDependents
lpr—
  • every version up to 1:0.48-1: fixed in 1:0.48-1
—
Debian:13(1)
PackageVulnerable rangeFix by version rangeDependents
lpr—
  • every version up to 1:0.48-1: fixed in 1:0.48-1
—
Debian:14(1)
PackageVulnerable rangeFix by version rangeDependents
lpr—
  • every version up to 1:0.48-1: fixed in 1:0.48-1
—

Data Freshness Timeline

(refreshed 9× in last 7d / 12× in last 30d)

Each row is a time one of our pipelines fetched, updated or re-scored this CVE. 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. An arrow marks a change the record states ("CVSS v3 → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). Most recent first.

A repeat, a row identical to one the same pipeline wrote less than 10 seconds earlier, is not a separate refresh and is not counted. 11 repeat rows among the latest 82 are merged into the row they repeat.

  1. 2026-10-12 02:30 UTCEG score recompute
  2. 2026-10-11 13:36 UTCEPSS rescoreEPSS 17% · 96th percentile
  3. 2026-10-10 19:53 UTCEPSS rescoreEPSS 17% · 96th percentile
  4. 2026-10-09 19:58 UTCEPSS rescoreEPSS 17% · 96th percentile
  5. 2026-10-08 16:26 UTCEPSS rescoreEPSS 17% · 96th percentile
  6. 2026-10-07 23:35 UTCEPSS rescoreEPSS 17% · 96th percentile
  7. 2026-10-06 15:07 UTCEPSS rescoreEPSS 17% · 96th percentile
  8. 2026-10-06 03:24 UTCOSV refresh
  9. 2026-10-05 17:36 UTCEPSS rescoreEPSS 17% · 96th percentile
  10. 2026-10-04 23:14 UTCEPSS rescoreEPSS 17% · 96th percentile
  11. 2026-09-29 02:31 UTCEG score recompute
  12. 2026-09-16 11:20 UTCOSV refresh
  13. 2026-09-04 04:59 UTCEPSS rescoreEPSS 17% · 96th percentile
  14. 2026-08-28 10:53 UTCOSV refresh
  15. 2026-08-11 23:32 UTCOSV refresh
  16. 2026-07-26 23:47 UTCOSV refresh
  17. 2026-07-26 13:20 UTCEG score recomputeFirst assessed: 10.0 HIGH
  18. 2026-07-23 00:42 UTCEG score recompute
  19. 2026-07-23 00:24 UTCEG score recompute
  20. 2026-07-22 23:47 UTCEG score recompute
  21. 2026-07-22 21:27 UTCEG score recompute
  22. 2026-07-20 17:02 UTCEPSS rescoreEPSS 17% · 96th percentile
  23. 2026-07-18 09:59 UTCEPSS rescoreEPSS 17% · 96th percentile
  24. 2026-07-16 16:58 UTCEPSS rescoreEPSS 17% · 96th percentile
  25. 2026-07-15 16:53 UTCEPSS rescoreEPSS 17% · 96th percentile
Show 46 more
  1. 2026-07-15 01:55 UTCEPSS rescoreEPSS 17% · 96th percentile
  2. 2026-07-13 06:07 UTCEPSS rescoreEPSS 17% · 96th percentile
  3. 2026-07-11 08:22 UTCEPSS rescoreEPSS 17% · 96th percentile
  4. 2026-07-09 18:15 UTCOSV refresh
  5. 2026-07-08 15:08 UTCEPSS rescoreEPSS 17% · 96th percentile
  6. 2026-07-02 14:00 UTCEPSS rescoreEPSS 17% · 96th percentile
  7. 2026-06-29 14:02 UTCEPSS rescoreEPSS 17% · 96th percentile
  8. 2026-06-28 14:02 UTCEPSS rescoreEPSS 17% · 96th percentile
  9. 2026-06-27 03:04 UTCEPSS rescoreEPSS 17% · 96th percentile
  10. 2026-06-24 14:01 UTCEPSS rescoreEPSS 17% · 96th percentile
  11. 2026-06-23 21:29 UTCEPSS rescoreEPSS 17% · 96th percentile
  12. 2026-06-22 14:22 UTCEPSS rescoreEPSS 17% · 96th percentile
  13. 2026-06-21 04:12 UTCOSV refresh
  14. 2026-06-21 01:56 UTCEPSS rescoreEPSS 17% · 96th percentile
  15. 2026-06-19 19:22 UTCEPSS rescoreEPSS 17% · 96th percentile
  16. 2026-06-18 17:49 UTCEPSS rescoreEPSS 17% · 96th percentile
  17. 2026-06-17 17:49 UTCEPSS rescoreEPSS 17% · 96th percentile
  18. 2026-06-16 17:49 UTCEPSS rescoreEPSS 17% · 96th percentile
  19. 2026-06-14 23:13 UTCEPSS rescoreEPSS 11% · 93rd percentile
  20. 2026-06-13 22:56 UTCEPSS rescoreEPSS 11% · 93rd percentile
  21. 2026-06-12 23:07 UTCEPSS rescoreEPSS 11% · 93rd percentile
  22. 2026-06-11 13:55 UTCEPSS rescoreEPSS 11% · 93rd percentile
  23. 2026-06-10 22:13 UTCEPSS rescoreEPSS 11% · 93rd percentile
  24. 2026-06-10 13:17 UTCEPSS rescoreEPSS 11% · 93rd percentile
  25. 2026-06-08 14:13 UTCEPSS rescoreEPSS 11% · 93rd percentile
  26. 2026-06-07 15:21 UTCEPSS rescoreEPSS 11% · 93rd percentile
  27. 2026-06-05 06:07 UTCEPSS rescoreEPSS 11% · 93rd percentile
  28. 2026-06-04 13:09 UTCEPSS rescoreEPSS 11% · 93rd percentile
  29. 2026-06-02 20:10 UTCEPSS rescoreEPSS 11% · 93rd percentile
  30. 2026-06-01 13:48 UTCEPSS rescoreEPSS 11% · 93rd percentile
  31. 2026-05-31 22:27 UTCEPSS rescoreEPSS 11% · 93rd percentile
  32. 2026-05-31 21:57 UTCEG score recompute
  33. 2026-05-31 21:57 UTCGHSA enrichmentGHSA-7g6p-865f-j3r5 · GitHub severity HIGH
  34. 2026-05-31 00:13 UTCEPSS rescoreEPSS 11% · 93rd percentile
  35. 2026-05-29 13:40 UTCEPSS rescoreEPSS 11% · 93rd percentile
  36. 2026-05-28 13:42 UTCEPSS rescoreEPSS 11% · 93rd percentile
  37. 2026-05-27 13:37 UTCEPSS rescoreEPSS 11% · 93rd percentile
  38. 2026-05-26 13:41 UTCEPSS rescoreEPSS 11% · 93rd percentile
  39. 2026-05-26 07:16 UTCEPSS rescoreEPSS 11% · 93rd percentile
  40. 2026-05-24 16:42 UTCEPSS rescoreEPSS 11% · 93rd percentile
  41. 2026-05-23 01:58 UTCOSV refresh
  42. 2026-05-22 21:15 UTCEPSS rescoreEPSS 11% · 93rd percentile
  43. 2026-05-21 22:38 UTCEPSS rescoreEPSS 11% · 93rd percentile
  44. 2026-05-20 22:36 UTCEPSS rescoreEPSS 11% · 93rd percentile
  45. 2026-05-20 11:20 UTCEPSS rescoreEPSS 11% · 93rd percentile
  46. 2026-05-18 21:29 UTCEPSS rescoreEPSS 11% · 93rd percentile

Publicly available exploits

(1 reference)

Public exploit code is referenced for this CVE (1 Exploit-DB entry). Defenders should treat patch urgency accordingly.

  • Exploit-DBEDB-19722✓ verified
    Published Jan 11, 2000

    RedHat 6.1 / IRIX 6.5.18 - 'lpd' Command Execution

    Open source ↗

Related CVEs(same product)

Frequently asked(4)

What is CVE-2000-1221?
CVE-2000-1221 is a high-severity vulnerability; its CVE record was published on January 8, 2000. The line printer daemon (lpd) in the lpr package in multiple Linux operating systems authenticates by comparing the reverse-resolved hostname of the local machine to the hostname of the print server as returned by gethostname, which allows remote attackers to bypass intended access controls by…
When was CVE-2000-1221 made public?
CVE-2000-1221 was made public on January 8, 2000: that is the date its CVE record's CNA, MITRE Corporation, gives for when the vulnerability was made public. The CVE record itself was published on January 8, 2000. EchelonGraph's copy of the record carries a last-modified date of June 16, 2026; the record at its source may have been updated since.
Is CVE-2000-1221 actively exploited?
CVE-2000-1221 is not currently on CISA's Known Exploited Vulnerabilities catalog. EchelonGraph's EG-KEV model places it in Tier 2 (Weaponized), which is not evidence of exploitation: Exploit-DB marks a public exploit for it as verified. EchelonGraph does not test whether exploit code works. FIRST EPSS estimates a 17% probability of exploitation in the next 30 days (96th percentile of EPSS-scored CVEs).
How do I remediate CVE-2000-1221?
A fix for CVE-2000-1221 is available: update to the fixed version the vendor names in its advisory.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2000-1221

Explore →

Is Your Infrastructure Affected by CVE-2000-1221?

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

Book a Demo →Browse All CVEs