First published: Tue Jul 16 1996(Updated: )
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.
Credit: cve@mitre.org cve@mitre.org
Affected Software | Affected Version | How to fix |
---|---|---|
Debian | =3.0 | |
FreeBSD FreeBSD | =2.1.0 | |
Mandrake Linux | =9.2 | |
Mandrake Linux | =10.0 | |
Mandrake Linux | =10.1 | |
Mandrake Linux | =cs2.1 | |
Mandrake Linux | =cs3.0 | |
Red Hat Enterprise Linux | =4.0 | |
Red Hat Enterprise Linux | =4.0 | |
Red Hat Enterprise Linux | =4.0 | |
redhat enterprise Linux desktop | =4.0 | |
Ubuntu | =4.10 |
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
CVE-1999-1572 is classified as a moderate severity vulnerability due to its potential to allow local users to read or overwrite sensitive files.
To fix CVE-1999-1572, you should update the cpio package to a version that addresses the 0 umask issue.
CVE-1999-1572 affects FreeBSD 2.1.0, Debian GNU/Linux 3.0, and various versions of Mandrake and Red Hat Enterprise Linux.
The 0 umask in CVE-1999-1572 means that files created using cpio with the -O or -F options have a mode of 0666, allowing all users to read or write to those files.
CVE-1999-1572 primarily allows for local exploitation, as it requires a local user to have access to the affected systems.