ID: CVE-2022-45873

Last Modified: Dec. 1, 2022

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.

Twitter Activity

Tweets last week: 3

Remaining steady

Yahoo Activity

Yahoo results: 0

Remaining steady

EPSS History

Current EPSS Score: 0.0089

Remaining steady


Reddit Activity

Reddit Posts: 1

Remaining steady

Github Repos

Github Repos: 0

Remaining steady

Exploits

Found exploits:

Attack Vector: Local

Attack Complexity: Low

Privileges Required: Low

User Interaction: None

Scope: Unchanged

Confidentiality: None

Integrity: None

Availability: High

Base Score: 5.5

Exploitability Score: 1.8

Impact Score: 3.6

CVSS V3: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H

Specialize CVSS-Score

CWE-400

Condition Configuration
OR
OR
Alle Schwachstellen für systemd_project
Alle Schwachstellen für systemd_project
Alle Schwachstellen für systemd_project
Date: Nov. 25, 2022

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.
Reference:
added:
https://github.com/systemd/systemd/pull/24853#issuecomment-1326561497



Date: Nov. 25, 2022

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.



Date: Dec. 1, 2022

CWE-ID: Not defined
Base Score V3: Not defined
Exploitability Score V3: Not defined
Impact Score V3: Not defined
Cvss Vector V3: Not defined
Configuration:
added:
cpe:2.3:a:systemd_project:systemd:*:*:*:*:*:*:*:*
cpe:2.3:a:systemd_project:systemd:252:rc1:*:*:*:*:*:*
cpe:2.3:a:systemd_project:systemd:252:rc2:*:*:*:*:*:*



                    <?xml version="1.0" ?>
<set operator="and">
    <set operator="or">
        <prop key="application" value="cpe:2.3:a:systemd_project:systemd:*:*:*:*:*:*:*:*"/>
        <prop key="application" value="cpe:2.3:a:systemd_project:systemd:252:rc1:*:*:*:*:*:*"/>
        <prop key="application" value="cpe:2.3:a:systemd_project:systemd:252:rc2:*:*:*:*:*:*"/>
    </set>
</set>

                  
                      <?xml version="1.0" ?>
<set operator="and">
    <set operator="or">
        <prop key="application" value="cpe:2.3:a:systemd_project:systemd:*:*:*:*:*:*:*:*"/>
        <prop key="application" value="cpe:2.3:a:systemd_project:systemd:252:rc1:*:*:*:*:*:*"/>
        <prop key="application" value="cpe:2.3:a:systemd_project:systemd:252:rc2:*:*:*:*:*:*"/>
    </set>
    <prop key="program_influence" value="input"/>
</set>