CVE-2017-3139
HIGHCVSS 7.5/10EPSS 1.63%
Last modified
CVE-2017-3139 is a high-severity vulnerability rated 7.5/10 on the CVSS scale. A 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.. EPSS estimates a 1.63% chance of exploitation in the next 30 days.
Description
A 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.
Metrics
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
Weakness Enumeration
Affected Software
| Vendor | Product | Versions |
|---|---|---|
| Redhat | Enterprise Linux Server Aus | 6.2 |
| Redhat | Enterprise Linux Server Aus | 6.4 |
| Redhat | Enterprise Linux Server Aus | 6.5 |
| Redhat | Enterprise Linux Server Aus | 6.6 |
| Redhat | Enterprise Linux Server Eus | 6.7 |
| Redhat | Enterprise Linux Server Tus | 6.5 |
| Redhat | Enterprise Linux Server Tus | 6.6 |
References
- https://access.redhat.com/security/cve/cve-2017-3139Third Party Advisory
- https://bugzilla.redhat.com/show_bug.cgi?id=1447743Issue Tracking, Third Party Advisory
- https://access.redhat.com/security/cve/cve-2017-3139Third Party Advisory
- https://bugzilla.redhat.com/show_bug.cgi?id=1447743Issue Tracking, Third Party Advisory
Timeline
- Published
- Last Modified
- Status
- Modified
Frequently Asked Questions
What is CVE-2017-3139?
A 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.
How severe is CVE-2017-3139?
CVE-2017-3139 has a CVSS score of 7.5/10 (HIGH severity). The EPSS model estimates a 1.63% probability of exploitation in the next 30 days.
How do I fix CVE-2017-3139?
Check the vendor references and advisories linked above for patched versions and mitigation guidance. You can also run a Strix scan to test if your systems are affected.
How Strix Helps
- How Strix found a critical auth bypass in etcdStrix autonomously discovered a critical authentication bypass in etcd, later designated CVE-2026-33413.
- Autonomous PentestingAI agents that find and validate exploitable vulnerabilities like this one across your applications.
- PR ReviewsPentest every pull request so vulnerable code is caught before it ships to production.
- AI Penetration TestingHow AI-driven penetration testing continuously covers your attack surface.
Related CVEs from 2017
- CVE-2017-3133A Cross-Site Scripting vulnerability in Fortinet FortiOS ver…
- CVE-2017-3134An escalation of privilege vulnerability in Fortinet FortiWL…
- CVE-2017-3135Under some conditions when using both DNS64 and RPZ to rewri…7.5
- CVE-2017-3136A query with a specific set of characteristics could cause a…5.9
- CVE-2017-3137Mistaken assumptions about the ordering of records in the an…7.5
- CVE-2017-3138named contains a feature which allows operators to issue com…6.5
- CVE-2017-3140If named is configured to use Response Policy Zones (RPZ) an…3.7
- CVE-2017-3141The BIND installer on Windows uses an unquoted service path …7.2
- CVE-2017-3142An attacker who is able to send and receive messages to an a…5.3
- CVE-2017-3143An attacker who is able to send and receive messages to an a…7.5
- CVE-2017-3144A vulnerability stemming from failure to properly clean up c…7.5
- CVE-2017-3145BIND was improperly sequencing cleanup operations on upstrea…7.5
Are you affected by CVE-2017-3139?
Run a free Strix scan to check your systems for this vulnerability.
Scan your code nowSource: NVD / NIST