CVE-2007-2925
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 · uneditedThe default access control lists (ACL) in ISC BIND 9.4.0, 9.4.1, and 9.5.0a1 through 9.5.0a5 do not set the allow-recursion and allow-query-cache ACLs, which allows remote attackers to make recursive queries and query the cache.
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 confidenceISC BIND 9.4.0 through 9.5.0a5 ships with default ACLs that do not explicitly set allow-recursion and allow-query-cache directives, causing the server to accept recursive queries and cache queries from any remote attacker, potentially enabling DNS amplification attacks and cache poisoning.
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= 9.4.0= 9.4.1= 9.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
- M
- Authentication
- None
- Confidentiality
- Partial
- Integrity
- Partial
- Availability
- None
AV:N/AC:M/Au:N/C:P/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 BIND versionRun 'named -v' or 'named -V' to get the installed BIND version, or check the package manager output (e.g., 'rpm -q bind', 'dpkg -l bind')Affected if The version is 9.4.0, 9.4.1, or 9.5.0
-
Locate named.confFind the BIND configuration file, typically at /etc/named.conf, /etc/bind/named.conf, or as specified in 'named -v' outputAffected if The file exists and is readable
-
Inspect allow-recursion settingSearch the named.conf file for 'allow-recursion' directive using grep or manual inspection of the options or view blocksAffected if The directive is absent or not explicitly set for any view/options block (meaning the default of 'localhost' and 'localnets' may apply, but the vulnerability is about not having explicit restrictions) - check if the line containing 'allow-recursion' is missing entirely in the configuration
-
Inspect allow-query-cache settingSearch the named.conf file for 'allow-query-cache' directive using grep or manual inspectionAffected if The directive is absent or not explicitly set (the vulnerability exists when this is not configured)
You are affected if you are running BIND version 9.4.0, 9.4.1, or 9.5.0 AND your named.conf lacks explicit allow-recursion and allow-query-cache directives, meaning the server accepts recursive queries from unauthorized sources by default.
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 dataConfigure explicit allow-recursion and allow-query-cache ACLs in named.conf to restrict recursive and cache queries to trusted internal networks or specific IP ranges.
- Consultation4.0 h
- Implementation2.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,152.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2007-2925 — 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-2007-2925 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