CVE-2022-45873: Medium severity Systemd Project Systemd vulnerability
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 parseelfobject 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.
Affected Software
Remediation
Recommended actions to resolve this vulnerability, in priority order.
- Upgrade
Upgrade
redhat/systemdto a version that resolves this vulnerability.Fixed in 252 - Upgrade
Upgrade
systemdto a version that resolves this vulnerability.Patch systemd 250 and 251 allows local users to achieve a systemd-coredump deadlock by triggering a crash that has a long backtrace
Event History
Frequently Asked Questions
What is CVE-2022-45873?
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.
How severe is CVE-2022-45873?
CVE-2022-45873 has a severity rating of 5.5 (Medium).
How does CVE-2022-45873 affect the affected software?
CVE-2022-45873 affects systemd versions 250 and 251, as well as version 252-rc1 and version 252-rc2. It also affects Fedora 36.
What is the exploitation methodology for CVE-2022-45873?
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.
Are there any references available for CVE-2022-45873?
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).