# CVE-2022-4415: Information disclosure in systemd

> Local attackers can leak sensitive information because systemd-coredump ignores the fs.suid_dumpable kernel setting.

- **Severity:** Medium 5.5 (`CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 11 Jan 2023
- **Updated:** 3 Nov 2025
- **Also known as:** ALSA-2023:0837, AZL-12970, AZL-12971, AZL-35293, CLSA-2023-1678395968, CLSA-2023-1678396066, DEBIAN-CVE-2022-4415, GHSA-x49m-v7mv-3wvx, MGASA-2023-0217, OESA-2023-1027, OESA-2023-1028, RHSA-2023:0837, RLSA-2023:0837, SUSE-SU-2022:4627-1, SUSE-SU-2022:4629-1, SUSE-SU-2022:4630-1, SUSE-SU-2023:0058-1, SUSE-SU-2023:0201-1, UBUNTU-CVE-2022-4415, openSUSE-SU-2024:12576-1

## What is CVE-2022-4415?

CVE-2022-4415 is a medium-severity vulnerability in Systemd Project Systemd, published on 11 Jan 2023. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

A vulnerability was found in systemd. This security flaw can cause a local information leak due to systemd-coredump not respecting the fs.suid_dumpable kernel setting.

Weakness: CWE-200 (Exposure of Sensitive Information to an Unauthorized Actor)

## Which versions are affected by CVE-2022-4415?

It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `systemd` | AlmaLinux:8 | All versions | 239-68.el8_7.4 |
| `systemd-container` | AlmaLinux:8 | All versions | 239-68.el8_7.4 |
| `systemd-devel` | AlmaLinux:8 | All versions | 239-68.el8_7.4 |
| `systemd-journal-remote` | AlmaLinux:8 | All versions | 239-68.el8_7.4 |
| `systemd-libs` | AlmaLinux:8 | All versions | 239-68.el8_7.4 |
| `systemd-pam` | AlmaLinux:8 | All versions | 239-68.el8_7.4 |
| `systemd-tests` | AlmaLinux:8 | All versions | 239-68.el8_7.4 |
| `systemd-udev` | AlmaLinux:8 | All versions | 239-68.el8_7.4 |
| `systemd` | Red Hat:enterprise_linux:8::baseos | All versions | 0:239-68.el8_7.4 |
| `systemd-container` | Red Hat:enterprise_linux:8::baseos | All versions | 0:239-68.el8_7.4 |
| `systemd-container-debuginfo` | Red Hat:enterprise_linux:8::baseos | All versions | 0:239-68.el8_7.4 |
| `systemd-debuginfo` | Red Hat:enterprise_linux:8::baseos | All versions | 0:239-68.el8_7.4 |
| `systemd-debugsource` | Red Hat:enterprise_linux:8::baseos | All versions | 0:239-68.el8_7.4 |
| `systemd-devel` | Red Hat:enterprise_linux:8::baseos | All versions | 0:239-68.el8_7.4 |
| `systemd-journal-remote` | Red Hat:enterprise_linux:8::baseos | All versions | 0:239-68.el8_7.4 |
| `systemd-journal-remote-debuginfo` | Red Hat:enterprise_linux:8::baseos | All versions | 0:239-68.el8_7.4 |
| `systemd-libs` | Red Hat:enterprise_linux:8::baseos | All versions | 0:239-68.el8_7.4 |
| `systemd-libs-debuginfo` | Red Hat:enterprise_linux:8::baseos | All versions | 0:239-68.el8_7.4 |
| `systemd-pam` | Red Hat:enterprise_linux:8::baseos | All versions | 0:239-68.el8_7.4 |
| `systemd-pam-debuginfo` | Red Hat:enterprise_linux:8::baseos | All versions | 0:239-68.el8_7.4 |
| `systemd-tests` | Red Hat:enterprise_linux:8::baseos | All versions | 0:239-68.el8_7.4 |
| `systemd-tests-debuginfo` | Red Hat:enterprise_linux:8::baseos | All versions | 0:239-68.el8_7.4 |
| `systemd-udev` | Red Hat:enterprise_linux:8::baseos | All versions | 0:239-68.el8_7.4 |
| `systemd-udev-debuginfo` | Red Hat:enterprise_linux:8::baseos | All versions | 0:239-68.el8_7.4 |
| `systemd` | Rocky Linux:8 | All versions | 0:239-68.el8_7.4 |
| `systemd` | SUSE:Enterprise Storage 7.1 | All versions | 246.16-150300.7.57.1 |
| `systemd` | SUSE:Linux Enterprise High Performance Computing 15 SP3-ESPOS | All versions | 246.16-150300.7.57.1 |
| `systemd` | SUSE:Linux Enterprise High Performance Computing 15 SP3-LTSS | All versions | 246.16-150300.7.57.1 |
| `systemd` | SUSE:Linux Enterprise Micro 5.1 | All versions | 246.16-150300.7.57.1 |
| `systemd` | SUSE:Linux Enterprise Micro 5.2 | All versions | 246.16-150300.7.57.1 |
| `systemd` | SUSE:Linux Enterprise Micro 5.3 | All versions | 249.12-150400.8.16.1 |
| `systemd` | SUSE:Linux Enterprise Micro 5.3 | All versions | 249.14-150400.8.19.1 |
| `systemd` | SUSE:Linux Enterprise Module for Basesystem 15 SP3 | All versions | 246.16-150300.7.57.1 |
| `systemd` | SUSE:Linux Enterprise Module for Basesystem 15 SP4 | All versions | 249.12-150400.8.16.1 |
| `systemd` | SUSE:Linux Enterprise Module for Basesystem 15 SP4 | All versions | 249.14-150400.8.19.1 |
| `systemd` | SUSE:Linux Enterprise Real Time 15 SP3 | All versions | 246.16-150300.7.57.1 |
| `systemd` | SUSE:Linux Enterprise Server 12 SP5 | All versions | 228-157.46.1 |
| `systemd` | SUSE:Linux Enterprise Server 12 SP5 | All versions | 228-157.49.1 |
| `systemd` | SUSE:Linux Enterprise Server 15 SP3-LTSS | All versions | 246.16-150300.7.57.1 |
| `systemd` | SUSE:Linux Enterprise Server for SAP Applications 12 SP5 | All versions | 228-157.46.1 |

Products: Systemd Project Systemd.

## How do I fix CVE-2022-4415?

Apply the vendor's patch.

## Is CVE-2022-4415 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2022-4415 exists.

## 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-2022-4415 and fix it if it is affected.

What it is: CVE-2022-4415 is a medium-severity vulnerability in Systemd Project Systemd, published on 11 Jan 2023. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2022-4415 exists.

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-2022-4415/ (Markdown: https://insights.sbomify.com/CVE-2022-4415/index.md)
```

## Sources

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

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