You are viewing this page in an unauthorized frame window.
This is a potential security issue, you are being redirected to
https://nvd.nist.gov
An official website of the United States government
Official websites use .gov
A .gov website belongs to an official government organization in the United States.
Secure .gov websites use HTTPS
A lock () or https:// means you've safely connected to the .gov website. Share sensitive information only on official, secure websites.
The NVD has a
new announcement page with status updates, news, and how
to stay connected!
CVE-2022-45873
Detail
Modified
This vulnerability has been modified since it was last analyzed by the NVD. It is awaiting reanalysis which may result in further changes to the information provided.
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.
Metrics
NVD enrichment efforts reference publicly available information to associate
vector strings. CVSS information contributed by other sources is also
displayed.
By selecting these links, you will be leaving NIST webspace.
We have provided these links to other web sites because they
may have information that would be of interest to you. No
inferences should be drawn on account of other sites being
referenced, or not, from this page. There may be other web
sites that are more appropriate for your purpose. NIST does
not necessarily endorse the views expressed, or concur with
the facts presented on these sites. Further, NIST does not
endorse any commercial products that may be mentioned on
these sites. Please address comments about this page to nvd@nist.gov.
OR
*cpe:2.3:o:fedoraproject:fedora:36:*:*:*:*:*:*:*
Changed
Reference Type
https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/MS5N5SLYAHKENLAJWYBDKU55ICU3SVZF/ No Types Assigned
https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/MS5N5SLYAHKENLAJWYBDKU55ICU3SVZF/ Mailing List, Third Party Advisory
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:*:*:*:*:*:*
Added
CVSS V3.1
NIST AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
Added
CWE
NIST CWE-400
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
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 deb
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 MITRE11/25/2022 1:15:10 AM
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 deb
) or https:// means you've safely connected to the .gov website. Share sensitive information only on official, secure websites.
