Bug 162979 - CAN-2005-2104 sysreport insecure temporary directory usage
CAN-2005-2104 sysreport insecure temporary directory usage
Product: Fedora
Classification: Fedora
Component: sysreport (Show other bugs)
All Linux
medium Severity low
: ---
: ---
Assigned To: Ngo Than
Ben Levenson
: Security
Depends On:
  Show dependency treegraph
Reported: 2005-07-11 18:54 EDT by Josh Bressers
Modified: 2007-11-30 17:11 EST (History)
1 user (show)

See Also:
Fixed In Version: FC5
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2006-09-21 22:11:32 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description Josh Bressers 2005-07-11 18:54:20 EDT
+++ This bug was initially created as a clone of Bug #162978 +++

sysreport creates a temporary directory in an insecure manner.

umask 0077

ROOT should be something like
ROOT=`mktemp -d /tmp/sysreport.XXXXXXXX`

It is possible for a local attacker to cause a race condition and trick
sysreport into writing its output to a directory the attacker can read.

This issue was discovered by Bill Stearns
Comment 1 Josh Bressers 2005-07-11 18:54:53 EDT
This issue should also affect FC3
Comment 2 Ngo Than 2005-07-13 05:03:56 EDT
it's fixed in 1.4.1-5(FC4) and 1.3.13-2(FC3)
Comment 3 Mark J. Cox (Product Security) 2005-11-10 08:50:00 EST
ping, intend to push updates?  
(removing embargo)
Comment 4 Ngo Than 2005-11-10 08:54:57 EST
yes, it should be pushed this week. Thanks for your remind
Comment 5 Fedora Update System 2005-11-10 12:18:44 EST
From User-Agent: XML-RPC

sysreport-1.3.13-2 has been pushed for FC3, which should resolve this issue.  If these problems are still present in this version, then please make note of it in this bug report.
Comment 6 Bill Nottingham 2006-09-21 22:11:32 EDT
Closing bugs in MODIFIED state from prior Fedora releases. If this bug persists
in a current Fedora release (such as Fedora Core 5 or later), please reopen and
set the version appropriately.

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