Deadlock The advisory has been revoked - it doesn't affect any version of package NetworkManager-tui  (opens in a new tab)


Threat Intelligence

EPSS
0.27% (20th percentile)

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 IDSNYK-RHEL8-NETWORKMANAGERTUI-3150619
  • published29 Nov 2022
  • disclosed18 Oct 2022

Introduced: 18 Oct 2022

CVE-2022-45873  (opens in a new tab)
CWE-833  (opens in a new tab)

Amendment

The Red Hat security team deemed this advisory irrelevant for RHEL:8.

NVD Description

Note: Versions mentioned in the description apply only to the upstream NetworkManager-tui package and not the NetworkManager-tui package as distributed by RHEL.

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.