CVE-2025-4598 : Détail

CVE-2025-4598

4.7
/
Moyen
0.11%V4
Local
2025-05-30
13h13 +00:00
2026-09-01
11h51 +00:00
Notifications pour un CVE
Restez informé de toutes modifications pour un CVE spécifique.
Gestion des notifications

Descriptions du CVE

Systemd-coredump: race condition that allows a local attacker to crash a suid program and gain read access to the resulting core dump

A vulnerability was found in systemd-coredump. This flaw allows an attacker to force a SUID process to crash and replace it with a non-SUID binary to access the original's privileged process coredump, allowing the attacker to read sensitive data, such as /etc/shadow content, loaded by the original process. A SUID binary or process has a special type of permission, which allows the process to run with the file owner's permissions, regardless of the user executing the binary. This allows the process to access more restricted data than unprivileged users or processes would be able to. An attacker can leverage this flaw by forcing a SUID process to crash and force the Linux kernel to recycle the process PID before systemd-coredump can analyze the /proc/pid/auxv file. If the attacker wins the race condition, they gain access to the original's SUID process coredump file. They can read sensitive content loaded into memory by the original binary, affecting data confidentiality.

Informations du CVE

Faiblesses connexes

CWE-ID Nom de la faiblesse Source
CWE-364 Signal Handler Race Condition
The product uses a signal handler that introduces a race condition.

Métriques

Métriques Score Gravité CVSS Vecteur Source
V3.1 4.7 MEDIUM CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:H/I:N/A:N

Base: Exploitabilty Metrics

The Exploitability metrics reflect the characteristics of the thing that is vulnerable, which we refer to formally as the vulnerable component.

Attack Vector

This metric reflects the context by which vulnerability exploitation is possible.

Local

The vulnerable component is not bound to the network stack and the attacker’s path is via read/write/execute capabilities.

Attack Complexity

This metric describes the conditions beyond the attacker’s control that must exist in order to exploit the vulnerability.

High

successful attack depends on conditions beyond the attacker's control. That is, a successful attack cannot be accomplished at will, but requires the attacker to invest in some measurable amount of effort in preparation or execution against the vulnerable component before a successful attack can be expected.

Privileges Required

This metric describes the level of privileges an attacker must possess before successfully exploiting the vulnerability.

Low

The attacker requires privileges that provide basic user capabilities that could normally affect only settings and files owned by a user. Alternatively, an attacker with Low privileges has the ability to access only non-sensitive resources.

User Interaction

This metric captures the requirement for a human user, other than the attacker, to participate in the successful compromise of the vulnerable component.

None

The vulnerable system can be exploited without interaction from any user.

Base: Scope Metrics

The Scope metric captures whether a vulnerability in one vulnerable component impacts resources in components beyond its security scope.

Scope

Formally, a security authority is a mechanism (e.g., an application, an operating system, firmware, a sandbox environment) that defines and enforces access control in terms of how certain subjects/actors (e.g., human users, processes) can access certain restricted objects/resources (e.g., files, CPU, memory) in a controlled manner. All the subjects and objects under the jurisdiction of a single security authority are considered to be under one security scope. If a vulnerability in a vulnerable component can affect a component which is in a different security scope than the vulnerable component, a Scope change occurs. Intuitively, whenever the impact of a vulnerability breaches a security/trust boundary and impacts components outside the security scope in which vulnerable component resides, a Scope change occurs.

Unchanged

An exploited vulnerability can only affect resources managed by the same security authority. In this case, the vulnerable component and the impacted component are either the same, or both are managed by the same security authority.

Base: Impact Metrics

The Impact metrics capture the effects of a successfully exploited vulnerability on the component that suffers the worst outcome that is most directly and predictably associated with the attack. Analysts should constrain impacts to a reasonable, final outcome which they are confident an attacker is able to achieve.

Confidentiality Impact

This metric measures the impact to the confidentiality of the information resources managed by a software component due to a successfully exploited vulnerability.

High

