Bug 155751 - CAN-2005-1111 Race condition in cpio
CAN-2005-1111 Race condition in cpio
Product: Fedora Legacy
Classification: Retired
Component: cpio (Show other bugs)
All Linux
medium Severity medium
: ---
: ---
Assigned To: Fedora Legacy Bugs
Brock Organ
: Reopened, Security
Depends On:
  Show dependency treegraph
Reported: 2005-04-22 14:51 EDT by Josh Bressers
Modified: 2007-04-18 13:24 EDT (History)
2 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2007-04-10 15:16:39 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)
patch fix cpio-2.6 race condition (4.01 KB, patch)
2005-04-25 09:06 EDT, Peter Vrabec
no flags Details | Diff

  None (edit)
Description Josh Bressers 2005-04-22 14:51:29 EDT
+++ This bug was initially created as a clone of Bug #155749 +++

Race condition in cpio 2.6 and earlier allows local users to modify permissions
of arbitrary files via a hard link attack on a file while it is being
decompressed, whose permissions are changed by cpio after the decompression is

Comment 1 Peter Vrabec 2005-04-25 09:06:14 EDT
Created attachment 113628 [details]
patch fix cpio-2.6 race condition

I replaced some chown, chmod with fchmod and fchown. And close file descriptor
Comment 2 Michal Jaegermann 2005-07-12 12:43:49 EDT
This bug is CLOSED RAWHIDE, and hopefuly fixed in cpio-2.6-7 from FC4 although
there is no explicit note to the effect in a changelog there, but I do not see
a security update for FC3 which would cover that bug and also CAN-2005-1229
(bug #156314) and this leaves those installations vulnerable.
Comment 3 Matthew Miller 2006-10-19 15:31:23 EDT
Reopening as per comment #2.
Comment 4 Matthew Miller 2006-10-19 15:32:53 EDT
also, confirming that this is fixed in FC4 and on.
Comment 5 Matthew Miller 2007-04-10 15:16:39 EDT
Fedora Core 3 is now completely unmaintained. These bugs can't be fixed in that
version. If the issue still persists in current Fedora Core, please reopen.
Thank you, and sorry about this.

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