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

> A malicious DNS server can trigger a buffer overflow in systemd-resolved via crafted TCP responses, potentially allowing arbitrary code execution.

- **Severity:** High 7.5 (`CVSS:3.1/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:** 28 Jun 2017
- **Updated:** 5 Aug 2024
- **Also known as:** DEBIAN-CVE-2017-9445, GHSA-42xm-66qf-5jj8, SUSE-SU-2017:1898-1, UBUNTU-CVE-2017-9445

## What is CVE-2017-9445?

CVE-2017-9445 is a high-severity memory corruption vulnerability in Systemd Project Systemd, published on 28 Jun 2017. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

In systemd through 233, certain sizes passed to dns_packet_new in systemd-resolved can cause it to allocate a buffer that's too small. A malicious DNS server can exploit this via a response with a specially crafted TCP payload to trick systemd-resolved into allocating a buffer that's too small, and subsequently write arbitrary data beyond the end of it.

Weakness: CWE-787 (Out-of-bounds Write)

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

It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `dracut` | SUSE:Linux Enterprise Desktop 12 SP2 | All versions | 044.1-109.8.3 |
| `systemd` | SUSE:Linux Enterprise Desktop 12 SP2 | All versions | 228-150.7.1 |
| `dracut` | SUSE:Linux Enterprise Server 12 SP2 | All versions | 044.1-109.8.3 |
| `systemd` | SUSE:Linux Enterprise Server 12 SP2 | All versions | 228-150.7.1 |
| `dracut` | SUSE:Linux Enterprise Server for Raspberry Pi 12 SP2 | All versions | 044.1-109.8.3 |
| `systemd` | SUSE:Linux Enterprise Server for Raspberry Pi 12 SP2 | All versions | 228-150.7.1 |
| `dracut` | SUSE:Linux Enterprise Server for SAP Applications 12 SP2 | All versions | 044.1-109.8.3 |
| `systemd` | SUSE:Linux Enterprise Server for SAP Applications 12 SP2 | All versions | 228-150.7.1 |
| `systemd` | SUSE:Linux Enterprise Software Development Kit 12 SP2 | All versions | 228-150.7.1 |

Products: Systemd Project Systemd.

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

Apply the vendor's patch.

## Is CVE-2017-9445 being exploited?

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

## Other vulnerabilities in Systemd Project Systemd

- [CVE-2015-7510](https://insights.sbomify.com/CVE-2015-7510/): Memory corruption in n/a (critical 9.8)
- [CVE-2017-1000082](https://insights.sbomify.com/CVE-2017-1000082/): Privilege escalation in n/a (critical 9.8)
- [CVE-2016-10156](https://insights.sbomify.com/CVE-2016-10156/): Privilege escalation in n/a (high 7.8)
- [CVE-2017-9217](https://insights.sbomify.com/CVE-2017-9217/): Null dereference in n/a (high 7.5)
- [CVE-2026-40224](https://insights.sbomify.com/CVE-2026-40224/): Privilege escalation in systemd (medium 6.7)

## Fix prompt for AI coding agents

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

What it is: CVE-2017-9445 is a high-severity memory corruption vulnerability in Systemd Project Systemd, published on 28 Jun 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-9445 in the wild and no public exploit code.

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

## Sources

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

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