BindApplication · Isc

CVE-2015-5722

HIGH · 7.8 CVSS v2.0 Published 2015-09-05

Fix available

A fix is available. Upgrade to after 9.10.2 or later.

See remediation →

87/100

Remediation priority · High

Remotely reachable No privileges Zero-click

Official description

NVD · unedited

buffer.c in named in ISC BIND 9.x before 9.9.7-P3 and 9.10.x before 9.10.2-P4 allows remote attackers to cause a denial of service (assertion failure and daemon exit) by creating a zone containing a malformed DNSSEC key and issuing a query for a name in that zone.

Technical summary

dbcve analysis · high confidence

buffer.c in ISC BIND 9.x before 9.9.7-P3 and 9.10.x before 9.10.2-P4 contains an assertion failure vulnerability that can be triggered by remote attackers creating a zone with a malformed DNSSEC key and issuing a query for a name in that zone, causing the daemon to exit.

MitigationUpgrade BIND 9 to version 9.9.7-P3, 9.10.2-P4, or later to patch the assertion failure in buffer.c; alternatively, disable DNSSEC validation if upgrading is not immediately feasible.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions

NVD · CPE data

BindApplication

Affected:<= 9.9.7<= 9.10.2

Mac Os X ServerOperating system

Affected:= 5.0.15

CVSS breakdown

From the vector

Attack vector: Network
Complexity: Low
Authentication: None
Confidentiality: None
Integrity: None
Availability: Complete

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

Am I affected?

dbcve checks

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

Identify installed BIND version

Run 'named -v' or 'named -V' to display the BIND version, or check the package manager output (e.g., 'rpm -q bind', 'dpkg -l bind9')

Affected if Version is 9.9.7 or lower, or 9.10.2 or lower (including all 9.9.x versions before 9.9.7-P3 and all 9.10.x versions before 9.10.2-P4)
Confirm DNSSEC validation is enabled

Inspect the BIND configuration file (named.conf) and look for the 'dnssec-enable' directive; if present, verify it is set to 'yes'

Affected if The directive 'dnssec-enable yes;' exists in the configuration, as DNSSEC must be enabled for the vulnerability to be triggered
Check for zones with DNSSEC keys configured

Review named.conf for 'dnssec-key' declarations or zone files that contain DNSSEC key material (KEY, DNSKEY, RRSIG records)

Affected if Any zone is configured with DNSSEC signing keys, as a malformed DNSSEC key in a zone can trigger the assertion failure when queried
Verify the server processes recursive or authoritative queries

Check named.conf for 'recursion yes;' or any 'zone' definitions indicating the server serves authoritative responses

Affected if The server is configured to answer queries (either recursive or authoritative for DNSSEC-signed zones), allowing remote attackers to trigger the flaw by querying a zone with a malformed key

You are affected if your BIND version is 9.9.7 or lower or 9.10.2 or lower, DNSSEC is enabled in the configuration, and the server can receive or serve queries for zones containing DNSSEC keys.

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

Remediation

From vendor data

Upgrade available Upgrade to a release after 9.10.2

Interim mitigation

Upgrade BIND 9 to version 9.9.7-P3, 9.10.2-P4, or later to patch the assertion failure in buffer.c; alternatively, disable DNSSEC validation if upgrading is not immediately feasible.

Fix this in Bind Scoped from the published advisory

Consultation3.0 h
Implementation4.0 h
Testing4.0 h
Review / QA2.0 h

13.0 hours of engineering $2,280

Get the upgrade done

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

Scan for this in your stack

Free · runs locally

dbcve dependency scanner

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

Primary sources

Practitioner notes

Contributed

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

Notes0 Guidelines

Know something about CVE-2015-5722?

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.

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

At a glance

A fix existsUpgrade to after 9.10.2 or later

Severity 7.8 High

Exploit likelihood EPSS, next 30 days 33.7%

Affects: Bind

Remediation

A high-priority fix

Fix this in Bind 13 hrs · Moderate

Typical engagement from $2,280

Get a fix See the full breakdown ↓

A high-priority vulnerability. Send your environment and a specialist will scope CVE-2015-5722 and return a fixed quote and timeline.

You’ll deal with our team directly and deploy the reviewed fix to staging first — never straight to production.

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.

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.

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.

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.

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.

Check your environment

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.

Scan for this in your stack

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

Practitioner notes

No notes yet

Official description

Technical summary

Affected products & versions

CVSS breakdown

Am I affected?

Remediation

References