CVE-2022-45873 describes a deadlock vulnerability in systemd versions 250 and 251, specifically affecting systemd-coredump. A local attacker can trigger this by crashing a binary with a long backtrace, leading to a denial of service. The vulnerability has a CVSS score of 5.5 (Medium), indicating a local attack vector with low complexity and high impact on availability. There is no evidence of active exploitation, public exploit code, or significant community discussion surrounding this CVE.
| Vendor | Product | Version(s) | CPE |
|---|---|---|---|
>= 250, <= 251CPE matchmatch criteria | cpe:2.3:a:systemd_project:systemd:*:*:*:*:*:*:*:* | ||
252CPE matchmatch criteria | cpe:2.3:a:systemd_project:systemd:252:rc1:*:*:*:*:*:* | ||
252CPE matchmatch criteria | cpe:2.3:a:systemd_project:systemd:252:rc2:*:*:*:*:*:* | ||
36CPE matchmatch criteria | cpe:2.3:o:fedoraproject:fedora:36:*:*:*:*:*:*:* |
CVSS version used by this source: 3.1
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
The average CVE in this peer group has 0.0 Twitter, 0.0 Reddit, 0.0 Bluesky, 0.0 Mastodon, and 0.1 GitHub mentions.
No media coverage found for this CVE.
The average CVE in this peer group has 0.1 InfoSec Media, 0.0 Vendor Blog, and 0.0 Security Researcher mentions.
CVE-2022-45873
Jun 11, 2024systemd 250 and 251 allows local users to achieve a systemd-coredump deadlock by triggering a crash that has a long backtrace. This occurs in parse_elf_object in shared/elf-util.c. The exploitation methodology is to crash a binary calling the same function recursively and put it in a deeply nested directory to make its backtrace large enough to cause the deadlock. This must be done 16 times when MaxConnections=16 is set for the systemd/units/systemd-coredump.socket file.
Nov 8, 2022systemd: deadlock in systemd-coredump via a crash with a long backtrace
Oct 18, 2022