# CVE-2017-9217: Null dereference in n/a

> Remote attackers can crash the systemd-resolved daemon by sending a crafted DNS response with an empty question section.

- **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:** 24 May 2017
- **Updated:** 13 Dec 2024
- **Also known as:** DEBIAN-CVE-2017-9217, GHSA-pv82-vf69-rqqm, SUSE-SU-2017:1773-1, UBUNTU-CVE-2017-9217

## What is CVE-2017-9217?

CVE-2017-9217 is a high-severity vulnerability in Systemd Project Systemd, published on 24 May 2017. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

systemd-resolved through 233 allows remote attackers to cause a denial of service (daemon crash) via a crafted DNS response with an empty question section.

Weakness: CWE-476 (NULL Pointer Dereference)

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

It affects 1 product.


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

Products: Systemd Project Systemd.

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

Apply the vendor's patch.

## Is CVE-2017-9217 being exploited?

There is no known exploitation of CVE-2017-9217 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-9445](https://insights.sbomify.com/CVE-2017-9445/): Memory corruption 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-9217 and fix it if it is affected.

What it is: CVE-2017-9217 is a high-severity vulnerability in Systemd Project Systemd, published on 24 May 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-9217 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-9217/ (Markdown: https://insights.sbomify.com/CVE-2017-9217/index.md)
```

## Sources

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

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