Bug 156399 - CAN-1999-1572 cpio insecure file creation
CAN-1999-1572 cpio insecure file creation
Product: Red Hat Enterprise Linux 4
Classification: Red Hat
Component: cpio (Show other bugs)
All Linux
medium Severity low
: ---
: ---
Assigned To: Peter Vrabec
Brock Organ
: Security
Depends On:
  Show dependency treegraph
Reported: 2005-04-29 15:07 EDT by Josh Bressers
Modified: 2007-11-30 17:07 EST (History)
1 user (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2005-05-05 06:02:36 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description Josh Bressers 2005-04-29 15:07:11 EDT
+++ This bug was initially created as a clone of Bug #145720 +++

This is a very old issue.  This message was posted to vendor-sec.

GNU cpio -oO appears to generate files with 0666 regardless of
the user's umask.  This is true for both cpio 2.5 (RH, SuSE) and
and the (surprisingly 3x) larger cpio 2.6, but I haven't had the
chance to dig into the code yet or sync with the developers yet.
(If anyone else can gets to it before me, by all means...)  cpio
has a  need to toggle between a "0" umask and the original umask
depending on what it is doing, and gets it wrong in this case.

It's a long-known public issue in general -- earliest I can find
a record of it goes back to 1996, when the BSD folks fixed it:


and fixes against older GNU cpio were posted to gnu.utils.bugs
by The Written Word folks:


but it never seems to have gotten into newer GNU cpio versions.
Comment 1 Peter Vrabec 2005-05-05 06:02:36 EDT
I think this is already fixed in
Comment 2 Josh Bressers 2005-05-05 08:46:58 EDT

You're right, thanks for the catch.

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