dbcve.org
BindApplication · Isc

CVE-2011-2464

MEDIUM · 5.0 CVSS v2.0 Published 2011-07-08
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
59/100
Remediation priority · Elevated
Remotely reachable No privileges Zero-click

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
Unspecified vulnerability in ISC BIND 9 9.6.x before 9.6-ESV-R4-P3, 9.7.x before 9.7.3-P3, and 9.8.x before 9.8.0-P4 allows remote attackers to cause a denial of service (named daemon crash) via a crafted UPDATE request.

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 confidence

ISC BIND 9 versions 9.6.x before 9.6-ESV-R4-P3, 9.7.x before 9.7.3-P3, and 9.8.x before 9.8.0-P4 contain an unspecified vulnerability that allows remote attackers to crash the named daemon via a crafted DNS UPDATE request, causing denial of service.

MitigationUpgrade BIND 9 to version 9.6-ESV-R4-P3 or later for the 9.6-ESV branch, 9.7.3-P3 or later for 9.7.x, or 9.8.0-P4 or later for 9.8.x. If immediate patching is not possible, consider restricting UPDATE access via ACLs or disabling dynamic updates from untrusted sources.

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
BindApplication
Affected:= 9.6= 9.6.0= 9.6.1= 9.6.2= 9.6.3= 9.7.0= 9.7.1= 9.7.2= 9.7.2b1= 9.7.3= 9.8.0= 9.8.1

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
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 checks

Work through these to decide whether this CVE applies to you.

  1. Determine installed BIND version
    Run `named -v` or `named -V` to display the BIND version. Alternatively, check your system's package manager (e.g., `rpm -q bind`, `dpkg -l bind9`, or `yum list installed bind`).
    Affected if The version is 9.6.x before 9.6-ESV-R4-P3, 9.7.x before 9.7.3-P3, or 9.8.x before 9.8.0-P4.
  2. Verify named daemon is running
    Check if the named process is active using `ps aux | grep named` or `service named status` (or `systemctl status named` on systemd systems).
    Affected if The named process is running on a vulnerable version.
  3. Check if dynamic updates are permitted
    Examine the BIND configuration file (commonly /etc/named.conf or /etc/bind/named.conf) for `allow-update` or `update-policy` directives within zone definitions or global options.
    Affected if Dynamic updates are allowed from untrusted or any source (e.g., `allow-update { any; }` or missing restriction), making the vulnerability exploitable over the network.
  4. Identify listening DNS ports
    Run `netstat -tulpn | grep :53` or `ss -tulpn | grep :53` to confirm named is listening on UDP/TCP port 53.
    Affected if The service is exposed to network traffic on port 53.

You are affected if BIND 9 is running a vulnerable version (9.6.x before 9.6-ESV-R4-P3, 9.7.x before 9.7.3-P3, or 9.8.x before 9.8.0-P4) and accepts DNS UPDATE requests from the network.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Upgrade BIND 9 to version 9.6-ESV-R4-P3 or later for the 9.6-ESV branch, 9.7.3-P3 or later for 9.7.x, or 9.8.0-P4 or later for 9.8.x. If immediate patching is not possible, consider restricting UPDATE access via ACLs or disabling dynamic updates from untrusted sources.

Fix this in Bind Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing6.0 h
  • Review / QA3.0 h
15.0 hours of engineering $2,560
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,096.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2011-2464 — 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-2011-2464 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