# CVE-2017-3137: A response packet can cause a resolver to terminate when processing an answer containing a CNAME or DNAME

> A remote attacker can cause the BIND DNS resolver to crash by sending a response with CNAME or DNAME records in an unusual order.

- **Severity:** High 7.5 (`CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 16 Jan 2019
- **Updated:** 17 Sep 2024
- **Also known as:** ALPINE-CVE-2017-3137, DEBIAN-CVE-2017-3137, GHSA-wmp5-3j44-5x2x, SUSE-SU-2017:1027-1, UBUNTU-CVE-2017-3137

## What is CVE-2017-3137?

CVE-2017-3137 is a high-severity denial of service vulnerability in Debian Debian Linux, published on 16 Jan 2019. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Mistaken assumptions about the ordering of records in the answer section of a response containing CNAME or DNAME resource records could lead to a situation in which named would exit with an assertion failure when processing a response in which records occurred in an unusual order. Affects BIND 9.9.9-P6, 9.9.10b1->9.9.10rc1, 9.10.4-P6, 9.10.5b1->9.10.5rc1, 9.11.0-P3, 9.11.1b1->9.11.1rc1, and 9.9.9-S8.

Weakness: CWE-617 (Reachable Assertion)

## Which versions are affected by CVE-2017-3137?

It affects 11 products.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `bind` | SUSE:Linux Enterprise Point of Sale 11 SP3 | All versions | 9.9.6P1-0.47.1 |
| `bind` | SUSE:Linux Enterprise Server 11 SP3-LTSS | All versions | 9.9.6P1-0.47.1 |
| `bind` | SUSE:Linux Enterprise Server 11 SP3-TERADATA | All versions | 9.9.6P1-0.47.1 |
| `bind` | SUSE:Linux Enterprise Server 11 SP4 | All versions | 9.9.6P1-0.47.1 |
| `bind` | SUSE:Linux Enterprise Server for SAP Applications 11 SP4 | All versions | 9.9.6P1-0.47.1 |
| `bind` | SUSE:Linux Enterprise Software Development Kit 11 SP4 | All versions | 9.9.6P1-0.47.1 |
| `bind` | SUSE:Manager 2.1 | All versions | 9.9.6P1-0.47.1 |
| `bind` | SUSE:Manager Proxy 2.1 | All versions | 9.9.6P1-0.47.1 |
| `bind` | SUSE:OpenStack Cloud 5 | All versions | 9.9.6P1-0.47.1 |

Products: Debian Debian Linux, Isc Bind, Netapp Data Ontap Edge, Netapp Element Software, Netapp Oncommand Balance, Redhat Enterprise Linux Desktop, Redhat Enterprise Linux Server, Redhat Enterprise Linux Server Aus, Redhat Enterprise Linux Server Eus, Redhat Enterprise Linux Server Tus, Redhat Enterprise Linux Workstation.

## How do I fix CVE-2017-3137?

Apply the vendor's patch.

## Is CVE-2017-3137 being exploited?

There is no known exploitation of CVE-2017-3137 in the wild and no public exploit code.

## Other vulnerabilities in Debian Debian Linux

- [CVE-2015-3306](https://insights.sbomify.com/CVE-2015-3306/): ProFTPD Improper Access Control (critical 10.0, exploited in the wild)
- [CVE-2025-49113](https://insights.sbomify.com/CVE-2025-49113/): RoundCube Webmail Deserialization of Untrusted Data (critical 9.9, exploited in the wild)
- [CVE-2026-24061](https://insights.sbomify.com/CVE-2026-24061/): GNU InetUtils Argument Injection (critical 9.8, exploited in the wild)
- [CVE-2025-39682](https://insights.sbomify.com/CVE-2025-39682/): Linux Kernel Improper Check for Unusual or Exceptional Conditions (critical 9.8, exploited in the wild)
- [CVE-2024-9680](https://insights.sbomify.com/CVE-2024-9680/): Mozilla Firefox Use-After-Free (critical 9.8, exploited in the wild)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2017-3137 and fix it if it is affected.

What it is: CVE-2017-3137 is a high-severity denial of service vulnerability in Debian Debian Linux, published on 16 Jan 2019. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2017-3137 in the wild and no public exploit code.

Affected product: Debian Debian Linux. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2017-3137/ (Markdown: https://insights.sbomify.com/CVE-2017-3137/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2017-3137
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2017-3137
- OSV: https://osv.dev/vulnerability/CVE-2017-3137

---
From sbomify Insights: https://insights.sbomify.com/CVE-2017-3137/
Summaries are generated and may contain mistakes; the official description above is the record.