Debian LinuxOperating system · Debian
CVE-2000-0888
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 · uneditednamed in BIND 8.2 through 8.2.2-P6 allows remote attackers to cause a denial of service by sending an SRV record to the server, aka the "srv bug."
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 · high confidenceThe named DNS server in BIND 8.2 through 8.2.2-P6 contains a vulnerability in its SRV record handling that allows remote attackers to cause a denial of service. Sending a specially crafted SRV record to the DNS server triggers the issue, causing the server to crash or become unresponsive.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
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
= 2.2= 8.2= 8.2.1= 8.2.2CVSS 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
- None
- Integrity
- None
- Availability
- Partial
AV:N/AC:L/Au:N/C:N/I:N/A:P
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Verify BIND is running as the DNS serverCheck running processes for the 'named' daemon or review DNS service status using system service management toolsAffected if BIND named process is active and handling DNS queries
-
Identify the installed BIND versionRun 'named -v' or 'named -V' to display the BIND version, or check the package manager output for the installed bind package versionAffected if The version reported is 8.2, 8.2.1, or 8.2.2 (including any P6 patch level)
-
Confirm the operating system matches affected platformsCheck the OS version; this vulnerability affects Debian Linux 2.2 and ISC BIND versions 8.2-8.2.2Affected if Running Debian 2.2 with BIND from that era, or any BIND 8.2.x installation in the affected range
-
Determine if the DNS server accepts external queriesReview the named.conf configuration file for 'allow-query' or 'allow-recursion' directives to see if the server accepts queries from external network rangesAffected if The server is configured to accept DNS queries from untrusted or external network sources
A system is affected if it runs BIND version 8.2, 8.2.1, or 8.2.2 (including P6) and the DNS service is exposed to network traffic, allowing malicious SRV record queries to reach the server.
Generated from the published advisory. Verify against your own configuration.
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.
From vendor dataUpgrade to BIND version 8.2.3 or later, which contains the fix for the SRV record processing vulnerability. Alternatively, restrict unauthorized external DNS queries at the network perimeter to limit attack surface.
Fix this in Debian Linux
Scoped from the published advisory
- Consultation4.0 h
- Implementation2.0 h
- Testing3.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,864.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2000-0888 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2000-0888 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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