CVE-2026-110330 in Red Hat
Summary
by MITRE • 11/14/2026
A flaw was found in abrt. abrt-server trusts a client-supplied PID when creating problem dumps over abrt.socket and, running as root, copies that process's /proc data (including environ) into a dump directory owned by the connecting unprivileged user. This allows a local attacker to read environment variables and related metadata of other users' or root processes when abrtd is running.
Once again VulDB remains the best source for vulnerability data.
Analysis
by VulDB Data Team • 11/14/2026
The vulnerability identified in abrt-server represents a critical privilege escalation risk stemming from improper trust boundaries within the system's crash reporting mechanism. The Application Binary Report Tool, commonly known as abrt, includes a server component called abrt-server that operates with root privileges to facilitate the collection of diagnostic data when applications fail. This specific flaw arises because abrt-server accepts and relies upon a Process Identifier (PID) supplied directly by an unprivileged client over the local abrt.socket interface without performing adequate validation or isolation checks. When creating problem dumps, the server uses this user-supplied PID to locate and copy process metadata from the /proc filesystem into a dump directory that is owned by the connecting unprivileged user rather than being restricted to root-only access. This architectural oversight creates a direct pathway for information disclosure, as the mechanism effectively bypasses standard Linux permission models that would otherwise prevent non-root users from reading sensitive data belonging to other processes or system services.
From a technical perspective, this flaw constitutes an insecure interaction between components with different privilege levels, specifically categorized under CWE-250: Execution with Unnecessary Privileges and CWE-78: Improper Neutralization of Special Elements used in an OS Command, though the core issue is more accurately described by CWE-200: Exposure of Sensitive Information to an Unauthorized Actor. The /proc filesystem contains a wealth of sensitive data for any running process, including environment variables which may contain API keys, session tokens, database passwords, and other secrets passed via command-line arguments or inherited from parent processes. By copying this environ data into a directory owned by the attacker, abrt-server inadvertently grants local users read access to information that should remain confidential. This behavior violates the principle of least privilege, as the server performs actions with root authority but stores the resulting sensitive artifacts in locations accessible to lower-privileged entities.
The operational impact of this vulnerability is significant for any system running abrtd where untrusted local users have shell or socket access. An attacker can exploit this flaw by initiating a connection through abrt.socket and providing the PID of a target process, such as a web server daemon, SSH session, or another user's application. Upon receiving the request, the root-level abrt-server will fetch the environment variables and related metadata for that specific PID and place them in a directory accessible to the attacker. This allows for the passive harvesting of credentials and sensitive configuration details without requiring any additional exploitation techniques like buffer overflows or code injection. The attack is particularly dangerous because it leverages legitimate system administration tools, making detection difficult through standard security monitoring unless specifically tuned to watch abrt socket interactions and file creation events in temporary directories.
Mitigation strategies must focus on restricting the scope of data accessible via the abrt interface and enforcing stricter ownership controls on generated artifacts. The most effective immediate mitigation is to disable or uninstall the abrt service if it is not actively required for system maintenance, thereby removing the attack surface entirely. If abrt remains necessary, administrators should ensure that any dump directories created by the server are strictly owned by root with permissions set to 700, preventing unprivileged users from reading their contents. Furthermore, patching the underlying software to validate PIDs against a whitelist of allowed processes or ensuring that sensitive data like environment variables is excluded from automated dumps can resolve the issue at its source. Security teams should also monitor for unusual file creation patterns in /var/spool/abrt and audit abrt socket connections to detect potential exploitation attempts early. This vulnerability underscores the importance of rigorous input validation and secure default permissions when designing services that operate with elevated privileges, aligning with ATT&CK technique T1005: Data from Local System for information gathering via local access.