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.

The remote host is affected by the vulnerability described in GLSA-202405-04 (systemd: Multiple Vulnerabilities)

  - A vulnerability was found in systemd. This security flaw can cause a local information leak due to     systemd-coredump not respecting the fs.suid_dumpable kernel setting. (CVE-2022-4415)

  - 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. (CVE-2022-45873)

Note that Nessus has not tested for these issues but has instead relied only on the application's self-reported version number.

The remote Rocky Linux 9 host has packages installed that are affected by multiple vulnerabilities as referenced in the RLSA-2023:0954 advisory.

  - A vulnerability was found in systemd. This security flaw can cause a local information leak due to     systemd-coredump not respecting the fs.suid_dumpable kernel setting. (CVE-2022-4415)

  - 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. (CVE-2022-45873)

Note that Nessus has not tested for these issues but has instead relied only on the application's self-reported version number.

It is, therefore, affected by multiple vulnerabilities as referenced in the ALAS2023-2023-025 advisory.

  - A flaw was found in systemd. An uncontrolled recursion in systemd-tmpfiles may lead to a denial of service     at boot time when too many nested directories are created in /tmp. (CVE-2021-3997)

  - A vulnerability was found in systemd. This security flaw can cause a local information leak due to     systemd-coredump not respecting the fs.suid_dumpable kernel setting. (CVE-2022-4415)

  - 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. (CVE-2022-45873)

Note that Nessus has not tested for these issues but has instead relied only on the application's self-reported version number.

The version of systemd / systemd-bootstrap installed on the remote CBL Mariner 2.0 host is prior to tested version. It is, therefore, affected by a vulnerability as referenced in the CVE-2022-45873 advisory.

  - 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. (CVE-2022-45873)

Note that Nessus has not tested for this issue but has instead relied only on the application's self-reported version number.

The remote Ubuntu 16.04 ESM / 18.04 LTS / 20.04 LTS / 22.04 LTS host has packages installed that are affected by multiple vulnerabilities as referenced in the USN-5928-1 advisory.

    It was discovered that systemd did not properly validate the time and accuracy values provided to the     format_timespan() function. An attacker could possibly use this issue to cause a buffer overrun, leading     to a denial of service attack. This issue only affected Ubuntu 14.04 ESM, Ubuntu 16.04 ESM, Ubuntu 18.04     LTS, Ubuntu 20.04 LTS, and Ubuntu 22.04 LTS. (CVE-2022-3821)

    It was discovered that systemd did not properly manage the fs.suid_dumpable kernel configurations. A local     attacker could possibly use this issue to expose sensitive information. This issue only affected Ubuntu     20.04 LTS, Ubuntu 22.04 LTS, and Ubuntu 22.10. (CVE-2022-4415)

    It was discovered that systemd did not properly manage a crash with long backtrace data. A local attacker     could possibly use this issue to cause a deadlock, leading to a denial of service attack. This issue only     affected Ubuntu 22.10. (CVE-2022-45873)

Tenable has extracted the preceding description block directly from the Ubuntu security advisory.

Note that Nessus has not tested for these issues but has instead relied only on the application's self-reported version number.

