* SECURITY FIX: kernel_crashdump: Enforce that the log/dmesg files are not a
symlink.
This prevents normal users from pre-creating a symlink to the predictable
.crash file, and thus triggering a "fill up disk" DoS attack when the
.crash report tries to include itself. Thanks to halfdog for discovering
this! (CVE-2015-1338, part of LP #1492570)
* SECURITY FIX: Fix all writers of report files to open the report file
exclusively.
Fix package_hook, kernel_crashdump, and similar hooks to fail if the
report already exists. This prevents privilege escalation through symlink
attacks. Note that this will also prevent overwriting previous reports
with the same same. Thanks to halfdog for discovering this!
(CVE-2015-1338, LP: #1492570)
* debian/tests/upstream-system: Change directory to /tmp, so that tests
actually run against the installed package.
This bug was fixed in the package apport - 2.0.1-0ubuntu17.10
--------------- 0ubuntu17. 10) precise-security; urgency=medium
apport (2.0.1-
* SECURITY FIX: kernel_crashdump: Enforce that the log/dmesg files are not a tests/upstream- system: Change directory to /tmp, so that tests
symlink.
This prevents normal users from pre-creating a symlink to the predictable
.crash file, and thus triggering a "fill up disk" DoS attack when the
.crash report tries to include itself. Thanks to halfdog for discovering
this! (CVE-2015-1338, part of LP #1492570)
* SECURITY FIX: Fix all writers of report files to open the report file
exclusively.
Fix package_hook, kernel_crashdump, and similar hooks to fail if the
report already exists. This prevents privilege escalation through symlink
attacks. Note that this will also prevent overwriting previous reports
with the same same. Thanks to halfdog for discovering this!
(CVE-2015-1338, LP: #1492570)
* debian/
actually run against the installed package.
-- Martin Pitt <email address hidden> Mon, 21 Sep 2015 11:58:45 +0200