This site requires JavaScript to be enabled to function correctly, please enable it.
Bug 182286 - CVE-2003-1294 xscreensaver temporary file flaws
Summary: CVE-2003-1294 xscreensaver temporary file flaws
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Red Hat Enterprise Linux 3
Classification: Red Hat
Component: xscreensaver
Version: 3.0
Hardware: All
OS: Linux
medium
low
Target Milestone: ---
Assignee: Ray Strode [halfline]
QA Contact:
URL:
Whiteboard: reported=20031103,impact=low,public=2...
Depends On:
Blocks:
TreeView+ depends on / blocked
Reported: 2006年02月21日 17:03 UTC by Mark J. Cox
Modified: 2012年06月20日 13:24 UTC (History)
0 users

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2012年06月20日 13:24:42 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)
Proposed patch as used by SUSE (6.39 KB, patch)
2006年02月21日 17:03 UTC, Mark J. Cox 		no flags Details | Diff
View All

Description Mark J. Cox 2006年02月21日 17:03:19 UTC 
Stan Bubrouski contacted jwz the maintainer of xscreensaver
 and cc'd Red Hat security folks on 20031031 to report an
 insecure temporary file flaw introduced in xscreensaver
 version 4.14. This was due to a bit of debugging code that
 got left in by mistake, it was removed in 4.15, and therefore
 didn't affect any RHEL releases. This was CVE-2003-0885.
However SUSE then found some other suspect temporary file issues which also got
silently fixed in 4.15 release. I've applied for a CVE name for these.
Comment 1 Mark J. Cox 2006年02月21日 17:03:19 UTC 
Created attachment 124968 [details] 
Proposed patch as used by SUSE
Comment 4 Jiri Pallich 2012年06月20日 13:24:42 UTC 
Thank you for submitting this issue for consideration in Red Hat Enterprise Linux. The release for which you requested us to review is now End of Life. 
Please See https://access.redhat.com/support/policy/updates/errata/
If you would like Red Hat to re-consider your feature request for an active release, please re-open the request via appropriate support channels and provide additional supporting details about the importance of this issue.
Note You need to log in before you can comment on or make changes to this bug.