Two data disclosure flaws have been recognized in apport and systemd-coredump, the core dump handlers in Ubuntu, Purple Hat Enterprise Linux, and Fedora, in response to the Qualys Menace Analysis Unit (TRU).
Tracked as CVE-2025-5054 and CVE-2025-4598, each vulnerabilities are race situation bugs that might allow an area attacker to acquire entry to entry delicate data. Instruments like Apport and systemd-coredump are designed to deal with crash reporting and core dumps in Linux methods.
“These race situations enable an area attacker to use a SUID program and acquire learn entry to the ensuing core dump,” Saeed Abbasi, supervisor of product at Qualys TRU, mentioned.
A short description of the 2 flaws is beneath –
- CVE-2025-5054 (CVSS rating: 4.7) – A race situation in Canonical apport package deal as much as and together with 2.32.0 that enables an area attacker to leak delicate data through PID-reuse by leveraging namespaces
- CVE-2025-4598 (CVSS rating: 4.7) – A race situation in systemd-coredump that enables an attacker to power a SUID course of to crash and exchange it with a non-SUID binary to entry the unique’s privileged course of coredump, permitting the attacker to learn delicate information, similar to /and so forth/shadow content material, loaded by the unique course of
SUID, quick for Set Consumer ID, is a particular file permission that enables a person to execute a program with the privileges of its proprietor, fairly than their very own permissions.
“When analyzing utility crashes, apport makes an attempt to detect if the crashing course of was working inside a container earlier than performing consistency checks on it,” Canonical’s Octavio Galland mentioned.
“Because of this if an area attacker manages to induce a crash in a privileged course of and rapidly replaces it with one other one with the identical course of ID that resides inside a mount and pid namespace, apport will try to ahead the core dump (which could include delicate data belonging to the unique, privileged course of) into the namespace.”
Purple Hat mentioned CVE-2025-4598 has been rated Average in severity owing to the excessive complexity in pulling an exploit for the vulnerability, noting that the attacker has to first win the race situation and be in possession of an unprivileged native account.
As mitigations, Purple Hat mentioned customers can run the command “echo 0 > /proc/sys/fs/suid_dumpable” as a root person to disable the flexibility of a system to generate a core dump for SUID binaries.
The “/proc/sys/fs/suid_dumpable” parameter basically controls whether or not SUID packages can produce core dumps following a crash. By setting it to zero, it disables core dumps for all SUID packages and prevents them from being analyzed within the occasion of a crash.
“Whereas this mitigates this vulnerability whereas it isn’t potential to replace the systemd package deal, it disables the aptitude of analyzing crashes for such binaries,” Purple Hat mentioned.
Comparable advisories have been issued by Amazon Linux, Debian, and Gentoo. It is value noting that Debian methods aren’t vulnerable to CVE-2025-4598 by default, since they do not embrace any core dump handler except the systemd-coredump package deal is manually put in. CVE-2025-4598 doesn’t have an effect on Ubuntu releases.
Qualys has additionally developed proof-of-concept (PoC) code for each vulnerabilities, demonstrating how an area attacker can exploit the coredump of a crashed unix_chkpwd course of, which is used to confirm the validity of a person’s password, to acquire password hashes from the /and so forth/shadow file.
Canonical, in an alert of its personal, mentioned the impression of CVE-2025-5054 is restricted to the confidentiality of the reminiscence area of invoked SUID executables and that the PoC exploit can leak hashed person passwords has restricted real-world impression.
“The exploitation of vulnerabilities in Apport and systemd-coredump can severely compromise the confidentiality at excessive danger, as attackers might extract delicate information, like passwords, encryption keys, or buyer data from core dumps,” Abbasi mentioned.
“The fallout consists of operational downtime, reputational injury, and potential non-compliance with rules. To mitigate these multifaceted dangers successfully, enterprises ought to undertake proactive safety measures by prioritizing patches and mitigations, implementing strong monitoring, and tightening entry controls.”
