* SECURITY UPDATE: When /proc/sys/fs/suid_dumpable is enabled, crashing a
program that is suid root or not readable for the user would create
root-owned core files in the current directory of that program. Creating
specially crafted core files in /etc/logrotate.d or similar could then
lead to arbitrary code execution with root privileges. Now core files do
not get written for these kinds of programs, in accordance with the
intention of core(5).
Thanks to Sander Bos for discovering this issue!
(CVE-2015-1324, LP: #1452239)
* Add test case to ensure that users cannot inject arbitrary core dump file
contents (CVE-2015-1325). This version is not affected, but having the
test will ensure that backported changes don't introduce this
vulnerability. (LP: #1453900)
* test_signal_crashes(): Drop hardcoded /tmp/ path in do_crash(),
test_nonwritable_cwd() uses a different dir.
-- Martin Pitt <email address hidden> Wed, 13 May 2015 13:58:17 +0200
This bug was fixed in the package apport - 2.0.1-0ubuntu17.9
---------------
apport (2.0.1-0ubuntu17.9) precise-security; urgency=medium
* SECURITY UPDATE: When /proc/sys/ fs/suid_ dumpable is enabled, crashing a crashes( ): Drop hardcoded /tmp/ path in do_crash(), nonwritable_ cwd() uses a different dir.
program that is suid root or not readable for the user would create
root-owned core files in the current directory of that program. Creating
specially crafted core files in /etc/logrotate.d or similar could then
lead to arbitrary code execution with root privileges. Now core files do
not get written for these kinds of programs, in accordance with the
intention of core(5).
Thanks to Sander Bos for discovering this issue!
(CVE-2015-1324, LP: #1452239)
* Add test case to ensure that users cannot inject arbitrary core dump file
contents (CVE-2015-1325). This version is not affected, but having the
test will ensure that backported changes don't introduce this
vulnerability. (LP: #1453900)
* test_signal_
test_
-- Martin Pitt <email address hidden> Wed, 13 May 2015 13:58:17 +0200