dbcve.org
BindApplication · Isc

CVE-2007-2241

HIGH · 7.1 CVSS v2.0 Published 2007-05-02
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
80/100
Remediation priority · High
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 query.c in ISC BIND 9.4.0, and 9.5.0a1 through 9.5.0a3, when recursion is enabled, allows remote attackers to cause a denial of service (daemon exit) via a sequence of queries processed by the query_addsoa function.

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 · moderate confidence

Buffer handling flaw in the query_addsoa function within BIND 9's query.c allows remote attackers to trigger daemon exit via a specific sequence of DNS queries when recursion is enabled.

MitigationUpgrade to BIND 9.4.1, 9.5.0a4, or later versions; alternatively, disable recursion if not required for DNS services.

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.4.0= 9.5.0

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
M
Authentication
None
Confidentiality
None
Integrity
None
Availability
Complete

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

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. Check BIND version
    Run 'named -v' or 'named -V' to display the BIND version number
    Affected if The version shown is exactly 9.4.0 or 9.5.0
  2. Locate the named.conf file
    Common paths are /etc/named.conf, /etc/bind/named.conf, or /usr/local/etc/named.conf. Check your system's configuration file location.
    Affected if The configuration file exists and is accessible for inspection
  3. Verify recursion setting
    Search the named.conf for 'recursion yes;' or 'allow-recursion' directives. Use 'grep -i recursion /path/to/named.conf' to find the recursion configuration.
    Affected if Recursion is explicitly enabled ('recursion yes;') or no 'recursion no;' directive is present with no explicit restriction on recursion
  4. Confirm service is running
    Check if the named daemon is active using 'ps aux | grep named' or 'systemctl status named' depending on your system
    Affected if The BIND named service is running and accepting queries

You are affected only if BIND version is exactly 9.4.0 or 9.5.0 AND recursion is enabled, allowing the malformed query sequence to reach the vulnerable query_addsoa function.

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 to BIND 9.4.1, 9.5.0a4, or later versions; alternatively, disable recursion if not required for DNS services.

Fix this in Bind Scoped from the published advisory
  • Consultation1.0 h
  • Implementation2.0 h
  • Testing2.0 h
  • Review / QA1.0 h
6.0 hours of engineering $1,040
Get help mitigating

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 locally
dbcve dependency scanner

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