Bug 236585 - (CVE-2007-2030) CVE-2007-2030 /tmp race in lha
CVE-2007-2030 /tmp race in lha
Status: CLOSED WONTFIX
Product: Security Response
Classification: Other
Component: vulnerability (Show other bugs)
unspecified
All Linux
low Severity low
: ---
: ---
Assigned To: Red Hat Product Security
https://bugzilla.novell.com/show_bug....
public=20060113,reported=20070416,sou...
: Security
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2007-04-16 12:20 EDT by Red Hat Product Security
Modified: 2011-08-02 14:19 EDT (History)
1 user (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2011-08-02 14:19:53 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)
Patch for lha /tmp race & others, applies to FC5 (3.44 KB, patch)
2007-04-16 12:20 EDT, Lubomir Kundrak
no flags Details | Diff

  None (edit)
Description Lubomir Kundrak 2007-04-16 12:20:13 EDT
Description of problem:

lha doesn't open temporary files exclusively, which makes it possible for an
attacker to conduct a time-dependent attack by creating the file in advance.

Version-Release number of selected component (if applicable):

        Affects: RHEL2.1
        Affects: RHEL3
        Affects: RHEL4
        Affects: FC5

How reproducible:

Time-dependent race.

Additional info:

The patch also incorporates some trailing-NUL things from SUSE's
security review patch. I do not know why weren't they unlike some other
fixes from that patch integrated in our packages. It might be possible
that they are not needed. The patch is basically a polished diff between
SUSE and FC-5 lha.
Comment 1 Lubomir Kundrak 2007-04-16 12:20:13 EDT
Created attachment 152702 [details]
Patch for lha /tmp race & others, applies to FC5
Comment 3 Red Hat Bugzilla 2009-10-23 15:03:38 EDT
Reporter changed to security-response-team@redhat.com by request of Jay Turner.
Comment 4 Josh Bressers 2011-08-02 14:17:41 EDT
Statement:

Red Hat no longer plans to fix this issue in Red Hat Enterprise Linux 4.

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