The kernel-invoked coredump processor in Automatic Bug Reporting Tool (ABRT) does not properly check the ownership of files before writing core dumps to them, which allows local users to obtain sensitive information by leveraging write permissions to the working directory of a crashed application.

The kernel-invoked coredump processor in Automatic Bug Reporting Tool (ABRT) does not properly check the ownership of files before writing core dumps to them, which allows local users to obtain sensitive information by leveraging write permissions to the working directory of a crashed application.

abrt: default event scripts follow symbolic links abrt: default abrt event scripts lead to information disclosure abrt: abrt-hook-ccpp writes core dumps to existing files owned by others abrt: does not validate contents of uploaded problem reports abrt: abrt-dbus does not guard against crafted problem directory path arguments abrt: directory traversals in several D-Bus methods implemented by abrt-dbus abrt: missing process environment sanitizaton in abrt-action-install-debuginfo-to-abrt-cache abrt: Various race-conditions and symlink issues found in abrt

abrt: default event scripts follow symbolic links abrt: default abrt event scripts lead to information disclosure abrt: abrt-hook-ccpp writes core dumps to existing files owned by others abrt: does not validate contents of uploaded problem reports abrt: missing process environment sanitizaton in abrt-action-install-debuginfo-to-abrt-cache abrt: Various race-conditions and symlink issues found in abrt