Bug 433719 (CVE-2008-0806) - CVE-2008-0806 Wyrd uses insecure temporary file
Summary: CVE-2008-0806 Wyrd uses insecure temporary file
Keywords:
Status: CLOSED ERRATA
Alias: CVE-2008-0806
Product: Security Response
Classification: Other
Component: vulnerability
Version: unspecified
Hardware: All
OS: Linux
low
low
Target Milestone: ---
Assignee: Red Hat Product Security
QA Contact:
URL: http://nvd.nist.gov/nvd.cfm?cvename=C...
Whiteboard:
Depends On: 433720 433721 433722
Blocks:
TreeView+ depends on / blocked
 
Reported: 2008-02-21 00:46 UTC by Lubomir Kundrak
Modified: 2008-05-06 16:16 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2008-05-06 16:16:58 UTC


Attachments (Terms of Use)

Description Lubomir Kundrak 2008-02-21 00:46:41 UTC
Common Vulnerabilities and Exposures assigned an identifier CVE-2008-0806 to the following vulnerability:

wyrd 1.4.3b allows local users to overwrite arbitrary files via a symlink attack on the wyrd-tmp.[USERID] temporary file.

References:

http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=466382
http://www.securityfocus.com/bid/27848
http://secunia.com/advisories/29009

Comment 2 Fedora Update System 2008-02-21 09:53:35 UTC
wyrd-1.4.3b-1.fc8 has been submitted as an update for Fedora 8

Comment 3 Fedora Update System 2008-02-21 09:53:36 UTC
wyrd-1.4.3b-1.fc7 has been submitted as an update for Fedora 7

Comment 4 Fedora Update System 2008-02-26 00:25:36 UTC
wyrd-1.4.3b-1.fc7 has been pushed to the Fedora 7 stable repository.  If problems still persist, please make note of it in this bug report.

Comment 5 Fedora Update System 2008-02-26 00:27:04 UTC
wyrd-1.4.3b-1.fc8 has been pushed to the Fedora 8 stable repository.  If problems still persist, please make note of it in this bug report.

Comment 6 Red Hat Product Security 2008-05-06 16:16:58 UTC
This issue was addressed in:

Fedora:
  https://admin.fedoraproject.org/updates/F7/FEDORA-2008-1963
  https://admin.fedoraproject.org/updates/F8/FEDORA-2008-1986




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