There is a total loss of confidentiality, resulting in all resources within the impacted component being divulged to the attacker. Alternatively, access to only some restricted information is obtained, but the disclosed information presents a direct, serious impact. For example, an attacker steals the administrator's password, or private encryption keys of a web server.

Integrity Impact

This metric measures the impact to integrity of a successfully exploited vulnerability. Integrity refers to the trustworthiness and veracity of information.

None

There is no loss of integrity within the impacted component.

Availability Impact

This metric measures the impact to the availability of the impacted component resulting from a successfully exploited vulnerability.

None

There is no impact to availability within the impacted component.

Temporal Metrics

The Temporal metrics measure the current state of exploit techniques or code availability, the existence of any patches or workarounds, or the confidence in the description of a vulnerability.

Environmental Metrics

These metrics enable the analyst to customize the CVSS score depending on the importance of the affected IT asset to a user’s organization, measured in terms of Confidentiality, Integrity, and Availability.

EPSS

EPSS est un modèle de notation qui prédit la probabilité qu'une vulnérabilité soit exploitée.

Score EPSS

Le modèle EPSS produit un score de probabilité compris entre 0 et 1 (0 et 100 %). Plus la note est élevée, plus la probabilité qu'une vulnérabilité soit exploitée est grande.

Percentile EPSS

Le percentile est utilisé pour classer les CVE en fonction de leur score EPSS. Par exemple, une CVE dans le 95e percentile selon son score EPSS est plus susceptible d'être exploitée que 95 % des autres CVE. Ainsi, le percentile sert à comparer le score EPSS d'une CVE par rapport à d'autres CVE.

Products Mentioned

Configuraton 0

Systemd_project>>Systemd >> Version To (excluding) 252.37

Systemd_project>>Systemd >> Version From (including) 253 To (excluding) 253.32

Systemd_project>>Systemd >> Version From (including) 254 To (excluding) 254.25

Systemd_project>>Systemd >> Version From (including) 255 To (excluding) 255.19

Systemd_project>>Systemd >> Version From (including) 256 To (excluding) 256.14

Systemd_project>>Systemd >> Version From (including) 257 To (excluding) 257.6

Configuraton 0

Redhat>>Openshift_container_platform >> Version 4.0

Redhat>>Enterprise_linux >> Version 7.0

Redhat>>Enterprise_linux >> Version 8.0

Redhat>>Enterprise_linux >> Version 9.0

Redhat>>Enterprise_linux >> Version 10.0

Configuraton 0

Debian>>Debian_linux >> Version 11.0

Debian>>Debian_linux >> Version 12.0

Configuraton 0

Oracle>>Linux >> Version 8

Oracle>>Linux >> Version 9

Configuraton 0

Linux>>Linux_kernel >> Version To (excluding) 6.16

Références

https://access.redhat.com/errata/RHSA-2025:22660
Tags : vendor-advisory, x_refsource_REDHAT
https://access.redhat.com/errata/RHSA-2025:22868
Tags : vendor-advisory, x_refsource_REDHAT
https://access.redhat.com/errata/RHSA-2025:23227
Tags : vendor-advisory, x_refsource_REDHAT
https://access.redhat.com/errata/RHSA-2025:23234
Tags : vendor-advisory, x_refsource_REDHAT
https://access.redhat.com/errata/RHSA-2026:0414
Tags : vendor-advisory, x_refsource_REDHAT
https://access.redhat.com/errata/RHSA-2026:1652
Tags : vendor-advisory, x_refsource_REDHAT
https://access.redhat.com/errata/RHSA-2026:18153
Tags : vendor-advisory, x_refsource_REDHAT
https://access.redhat.com/security/cve/CVE-2025-4598
Tags : vdb-entry, x_refsource_REDHAT
https://bugzilla.redhat.com/show_bug.cgi?id=2369242
Tags : issue-tracking, x_refsource_REDHAT
https://www.openwall.com/lists/oss-security/2025/08/18/3
Tags : Mailing List, Third Party Advisory