# CVE-2023-7008: Systemd-resolved: unsigned name response in signed zone is not refused when dnssec=yes

> Attackers can bypass DNSSEC validation to manipulate DNS records, affecting Linux systems using systemd-resolved with DNSSEC enabled.

- **Severity:** Medium 5.9 (`CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:H/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 23 Dec 2023
- **Updated:** 14 Oct 2026
- **Also known as:** ALSA-2024:2463, ALSA-2024:3203, AZL-32270, AZL-32271, AZL-35291, AZL-43171, CLSA-2024-1718895586, CLSA-2024-1718898538, CLSA-2024-1722535503, DEBIAN-CVE-2023-7008, GHSA-hwxf-wjq7-j3hm, OESA-2024-1020, OESA-2024-2262, RHSA-2024:2463, RHSA-2024:3203, RLSA-2024:2463, RLSA-2024:3203, SUSE-SU-2024:3149-1, UBUNTU-CVE-2023-7008, openSUSE-SU-2024:13665-1

## What is CVE-2023-7008?

CVE-2023-7008 is a medium-severity vulnerability in Systemd Project Systemd, published on 23 Dec 2023. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

A vulnerability was found in systemd-resolved. This issue may allow systemd-resolved to accept records of DNSSEC-signed domains even when they have no signature, allowing man-in-the-middles (or the upstream DNS resolver) to manipulate records.

Weakness: CWE-300 (Channel Accessible by Non-Endpoint)

## Which versions are affected by CVE-2023-7008?

It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `systemd` | AlmaLinux:8 | All versions | 239-82.el8 |
| `systemd-container` | AlmaLinux:8 | All versions | 239-82.el8 |
| `systemd-devel` | AlmaLinux:8 | All versions | 239-82.el8 |
| `systemd-journal-remote` | AlmaLinux:8 | All versions | 239-82.el8 |
| `systemd-libs` | AlmaLinux:8 | All versions | 239-82.el8 |
| `systemd-pam` | AlmaLinux:8 | All versions | 239-82.el8 |
| `systemd-tests` | AlmaLinux:8 | All versions | 239-82.el8 |
| `systemd-udev` | AlmaLinux:8 | All versions | 239-82.el8 |
| `rhel-net-naming-sysattrs` | AlmaLinux:9 | All versions | 252-32.el9_4.alma.1 |
| `systemd` | AlmaLinux:9 | All versions | 252-32.el9_4.alma.1 |
| `systemd-boot-unsigned` | AlmaLinux:9 | All versions | 252-32.el9_4.alma.1 |
| `systemd-container` | AlmaLinux:9 | All versions | 252-32.el9_4.alma.1 |
| `systemd-devel` | AlmaLinux:9 | All versions | 252-32.el9_4.alma.1 |
| `systemd-journal-remote` | AlmaLinux:9 | All versions | 252-32.el9_4.alma.1 |
| `systemd-libs` | AlmaLinux:9 | All versions | 252-32.el9_4.alma.1 |
| `systemd-oomd` | AlmaLinux:9 | All versions | 252-32.el9_4.alma.1 |
| `systemd-pam` | AlmaLinux:9 | All versions | 252-32.el9_4.alma.1 |
| `systemd-resolved` | AlmaLinux:9 | All versions | 252-32.el9_4.alma.1 |
| `systemd-rpm-macros` | AlmaLinux:9 | All versions | 252-32.el9_4.alma.1 |
| `systemd-udev` | AlmaLinux:9 | All versions | 252-32.el9_4.alma.1 |
| `systemd` | Red Hat:enterprise_linux:8::baseos | All versions | 0:239-82.el8 |
| `systemd-container` | Red Hat:enterprise_linux:8::baseos | All versions | 0:239-82.el8 |
| `systemd-container-debuginfo` | Red Hat:enterprise_linux:8::baseos | All versions | 0:239-82.el8 |
| `systemd-debuginfo` | Red Hat:enterprise_linux:8::baseos | All versions | 0:239-82.el8 |
| `systemd-debugsource` | Red Hat:enterprise_linux:8::baseos | All versions | 0:239-82.el8 |
| `systemd-devel` | Red Hat:enterprise_linux:8::baseos | All versions | 0:239-82.el8 |
| `systemd-journal-remote` | Red Hat:enterprise_linux:8::baseos | All versions | 0:239-82.el8 |
| `systemd-journal-remote-debuginfo` | Red Hat:enterprise_linux:8::baseos | All versions | 0:239-82.el8 |
| `systemd-libs` | Red Hat:enterprise_linux:8::baseos | All versions | 0:239-82.el8 |
| `systemd-libs-debuginfo` | Red Hat:enterprise_linux:8::baseos | All versions | 0:239-82.el8 |
| `systemd-pam` | Red Hat:enterprise_linux:8::baseos | All versions | 0:239-82.el8 |
| `systemd-pam-debuginfo` | Red Hat:enterprise_linux:8::baseos | All versions | 0:239-82.el8 |
| `systemd-tests` | Red Hat:enterprise_linux:8::baseos | All versions | 0:239-82.el8 |
| `systemd-tests-debuginfo` | Red Hat:enterprise_linux:8::baseos | All versions | 0:239-82.el8 |
| `systemd-udev` | Red Hat:enterprise_linux:8::baseos | All versions | 0:239-82.el8 |
| `systemd-udev-debuginfo` | Red Hat:enterprise_linux:8::baseos | All versions | 0:239-82.el8 |
| `systemd-boot-unsigned-debuginfo` | Red Hat:enterprise_linux:9::appstream | All versions | 0:252-32.el9_4 |
| `systemd-container-debuginfo` | Red Hat:enterprise_linux:9::appstream | All versions | 0:252-32.el9_4 |
| `systemd-debuginfo` | Red Hat:enterprise_linux:9::appstream | All versions | 0:252-32.el9_4 |
| `systemd-debugsource` | Red Hat:enterprise_linux:9::appstream | All versions | 0:252-32.el9_4 |

Products: Systemd Project Systemd.

## How do I fix CVE-2023-7008?

Apply the vendor's patch.

## Is CVE-2023-7008 being exploited?

There is no known exploitation of CVE-2023-7008 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-2017-9217](https://insights.sbomify.com/CVE-2017-9217/): Null dereference in n/a (high 7.5)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2023-7008 and fix it if it is affected.

What it is: CVE-2023-7008 is a medium-severity vulnerability in Systemd Project Systemd, published on 23 Dec 2023. 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-2023-7008 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-2023-7008/ (Markdown: https://insights.sbomify.com/CVE-2023-7008/index.md)
```

## Sources

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

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