Homepage
About Snyk

Deadlock The advisory has been revoked - it doesn't affect any version of package systemd Open this link in a new tab

    Threat Intelligence

    EPSS 0.04% (6th percentile)
Expand this section
NVD
5.5 medium
Expand this section
Red Hat
5.5 medium

Do your applications use this vulnerable package?

In a few clicks we can analyze your entire application and see what components are vulnerable in your application, and suggest you quick fixes.

Test your applications
  • Snyk ID SNYK-CENTOS8-SYSTEMD-3150592
  • published 29 Nov 2022
  • disclosed 18 Oct 2022
Report a new vulnerability Found a mistake?

Introduced: 18 Oct 2022

CVE-2022-45873 Open this link in a new tab
CWE-833 Open this link in a new tab

Amendment

The Centos security team deemed this advisory irrelevant for Centos:8.

NVD Description

Note: Versions mentioned in the description apply only to the upstream systemd package and not the systemd package as distributed by Centos.

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.