Enterprise Linux Server AusOperating system · Redhat
CVE-2017-3139
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 denial of service flaw was found in the way BIND handled DNSSEC validation. A remote attacker could use this flaw to make named exit unexpectedly with an assertion failure via a specially crafted DNS response.
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 denial of service vulnerability in BIND's DNSSEC validation allows remote attackers to crash the named process by sending specially crafted DNS responses that trigger an assertion failure, causing the DNS server to exit unexpectedly.
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
Enterprise Linux Server AusOperating system
= 6.2= 6.4= 6.5= 6.6
Enterprise Linux Server EusOperating system
= 6.7
Enterprise Linux Server TusOperating system
= 6.5= 6.6CVSS 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.
-
Identify BIND versionRun 'named -v' or 'rpm -q bind' to determine the installed BIND versionAffected if Installed BIND version matches the vulnerable version range for your RHEL version (compare against the affected RHEL versions listed)
-
Confirm named service is runningRun 'systemctl status named' or 'service named status' to verify the DNS server is activeAffected if The named process is running - the vulnerability only affects active BIND instances
-
Verify DNSSEC validation is enabledInspect the named.conf file (typically in /etc/named.conf) and look for 'dnssec-enable yes;' or 'dnssec-validation yes;' directives in the options blockAffected if DNSSEC validation is explicitly enabled (dnssec-validation set to 'yes' or 'auto') - the flaw only triggers when DNSSEC validation is active
-
Check RHEL versionRun 'cat /etc/redhat-release' to identify the exact RHEL versionAffected if The system runs RHEL 6.2, 6.4, 6.5, 6.6, or 6.7 and meets the affected variant criteria (Aus, Eus, or Tus)
-
Review DNS query logs for crashesCheck system logs (/var/log/messages or journalctl -u named) for recent 'assertion failure' or 'exiting' events related to namedAffected if Recent crashes or unexpected exits of the named process have occurred, particularly after processing DNSSEC-related responses
You are affected if you run a vulnerable BIND version on RHEL 6.2-6.7 (Aus/Eus/Tus variants) with DNSSEC validation enabled, and the named process has crashed or is vulnerable to crafted DNS responses.
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 a patched version. As a workaround, consider disabling DNSSEC validation if not required, or implement network-level filtering of suspicious DNS responses.
Fix this in Enterprise Linux Server Aus
Scoped from the published advisory
- Consultation2.0 h
- Implementation3.0 h
- Testing2.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,272.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2017-3139 — 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-2017-3139 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