LinuxOperating system · Redhat
CVE-1999-0010
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 · uneditedDenial of Service vulnerability in BIND 8 Releases via maliciously formatted DNS messages.
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 confidenceDenial of Service vulnerability in BIND 8 where maliciously formatted DNS messages can crash the DNS server by exploiting improper parsing/handling of specially crafted DNS packets.
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
LinuxOperating system
= 4.2= 5.0= y2k_patchr4.11mu05= y2k_patchr4.12mu03= y2k_patchr4.20mu01= y2k_patchr4.20mu02= y2k_patchr4.20mu03= 4.9= 8= 4.1= 4.2= 4.3= 11= 13= 1.3= 1.3.1= 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
- 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 on the systemRun 'ps -ef | grep named' or 'ps -aux | grep named' to check if the BIND/named DNS server process is currently running. On Windows systems, check Services for 'DNS Server'.Affected if The named/BIND process is running and its version is 4.9 or 8.x (any 8.x release).
-
Determine the installed BIND versionRun 'named -v' or 'named -V' to display the BIND version. Alternatively, check the package manager: 'rpm -q bind' (Red Hat), 'dpkg -l bind' (Debian), or check the BIND binary directly with 'strings /usr/sbin/named | grep -i version'.Affected if The installed BIND version is 4.9.x or 8.x (any 8.x release).
-
Check the operating system version if using bundled BINDRun 'uname -a' or 'cat /etc/redhat-release' (Red Hat), 'oslevel' (AIX), or 'uname -srv' (NetBSD) to identify the OS version.Affected if The system runs Red Hat Linux 4.2 or 5.0, IBM AIX 4.1/4.2/4.3, NetBSD 1.3/1.3.1, or other affected OS variants listed in the CVE with BIND 4.9 or 8 bundled.
-
Verify DNS service network exposureCheck if port 53 is listening on external interfaces using 'netstat -tulpn | grep :53' or 'ss -tulpn | grep :53'. Review the 'listen-on' directive in /etc/named.conf (or /etc/named/named.conf).Affected if The DNS service is bound to external network interfaces (0.0.0.0 or non-loopback IP) and the vulnerable BIND version is running.
A system is affected if it runs BIND version 4.9 or 8 (or shipped with these versions) and has the DNS service exposed to the network.
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 from BIND 8 to a supported, current version of BIND (9.x or later) or migrate to an alternative DNS server software; for legacy systems that cannot upgrade, implement network-level filtering of malformed DNS packets at the perimeter.
Fix this in Linux
Scoped from the published advisory
- Consultation2.0 h
- Implementation4.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 $2,560.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-1999-0010 — 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-0010 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