CVE-2022-45873
Systemd Coredump Deadlock Local Denial of Service
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.
INFO
Published Date :
Nov. 23, 2022, 11:15 p.m.
Last Modified :
Nov. 7, 2023, 3:54 a.m.
Source :
[email protected]
Remotely Exploitable :
No
Impact Score :
3.6
Exploitability Score :
1.8
Affected Products
The following products are affected by CVE-2022-45873
vulnerability.
Even if cvefeed.io
is aware of the exact versions of the
products
that
are
affected, the information is not represented in the table below.
References to Advisories, Solutions, and Tools
Here, you will find a curated list of external links that provide in-depth
information, practical solutions, and valuable tools related to
CVE-2022-45873
.
URL | 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/ |
We scan GitHub repositories to detect new proof-of-concept exploits. Following list is a collection of public exploits and proof-of-concepts, which have been published on GitHub (sorted by the most recently updated).
Results are limited to the first 15 repositories due to potential performance issues.
The following list is the news that have been mention
CVE-2022-45873
vulnerability anywhere in the article.
The following table lists the changes that have been made to the
CVE-2022-45873
vulnerability over time.
Vulnerability history details can be useful for understanding the evolution of a vulnerability, and for identifying the most recent changes that may impact the vulnerability's severity, exploitability, or other characteristics.
-
CVE Modified by [email protected]
May. 14, 2024
Action Type Old Value New Value -
CVE Modified by [email protected]
Nov. 07, 2023
Action Type Old Value New Value Added Reference MITRE https://lists.fedoraproject.org/archives/list/package-announce%40lists.fedoraproject.org/message/MS5N5SLYAHKENLAJWYBDKU55ICU3SVZF/ [No types assigned] Removed Reference MITRE https://lists.fedoraproject.org/archives/list/[email protected]/message/MS5N5SLYAHKENLAJWYBDKU55ICU3SVZF/ -
Modified Analysis by [email protected]
Mar. 01, 2023
Action Type Old Value New Value Changed Reference Type https://lists.fedoraproject.org/archives/list/[email protected]/message/MS5N5SLYAHKENLAJWYBDKU55ICU3SVZF/ No Types Assigned https://lists.fedoraproject.org/archives/list/[email protected]/message/MS5N5SLYAHKENLAJWYBDKU55ICU3SVZF/ Mailing List, Third Party Advisory Added CPE Configuration OR *cpe:2.3:o:fedoraproject:fedora:36:*:*:*:*:*:*:* -
CVE Modified by [email protected]
Dec. 31, 2022
Action Type Old Value New Value Added Reference https://lists.fedoraproject.org/archives/list/[email protected]/message/MS5N5SLYAHKENLAJWYBDKU55ICU3SVZF/ [No Types Assigned] -
Initial Analysis by [email protected]
Dec. 01, 2022
Action Type Old Value New Value Added CVSS V3.1 NIST AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H Changed Reference Type https://github.com/systemd/systemd/commit/076b807be472630692c5348c60d0c2b7b28ad437 No Types Assigned https://github.com/systemd/systemd/commit/076b807be472630692c5348c60d0c2b7b28ad437 Patch, Third Party Advisory Changed Reference Type https://github.com/systemd/systemd/pull/24853#issuecomment-1326561497 No Types Assigned https://github.com/systemd/systemd/pull/24853#issuecomment-1326561497 Issue Tracking, Patch, Third Party Advisory Changed Reference Type https://github.com/systemd/systemd/pull/25055#issuecomment-1313733553 No Types Assigned https://github.com/systemd/systemd/pull/25055#issuecomment-1313733553 Issue Tracking, Patch, Third Party Advisory Added CWE NIST CWE-400 Added CPE Configuration OR *cpe:2.3:a:systemd_project:systemd:*:*:*:*:*:*:*:* versions from (including) 250 up to (including) 251 *cpe:2.3:a:systemd_project:systemd:252:rc1:*:*:*:*:*:* *cpe:2.3:a:systemd_project:systemd:252:rc2:*:*:*:*:*:* -
CVE Modified by [email protected]
Nov. 25, 2022
Action Type Old Value New Value Changed 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. NOTE: there is some debate about the security relevance of this report because there are zero subscribers by default. 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 Modified by [email protected]
Nov. 25, 2022
Action Type Old Value New Value Changed 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. 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. NOTE: there is some debate about the security relevance of this report because there are zero subscribers by default. Added Reference https://github.com/systemd/systemd/pull/24853#issuecomment-1326561497 [No Types Assigned]
CWE - Common Weakness Enumeration
While CVE identifies
specific instances of vulnerabilities, CWE categorizes the common flaws or
weaknesses that can lead to vulnerabilities. CVE-2022-45873
is
associated with the following CWEs:
Common Attack Pattern Enumeration and Classification (CAPEC)
Common Attack Pattern Enumeration and Classification
(CAPEC)
stores attack patterns, which are descriptions of the common attributes and
approaches employed by adversaries to exploit the CVE-2022-45873
weaknesses.
Exploit Prediction
EPSS is a daily estimate of the probability of exploitation activity being observed over the next 30 days.
0.04 }} 0.00%
score
0.05635
percentile