CVE-2019-6467
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 · uneditedA programming error in the nxdomain-redirect feature can cause an assertion failure in query.c if the alternate namespace used by nxdomain-redirect is a descendant of a zone that is served locally. The most likely scenario where this might occur is if the server, in addition to performing NXDOMAIN redirection for recursive clients, is also serving a local copy of the root zone or using mirroring to provide the root zone, although other configurations are also possible. Versions affected: BIND 9.12.0-> 9.12.4, 9.14.0. Also affects all releases in the 9.13 development branch.
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 confidenceA programming error in BIND's nxdomain-redirect feature can cause an assertion failure in query.c, leading to a denial of service. The vulnerability triggers when the alternate namespace used for NXDOMAIN redirection is a descendant of a zone served locally, most commonly when the server serves a local copy or mirrored version of the root zone in addition to performing NXDOMAIN redirection for recursive clients.
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.12.0, <= 9.12.4>= 9.13.0, <= 9.13.7= 9.14.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
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- None
- Integrity
- None
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
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.
-
Check BIND versionRun 'named -v' or 'named -V' to retrieve the installed BIND version numberAffected if Version is 9.12.0 through 9.12.4, 9.13.0 through 9.13.7, or exactly 9.14.0
-
Verify nxdomain-redirect is enabledSearch the named.conf configuration file (including included files) for the directive 'nxdomain-redirect yes;' or check for 'nxdomain-redirect' set to trueAffected if The nxdomain-redirect option is enabled in the configuration
-
Check for local zone definitionsSearch named.conf for 'zone' blocks, particularly looking for a zone named '.' (dot/root) defined with type 'mirror' or 'master'Affected if A local zone definition exists, especially for the root zone (zone '.'), as this creates the condition where the redirect namespace is a descendant of a locally served zone
-
Confirm combined vulnerable configurationReview both the nxdomain-redirect setting and local zone configuration together to determine if both conditions exist simultaneouslyAffected if Both nxdomain-redirect is enabled AND a local copy of the root zone (or other zone that becomes the redirect target's parent) is being served
A user is affected if running a vulnerable BIND version (9.12.0-9.12.4, 9.13.0-9.13.7, or 9.14.0) with nxdomain-redirect enabled alongside a locally served root zone or similar local zone configuration.
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 to BIND 9.12.5 or later, or 9.14.1 or later. Alternatively, disable nxdomain-redirect or avoid serving local copies of the root zone when nxdomain-redirect is enabled.
- Consultation3.0 h
- Implementation4.0 h
- Testing4.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,648.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2019-6467 — 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-2019-6467 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