First published: Wed Nov 23 2022(Updated: )
systemd 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.
Credit: cve@mitre.org cve@mitre.org
Affected Software | Affected Version | How to fix |
---|---|---|
Systemd Project Systemd | >=250<=251 | |
Systemd Project Systemd | =252-rc1 | |
Systemd Project Systemd | =252-rc2 | |
Fedoraproject Fedora | =36 | |
redhat/systemd | <252 | 252 |
>=250<=251 | ||
=252-rc1 | ||
=252-rc2 | ||
=36 |
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
CVE-2022-45873 is a vulnerability in systemd which allows local users to achieve a systemd-coredump deadlock by triggering a crash that has a long backtrace, and it occurs in parse_elf_object in shared/elf-util.c.
CVE-2022-45873 has a severity rating of 5.5 (Medium).
CVE-2022-45873 affects systemd versions 250 and 251, as well as version 252-rc1 and version 252-rc2. It also affects Fedora 36.
The exploitation methodology for CVE-2022-45873 is to crash a binary calling the same function recursively and put it in a deeply nested state.
Yes, you can find references for CVE-2022-45873 by visiting the following links: [GitHub commit](https://github.com/systemd/systemd/commit/076b807be472630692c5348c60d0c2b7b28ad437), [GitHub pull request](https://github.com/systemd/systemd/pull/24853#issuecomment-1326561497), [GitHub pull request](https://github.com/systemd/systemd/pull/25055#issuecomment-1313733553).