CVE-1999-0024
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 · uneditedDNS cache poisoning via BIND, by predictable query IDs.
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 confidenceDNS cache poisoning vulnerability in BIND where the transaction ID (query ID) in DNS requests was predictable, allowing remote attackers to inject malicious DNS records into a caching resolver's cache and redirect traffic to attacker-controlled servers.
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= 4.9.5= 8.1= 2.1= 3.0= 4.1= 4.2= 64= 4.2= 4.2mp= 4.2mp= 3.0= 5.0CVSS 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
- Partial
- Availability
- None
AV:N/AC:L/Au:N/C:N/I:P/A:N
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.
-
Identify if BIND is installedRun 'named -v' or 'named -V' to check the BIND version, or check for the named process with 'ps aux | grep named'Affected if BIND version matches 4.9.5 or 8.1 from the affected list, or the specific versions listed for other affected products
-
Determine the BIND package versionUse system package managers: rpm -q bind, dpkg -l bind, or check /usr/sbin/named binary directly with 'named -v'Affected if Installed version equals 4.9.5 or 8.1 for ISC BIND, or any of the specific versions listed for BSDi, IBM AIX, NEC, or SCO systems
-
Check if recursion is enabledInspect the BIND configuration file (named.conf) for 'recursion yes;' or 'allow-recursion' directives, or query the server with 'dig +short @server localhost' to test recursive capabilityAffected if The server is configured as a caching resolver with recursion enabled - this is required for the cache poisoning attack to be exploitable
-
Verify query ID randomnessCapture DNS queries with tcpdump or wireshark and observe the Transaction ID (ID) field in DNS packets - check if IDs follow a predictable pattern or increment sequentiallyAffected if Query IDs are sequential, zero, or otherwise predictable rather than randomized - the core vulnerability of CVE-1999-0024
The system is affected if it runs BIND version 4.9.5 or 8.1 (or any affected product/version listed) with recursion enabled, and DNS query IDs can be predicted rather than randomly generated.
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 BIND to a version that implements cryptographically random transaction IDs, or configure the resolver to use source port randomization and modern BIND versions with improved query ID generation.
- Consultation1.0 h
- Implementation2.0 h
- Testing2.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 $1,664.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-1999-0024 — 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-1999-0024 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