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.
References
Link | Resource |
---|---|
https://github.com/systemd/systemd/commit/076b807be472630692c5348c60d0c2b7b28ad437 | Patch Third Party Advisory |
https://github.com/systemd/systemd/pull/24853#issuecomment-1326561497 | Issue Tracking Patch Third Party Advisory |
https://github.com/systemd/systemd/pull/25055#issuecomment-1313733553 | Issue Tracking Patch Third Party Advisory |
https://lists.fedoraproject.org/archives/list/package-announce%40lists.fedoraproject.org/message/MS5N5SLYAHKENLAJWYBDKU55ICU3SVZF/ |
Configurations
History
07 Nov 2023, 03:54
Type | Values Removed | Values Added |
---|---|---|
References |
|
|
Information
Published : 2022-11-23 23:15
Updated : 2024-02-28 19:51
NVD link : CVE-2022-45873
Mitre link : CVE-2022-45873
CVE.ORG link : CVE-2022-45873
JSON object : View
Products Affected
fedoraproject
- fedora
systemd_project
- systemd
CWE
CWE-400
Uncontrolled Resource Consumption