CVE-2014-8680
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 GeoIP functionality in ISC BIND 9.10.0 through 9.10.1 allows remote attackers to cause a denial of service (assertion failure and named exit) via vectors related to (1) the lack of GeoIP databases for both IPv4 and IPv6, or (2) IPv6 support with certain options.
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 confidenceThe GeoIP functionality in ISC BIND versions 9.10.0 through 9.10.1 contains assertion failures that cause denial of service. The vulnerability triggers when GeoIP databases are missing for both IPv4 and IPv6, or when IPv6 is used with certain GeoIP options, leading to named process exit.
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.10.0= 9.10.1CVSS 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
- High
- Authentication
- None
- Confidentiality
- None
- Integrity
- None
- Availability
- Complete
AV:N/AC:H/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 checksWork through these to decide whether this CVE applies to you.
-
Verify BIND versionRun 'named -v' or 'named -V' to check the installed BIND versionAffected if Version is 9.10.0 or 9.10.1
-
Check if GeoIP is configured in named.confSearch for 'geoip' directives in named.conf using 'grep -i geoip /etc/named.conf' or similar path to your configuration fileAffected if GeoIP directives are present and BIND version is 9.10.0-9.10.1
-
Verify GeoIP database files existCheck for the presence of GeoIP database files (typically under /usr/share/GeoIP/ or similar location) using 'ls -la /usr/share/GeoIP/'Affected if GeoIP databases are missing or incomplete, and GeoIP is enabled in configuration
-
Check for IPv6 usage with GeoIPReview named.conf for any 'geoip' directives that reference IPv6 addresses or listen-on-v6 options combined with geoip blocksAffected if IPv6 is enabled alongside GeoIP configuration in affected BIND versions
A system is affected if running BIND 9.10.0 or 9.10.1 with GeoIP functionality enabled and either missing GeoIP databases or using IPv6 with GeoIP options
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 BIND to version 9.10.2 or later where the vulnerability is fixed. If upgrade is not immediately possible, disable GeoIP functionality in named.conf if not required, or ensure GeoIP databases are properly installed and configured when using GeoIP features.
- Consultation2.0 h
- Implementation2.0 h
- Testing3.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,224.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2014-8680 — 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-2014-8680 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