CVE-1999-1572
published 1996-07-16CVE-1999-1572: cpio on FreeBSD 2.1.0, Debian GNU/Linux 3.0, and possibly other operating systems, uses a 0 umask when creating files using the -O (archive) or -F options…
PriorityP46low2.1CVSS 2.0
AVLACLAuNCPINAN
EPSS
0.56%
42.6th percentile
cpio on FreeBSD 2.1.0, Debian GNU/Linux 3.0, and possibly other operating systems, uses a 0 umask when creating files using the -O (archive) or -F options, which creates the files with mode 0666 and allows local users to read or overwrite those files.
Affected
15 ranges
| Vendor | Product | Version range | Fixed in |
|---|---|---|---|
| debian | cpio | < cpio 2.5-1.2 (bookworm) | cpio 2.5-1.2 (bookworm) |
| debian | debian_linux | — | — |
| freebsd | freebsd | — | — |
| gnu | cpio | >= 0 < 2.5-1.2 | 2.5-1.2 |
| gnu | cpio | >= 0 < 2.5-1.2 | 2.5-1.2 |
| gnu | cpio | >= 0 < 2.5-1.2 | 2.5-1.2 |
| gnu | cpio | >= 0 < 2.5-1.2 | 2.5-1.2 |
| mandrakesoft | mandrake_linux | — | — |
| mandrakesoft | mandrake_linux | — | — |
| mandrakesoft | mandrake_linux | — | — |
| mandrakesoft | mandrake_linux | — | — |
| mandrakesoft | mandrake_linux | — | — |
| redhat | enterprise_linux | — | — |
| redhat | enterprise_linux_desktop | — | — |
| ubuntu | ubuntu_linux | — | — |
CVSS provenance
nvdv2.02.1LOWAV:L/AC:L/Au:N/C:P/I:N/A:N
osv2.1LOW
vendor_debian2.1LOW
vendor_redhat2.1LOW
Stop checking back — get the weekly exploitation signal.
Every Monday: what got weaponized or added to CISA KEV in the last seven days — each CVE cross-linked to its PoC, Nuclei template, and detection rule. Free, one email a week, unsubscribe in one click.
Ubuntu
cpio vulnerability
vendor_ubuntu·2005-02-04
CVE-1999-1572 cpio vulnerability
Title: cpio vulnerability
Summary: cpio vulnerability
Recently it was discovered that cpio created world-writeable files
when used in -o/--create mode with giving an output file (with -O).
This allowed any user to modify the created cpio archives. Now cpio
respects the current umask setting of the user.
Note: This vulnerability has already been fixed in a very old version
of cpio, but the fix was never ported to the current version.
Therefore the CAN number was assigned to the year 1999.
Instructions: In general, a standard system update will make all the necessary changes.
Debian
CVE-1999-1572: cpio - cpio on FreeBSD 2.1.0, Debian GNU/Linux 3.0, and possibly other operating system...
vendor_debian·1999·CVSS 2.1
CVE-1999-1572 [LOW] CVE-1999-1572: cpio - cpio on FreeBSD 2.1.0, Debian GNU/Linux 3.0, and possibly other operating system...
cpio on FreeBSD 2.1.0, Debian GNU/Linux 3.0, and possibly other operating systems, uses a 0 umask when creating files using the -O (archive) or -F options, which creates the files with mode 0666 and allows local users to read or overwrite those files.
Scope: local
bookworm: resolved (fixed in 2.5-1.2)
bullseye: resolved (fixed in 2.5-1.2)
forky: resolved (fixed in 2.5-1.2)
sid: resolved (fixed in 2.5-1.2)
trixie: resolved (fixed in 2.5-1.2)
Red Hat
security flaw
vendor_redhat·1996-07-16·CVSS 2.1
CVE-1999-1572 [LOW] security flaw
security flaw
cpio on FreeBSD 2.1.0, Debian GNU/Linux 3.0, and possibly other operating systems, uses a 0 umask when creating files using the -O (archive) or -F options, which creates the files with mode 0666 and allows local users to read or overwrite those files.
Statement: Red Hat Enterprise Linux 5 is not vulnerable to this issue as it contains a backported patch.
GHSA
GHSA-j8q5-qf4r-w33w: cpio on FreeBSD 2
ghsa_unreviewed·2022-04-30
CVE-1999-1572 [LOW] GHSA-j8q5-qf4r-w33w: cpio on FreeBSD 2
cpio on FreeBSD 2.1.0, Debian GNU/Linux 3.0, and possibly other operating systems, uses a 0 umask when creating files using the -O (archive) or -F options, which creates the files with mode 0666 and allows local users to read or overwrite those files.
OSV
CVE-1999-1572: cpio on FreeBSD 2
osv·1996-07-16·CVSS 2.1
CVE-1999-1572 [LOW] CVE-1999-1572: cpio on FreeBSD 2
cpio on FreeBSD 2.1.0, Debian GNU/Linux 3.0, and possibly other operating systems, uses a 0 umask when creating files using the -O (archive) or -F options, which creates the files with mode 0666 and allows local users to read or overwrite those files.
No detection rules found.
No public exploits indexed.
Bugzilla
CVE-1999-1572 security flaw
bugzilla·2018-08-16·CVSS 2.1
CVE-1999-1572 [LOW] CVE-1999-1572 security flaw
CVE-1999-1572 security flaw
Flaw bug created to hold information about an old flaw we knew something about. For more details see the MITRE CVE description.
Discussion:
MITRE description:
cpio on FreeBSD 2.1.0, Debian GNU/Linux 3.0, and possibly other operating systems, uses a 0 umask when creating files using the -O (archive) or -F options, which creates the files with mode 0666 and allows local users to read or overwrite those files.
---
Statement:
Red Hat Enterprise Linux 5 is not vulnerable to this issue as it contains a backported patch.
Acknowledgments:
Red Hat would like to thank Mike O'Connor for bringing this issue to our attention.
Bugzilla
CVE-1999-1572 cpio insecure file creation
bugzilla·2005-11-01·CVSS 2.1
CVE-1999-1572 [LOW] CVE-1999-1572 cpio insecure file creation
CVE-1999-1572 cpio insecure file creation
+++ 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:
http://www.freebsd.org/cgi/query-pr.cgi?pr=bin
http://marc.info/?l=bugtraq&m=110763404701519&w=2http://secunia.com/advisories/14357http://secunia.com/advisories/17063http://secunia.com/advisories/17532http://support.avaya.com/elmodocs2/security/ASA-2005-212.pdfhttp://www.debian.org/security/2005/dsa-664http://www.freebsd.org/cgi/query-pr.cgi?pr=bin/1391http://www.mandriva.com/security/advisories?name=MDKSA-2005:032http://www.redhat.com/support/errata/RHSA-2005-073.htmlhttp://www.redhat.com/support/errata/RHSA-2005-080.htmlhttp://www.redhat.com/support/errata/RHSA-2005-806.htmlhttp://www.trustix.org/errata/2005/0003/https://exchange.xforce.ibmcloud.com/vulnerabilities/19167https://oval.cisecurity.org/repository/search/definition/oval%3Aorg.mitre.oval%3Adef%3A10888http://marc.info/?l=bugtraq&m=110763404701519&w=2http://secunia.com/advisories/14357http://secunia.com/advisories/17063http://secunia.com/advisories/17532http://support.avaya.com/elmodocs2/security/ASA-2005-212.pdfhttp://www.debian.org/security/2005/dsa-664http://www.freebsd.org/cgi/query-pr.cgi?pr=bin/1391http://www.mandriva.com/security/advisories?name=MDKSA-2005:032http://www.redhat.com/support/errata/RHSA-2005-073.htmlhttp://www.redhat.com/support/errata/RHSA-2005-080.htmlhttp://www.redhat.com/support/errata/RHSA-2005-806.htmlhttp://www.trustix.org/errata/2005/0003/https://exchange.xforce.ibmcloud.com/vulnerabilities/19167https://oval.cisecurity.org/repository/search/definition/oval%3Aorg.mitre.oval%3Adef%3A10888
1996-07-16
Published