Red Hat: CVE-2022-45873: deadlock in systemd-coredump via a crash with a long backtrace (Multiple Advisories)
Description
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.
Solution(s)
- redhat-upgrade-systemd
- redhat-upgrade-systemd-container
- redhat-upgrade-systemd-container-debuginfo
- redhat-upgrade-systemd-debuginfo
- redhat-upgrade-systemd-debugsource
- redhat-upgrade-systemd-devel
- redhat-upgrade-systemd-devel-debuginfo
- redhat-upgrade-systemd-journal-remote
- redhat-upgrade-systemd-journal-remote-debuginfo
- redhat-upgrade-systemd-libs
- redhat-upgrade-systemd-libs-debuginfo
- redhat-upgrade-systemd-oomd
- redhat-upgrade-systemd-oomd-debuginfo
- redhat-upgrade-systemd-pam
- redhat-upgrade-systemd-pam-debuginfo
- redhat-upgrade-systemd-resolved
- redhat-upgrade-systemd-resolved-debuginfo
- redhat-upgrade-systemd-rpm-macros
- redhat-upgrade-systemd-standalone-sysusers-debuginfo
- redhat-upgrade-systemd-standalone-tmpfiles-debuginfo
- redhat-upgrade-systemd-udev
- redhat-upgrade-systemd-udev-debuginfo
- Lightweight Endpoint Agent
- Live Dashboards
- Real Risk Prioritization
- IT-Integrated Remediation Projects
- Cloud, Virtual, and Container Assessment
- Integrated Threat Feeds
- Easy-to-Use RESTful API
- Automation-Assisted Patching
- Automated Containment
With Rapid7 live dashboards, I have a clear view of all the assets on my network, which ones can be exploited, and what I need to do in order to reduce the risk in my environment in real-time. No other tool gives us that kind of value and insight.
– Scott Cheney, Manager of Information Security, Sierra View Medical Center