# CVE-2017-15650: Memory corruption in n/a

> A buffer overflow in musl libc allows attackers to execute arbitrary code or cause denial of service via crafted DNS replies.

- **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:** 19 Oct 2017
- **Updated:** 5 Aug 2024
- **Also known as:** ALPINE-CVE-2017-15650, DEBIAN-CVE-2017-15650, GHSA-p2mj-x9rf-q85j, UBUNTU-CVE-2017-15650

## What is CVE-2017-15650?

CVE-2017-15650 is a high-severity memory corruption vulnerability in n/a, published on 19 Oct 2017. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

musl libc before 1.1.17 has a buffer overflow via crafted DNS replies because dns_parse_callback in network/lookup_name.c does not restrict the number of addresses, and thus an attacker can provide an unexpected number by sending A records in a reply to an AAAA query.

Weakness: CWE-119 (Improper Restriction of Operations within the Bounds of a Memory Buffer)

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

It affects 1 product.


Products: Musl-Libc Musl.

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

Upgrade to a fixed version.

## Is CVE-2017-15650 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2014-3484](https://insights.sbomify.com/CVE-2014-3484/): Memory corruption in musl libc (critical 9.8)
- [CVE-2019-14697](https://insights.sbomify.com/CVE-2019-14697/): Memory corruption in n/a (critical 9.8)
- [CVE-2015-1817](https://insights.sbomify.com/CVE-2015-1817/): Memory corruption in n/a (critical 9.8)
- [CVE-2025-26519](https://insights.sbomify.com/CVE-2025-26519/): Memory corruption in musl (high 8.1)

## Fix prompt for AI coding agents

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

What it is: CVE-2017-15650 is a high-severity memory corruption vulnerability in n/a, published on 19 Oct 2017. 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-15650 in the wild and no public exploit code.

Affected product: n/a. 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-15650/ (Markdown: https://insights.sbomify.com/CVE-2017-15650/index.md)
```

## Sources

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

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