GHSA-JX2M-WGQ5-5QCJ
Vulnerability from github – Published: 2025-05-30 15:30 – Updated: 2025-12-08 21:30A 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.
{
"affected": [],
"aliases": [
"CVE-2025-4598"
],
"database_specific": {
"cwe_ids": [
"CWE-364"
],
"github_reviewed": false,
"github_reviewed_at": null,
"nvd_published_at": "2025-05-30T14:15:23Z",
"severity": "MODERATE"
},
"details": "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\u0027s privileged process coredump, allowing the attacker to read sensitive data, such as /etc/shadow content, loaded by the original process.\n\nA SUID binary or process has a special type of permission, which allows the process to run with the file owner\u0027s 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\u0027s SUID process coredump file. They can read sensitive content loaded into memory by the original binary, affecting data confidentiality.",
"id": "GHSA-jx2m-wgq5-5qcj",
"modified": "2025-12-08T21:30:18Z",
"published": "2025-05-30T15:30:31Z",
"references": [
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2025-4598"
},
{
"type": "WEB",
"url": "https://access.redhat.com/errata/RHSA-2025:22660"
},
{
"type": "WEB",
"url": "https://access.redhat.com/errata/RHSA-2025:22868"
},
{
"type": "WEB",
"url": "https://access.redhat.com/security/cve/CVE-2025-4598"
},
{
"type": "WEB",
"url": "https://blogs.oracle.com/linux/post/analysis-of-cve-2025-4598"
},
{
"type": "WEB",
"url": "https://bugzilla.redhat.com/show_bug.cgi?id=2369242"
},
{
"type": "WEB",
"url": "https://ciq.com/blog/the-real-danger-of-systemd-coredump-cve-2025-4598"
},
{
"type": "WEB",
"url": "https://lists.debian.org/debian-lts-announce/2025/07/msg00022.html"
},
{
"type": "WEB",
"url": "https://www.openwall.com/lists/oss-security/2025/05/29/3"
},
{
"type": "WEB",
"url": "https://www.openwall.com/lists/oss-security/2025/08/18/3"
},
{
"type": "WEB",
"url": "http://seclists.org/fulldisclosure/2025/Jun/9"
},
{
"type": "WEB",
"url": "http://www.openwall.com/lists/oss-security/2025/06/05/1"
},
{
"type": "WEB",
"url": "http://www.openwall.com/lists/oss-security/2025/06/05/3"
},
{
"type": "WEB",
"url": "http://www.openwall.com/lists/oss-security/2025/08/18/3"
}
],
"schema_version": "1.4.0",
"severity": [
{
"score": "CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:H/I:N/A:N",
"type": "CVSS_V3"
}
]
}
Sightings
| Author | Source | Type | Date |
|---|
Nomenclature
- Seen: The vulnerability was mentioned, discussed, or observed by the user.
- Confirmed: The vulnerability has been validated from an analyst's perspective.
- Published Proof of Concept: A public proof of concept is available for this vulnerability.
- Exploited: The vulnerability was observed as exploited by the user who reported the sighting.
- Patched: The vulnerability was observed as successfully patched by the user who reported the sighting.
- Not exploited: The vulnerability was not observed as exploited by the user who reported the sighting.
- Not confirmed: The user expressed doubt about the validity of the vulnerability.
- Not patched: The vulnerability was not observed as successfully patched by the user who reported the sighting.