Bug 182286 - CVE-2003-1294 xscreensaver temporary file flaws
CVE-2003-1294 xscreensaver temporary file flaws
Status: CLOSED WONTFIX
Product: Red Hat Enterprise Linux 3
Classification: Red Hat
Component: xscreensaver (Show other bugs)
3.0
All Linux
medium Severity low
: ---
: ---
Assigned To: Ray Strode [halfline]
reported=20031103,impact=low,public=2...
: Security
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2006-02-21 12:03 EST by Mark J. Cox (Product Security)
Modified: 2012-06-20 09:24 EDT (History)
0 users

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2012-06-20 09:24:42 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)
Proposed patch as used by SUSE (6.39 KB, patch)
2006-02-21 12:03 EST, Mark J. Cox (Product Security)
no flags Details | Diff

  None (edit)
Description Mark J. Cox (Product Security) 2006-02-21 12:03:19 EST
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 (Product Security) 2006-02-21 12:03:19 EST
Created attachment 124968 [details]
Proposed patch as used by SUSE
Comment 4 Jiri Pallich 2012-06-20 09:24:42 EDT
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.