Bug 2488568 (CVE-2026-54230) - CVE-2026-54230 abrt: event handler scripts follow symlinks when writing output files, allowing arbitrary file overwrites
Summary: CVE-2026-54230 abrt: event handler scripts follow symlinks when writing outpu...
Keywords:
Status: NEW
Alias: CVE-2026-54230
Product: Security Response
Classification: Other
Component: vulnerability
Version: unspecified
Hardware: All
OS: Linux
high
high
Target Milestone: ---
Assignee: Product Security DevOps Team
QA Contact:
URL:
Whiteboard:
Depends On: 2488619
Blocks:
TreeView+ depends on / blocked
 
Reported: 2026-06-12 21:02 UTC by OSIDB Bzimport
Modified: 2026-06-12 22:30 UTC (History)
2 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed:
Embargoed:


Attachments (Terms of Use)

Description OSIDB Bzimport 2026-06-12 21:02:55 UTC
A symlink following vulnerability was found in the ABRT post-create event handler scripts in /etc/libreport/events.d/abrt_event.conf. Event scripts write output files using shell redirections (e.g., "printf ... > $DUMP_DIR/var_log_messages") which use open() with O_WRONLY|O_CREAT|O_TRUNC without the O_NOFOLLOW flag. If the target file is replaced with a symlink, the shell process (running as root in the abrt_handle_event_t SELinux domain, which is effectively unconfined) follows the symlink and writes content to the symlink target. In contrast, dd_save_text (used by SetElement) correctly uses O_NOFOLLOW. An attacker who has gained filesystem control of the dump directory can replace output files with symlinks pointing to sensitive system files such as /var/spool/cron/root.


Note You need to log in before you can comment on or make changes to this bug.