Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.
For bugs related to Red Hat Enterprise Linux 4 product line. The current stable release is 4.9. For Red Hat Enterprise Linux 6 and above, please visit Red Hat JIRA https://issues.redhat.com/secure/CreateIssue!default.jspa?pid=12332745 to report new issues.

Bug 146774

Summary: CAN-2004-0452 File::Path::rmtree() issue
Product: Red Hat Enterprise Linux 4 Reporter: Mark J. Cox <mjc>
Component: perlAssignee: Chip Turner <cturner>
Status: CLOSED ERRATA QA Contact: David Lawrence <dkl>
Severity: medium Docs Contact:
Priority: medium    
Version: 4.0CC: security-response-team, shillman
Target Milestone: ---   
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2005-02-15 09:18:19 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Mark J. Cox 2005-02-01 15:55:38 UTC
*** This bug has been split off bug 140542 ***

------- Original comment by Mark J. Cox (Security Response Team) on 2004.11.23
10:54 -------

Debian reported to vendor-sec earlier in the year a possible issue in
File::Path::rmtree.  "It seems that in the process of recursing the
tree, File::Path::rmtree uses chmod to set various things to be world
writable.  This would seem to open the usual race conditions in 
situations where they would not otherwise exist, due to the directories
involved having sane permissions."

Possibly not public; checking with Debian.

Comment 2 Mark J. Cox 2005-02-15 09:18:19 UTC
An advisory has been issued which should help the problem
described in this bug report. This report is therefore being
closed with a resolution of ERRATA. For more information
on the solution and/or where to find the updated files,
please follow the link below. You may reopen this bug report
if the solution does not work for you.

http://rhn.redhat.com/errata/RHSA-2005-103.html