The remote Oracle Linux 9 host has packages installed that are affected by multiple vulnerabilities as referenced in the ELSA-2023-0954 advisory.

    [250-12.0.2.3]
    - Backport upstream pstore dmesg fix [Orabug: 34868110]
    - Remove upstream references  [Orabug: 33995357]
    - Disable unprivileged BPF by default [Orabug: 32870980]
    - udev rules: fix memory hot add and remove [Orabug: 31310273]
    - set 'RemoveIPC=no' in logind.conf as default for OL7.2 [Orabug: 22224874]
    - allow dm remove ioctl to co-operate with UEK3 (Vaughan Cao) [Orabug: 18467469]
    - fix _netdev is missing for iscsi entry in /etc/fstab (tony.l.lam@oracle.com) [Orabug: 25897792]
    - shutdown: get only active md arrays. [Orabug: 34467234]

    [250-12.3]
    - shared/json: allow json_variant_dump() to return an error (#2149074)
    - shared/json: use different return code for empty input (#2149074)
    - coredump: avoid deadlock when passing processed backtrace data (#2149074)
    - test: disable flaky subtests that require udevadm wait/lock (#2149074)

    [250-12.2]
    - coredump: adjust whitespace (#2155516)
    - basic: add STRERROR() wrapper for strerror_r() (#2155516)
    - coredump: do not allow user to access coredumps with changed uid/gid/capabilities (#2155516)
    - Packit: build SRPMs in Copr (#2155516)
    - test: support non-summer time (#2155516)
    - test: bump the base VM memory to 768M (#2155516)
    - test: don't overwrite existing  (#2155516)

Tenable has extracted the preceding description block directly from the Oracle Linux security advisory.

Note that Nessus has not tested for these issues but has instead relied only on the application's self-reported version number.

The remote AlmaLinux 9 host has packages installed that are affected by multiple vulnerabilities as referenced in the ALSA-2023:0954 advisory.

  - A vulnerability was found in systemd. This security flaw can cause a local information leak due to     systemd-coredump not respecting the fs.suid_dumpable kernel setting. (CVE-2022-4415)

  - 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. (CVE-2022-45873)

Note that Nessus has not tested for these issues but has instead relied only on the application's self-reported version number.

The remote Redhat Enterprise Linux 9 host has packages installed that are affected by multiple vulnerabilities as referenced in the RHSA-2023:0954 advisory.

    The systemd packages contain systemd, a system and service manager for Linux, compatible with the SysV and     LSB init scripts. It provides aggressive parallelism capabilities, uses socket and D-Bus activation for     starting services, offers on-demand starting of daemons, and keeps track of processes using Linux cgroups.
    In addition, it supports snapshotting and restoring of the system state, maintains mount and automount     points, and implements an elaborate transactional dependency-based service control logic. It can also work     as a drop-in replacement for sysvinit.

    Security Fix(es):

    * systemd: local information leak due to systemd-coredump not respecting fs.suid_dumpable kernel setting     (CVE-2022-4415)

    * systemd: deadlock in systemd-coredump via a crash with a long backtrace (CVE-2022-45873)

    For more details about the security issue(s), including the impact, a CVSS score, acknowledgments, and     other related information, refer to the CVE page(s) listed in the References section.

Tenable has extracted the preceding description block directly from the Red Hat Enterprise Linux security advisory.

Note that Nessus has not tested for these issues but has instead relied only on the application's self-reported version number.

The remote Fedora 36 host has a package installed that is affected by multiple vulnerabilities as referenced in the FEDORA-2022-ef4f57b072 advisory.

  - 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. (CVE-2022-45873)

  - local information leak due to systemd-coredump not respecting fs.suid_dumpable kernel setting [fedora-37]     (CVE-2022-4415)

Note that Nessus has not tested for these issues but has instead relied only on the application's self-reported version number.

ID	Name	Product	Family	Severity
194972	GLSA-202405-04 : systemd: Multiple Vulnerabilities	Nessus	Gentoo Local Security Checks	medium
173982	Rocky Linux 9 : systemd (RLSA-2023:0954)	Nessus	Rocky Linux Local Security Checks	medium
173143	Amazon Linux 2023 : systemd, systemd-container, systemd-devel (ALAS2023-2023-025)	Nessus	Amazon Linux Local Security Checks	medium
172763	CBL Mariner 2.0 Security Update: systemd / systemd-bootstrap (CVE-2022-45873)	Nessus	MarinerOS Local Security Checks	medium
172227	Ubuntu 16.04 ESM / 18.04 LTS / 20.04 LTS / 22.04 LTS : systemd vulnerabilities (USN-5928-1)	Nessus	Ubuntu Local Security Checks	medium
172037	Oracle Linux 9 : systemd (ELSA-2023-0954)	Nessus	Oracle Linux Local Security Checks	medium
172002	AlmaLinux 9 : systemd (ALSA-2023:0954)	Nessus	Alma Linux Local Security Checks	medium
171981	RHEL 9 : systemd (RHSA-2023:0954)	Nessus	Red Hat Local Security Checks	medium
169431	Fedora 36 : systemd (2022-ef4f57b072)	Nessus	Fedora Local Security Checks	medium

Detections

Analytics

CVE-2022-45873

medium

Tenable Plugins

medium

medium

medium

medium

medium

medium

medium

medium

medium