dbcve.org
Debian LinuxOperating system · Debian

CVE-2000-1221

HIGH · 10.0 CVSS v2.0 Published 2000-01-08
Patch available
A vendor patch is available. No clean upgrade release — apply the published patch.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click Patch available

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis

A detailed technical summary for this CVE is being prepared.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Debian LinuxOperating system
Affected:= 2.1
LinuxOperating system
Affected:= 4.1= 4.2= 5.0= 5.2= 6.0= 6.1
IrixOperating system
Affected:= 6.5= 6.5.1= 6.5.2= 6.5.3= 6.5.4= 6.5.5= 6.5.6= 6.5.7= 6.5.8= 6.5.9= 6.5.10= 6.5.11

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Authentication
None
Confidentiality
Complete
Integrity
Complete
Availability
Complete

AV:N/AC:L/Au:N/C:C/I:C/A:C

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Patch available Apply the vendor patch
Vendor patch patches.sgi.com →
Recommended fix Moderate confidence

For legacy systems, upgrade to a modern Linux distribution that has discontinued use of the vulnerable lprng/lpr package in favor of CUPS (Common Unix Printing System)

  1. 1. Obtain the vendor-specific patch from the SGI advisory at ftp://patches.sgi.com/support/free/security/advisories/20021104-01-P for IRIX systems
  2. 2. For Red Hat Linux systems, check rhn.redhat.com for errata related to the lpr/lpd package
  3. 3. For Debian systems, check www.debian.org security advisories for the lpr package update for Debian 2.1
  4. 4. Apply the appropriate vendor patch to the lpr package, ensuring the patch addresses the reverse DNS hostname comparison vulnerability
  5. 5. Restart the lpd daemon after applying the patch to ensure the fix takes effect
  6. 6. Verify that lpd now properly validates both forward and reverse DNS lookups before granting print server access
Caveat Upgrading to modern CUPS may require reconfiguration of print queues and updating print client configurations; some legacy print workflows may need adjustment

Generated from the published advisory — verify against the referenced sources before acting.

We can apply and verify the patch for your build — typical engagement from $1,950. Get the patch applied

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2000-1221 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2000-1221 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data