Bug 492098 - XFree86-xfs, xorg-x11-xfs: Unsafe usage of temporary file
XFree86-xfs, xorg-x11-xfs: Unsafe usage of temporary file
Product: Security Response
Classification: Other
Component: vulnerability (Show other bugs)
All Linux
low Severity low
: ---
: ---
Assigned To: Red Hat Product Security
: Security
Depends On:
  Show dependency treegraph
Reported: 2009-03-25 08:00 EDT by Jan Lieskovsky
Modified: 2009-03-25 10:21 EDT (History)
2 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2009-03-25 09:34:26 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 Jan Lieskovsky 2009-03-25 08:00:33 EDT
A security flaw was found in the start() initscript of font server for XFree86/X.Org server. An attacker could use this flaw to cause
a symlink attack.

Comment 2 Jan Lieskovsky 2009-03-25 08:33:05 EDT
The Red Hat Security Response Team has rated this issue as having
low security impact, a future update may address this flaw.
More information regarding issue severity can be found here:
Comment 3 Kristian Høgsberg 2009-03-25 09:34:26 EDT
Doesn't apply to our xfs init script.  The debian script tries to save the contents of a non-directory /tmp/.font-unix file if it exists, which  is pretty stupid.  The only reason that file would exists would be an exploit attempt.  We just delete it if it's not a directory.
Comment 4 Kristian Høgsberg 2009-03-25 09:34:50 EDT
See also bug #242903.
Comment 5 Tomas Hoger 2009-03-25 10:21:06 EDT
(In reply to comment #4)
> See also bug #242903.  

Right, this indeed looks like Debian specific.  Our init script issues were addressed via CVE-2007-3103.  The only question that remains is why that issue is not fixed in Fedora?  We seem to have changed init script in Red Hat Enterprise Linux 4 and 5 to not do chmod/chown, but that change did not make it to Fedora...

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