# CVE-1999-1572: Misconfiguration in n/a

> Local attackers can read or overwrite files created by cpio due to insecure default permissions, affecting system integrity and confidentiality.

- **Severity:** Low 2.1 (`AV:L/AC:L/Au:N/C:P/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 29 Jan 2005
- **Updated:** 1 Aug 2024
- **Also known as:** DEBIAN-CVE-1999-1572, DSA-664-1, GHSA-j8q5-qf4r-w33w, RHSA-2005:073, RHSA-2005:080

## What is CVE-1999-1572?

CVE-1999-1572 is a low-severity vulnerability in Debian Debian Linux, published on 29 Jan 2005. It can only be exploited from the same machine or local network, with no action from the victim.

### Official 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.

## Which versions are affected by CVE-1999-1572?

It affects 6 products.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `cpio` | Red Hat:enterprise_linux:3::as | All versions | 0:2.5-3e.3 |
| `cpio-debuginfo` | Red Hat:enterprise_linux:3::as | All versions | 0:2.5-3e.3 |
| `cpio` | Red Hat:enterprise_linux:3::desktop | All versions | 0:2.5-3e.3 |
| `cpio-debuginfo` | Red Hat:enterprise_linux:3::desktop | All versions | 0:2.5-3e.3 |
| `cpio` | Red Hat:enterprise_linux:3::es | All versions | 0:2.5-3e.3 |
| `cpio-debuginfo` | Red Hat:enterprise_linux:3::es | All versions | 0:2.5-3e.3 |
| `cpio` | Red Hat:enterprise_linux:3::ws | All versions | 0:2.5-3e.3 |
| `cpio-debuginfo` | Red Hat:enterprise_linux:3::ws | All versions | 0:2.5-3e.3 |
| `cpio` | Red Hat:enterprise_linux:4::as | All versions | 0:2.5-7.EL4.1 |
| `cpio-debuginfo` | Red Hat:enterprise_linux:4::as | All versions | 0:2.5-7.EL4.1 |
| `cpio` | Red Hat:enterprise_linux:4::desktop | All versions | 0:2.5-7.EL4.1 |
| `cpio-debuginfo` | Red Hat:enterprise_linux:4::desktop | All versions | 0:2.5-7.EL4.1 |
| `cpio` | Red Hat:enterprise_linux:4::es | All versions | 0:2.5-7.EL4.1 |
| `cpio-debuginfo` | Red Hat:enterprise_linux:4::es | All versions | 0:2.5-7.EL4.1 |
| `cpio` | Red Hat:enterprise_linux:4::ws | All versions | 0:2.5-7.EL4.1 |
| `cpio-debuginfo` | Red Hat:enterprise_linux:4::ws | All versions | 0:2.5-7.EL4.1 |

Products: Debian Debian Linux, Freebsd Freebsd, Mandrakesoft Mandrake Linux, Redhat Enterprise Linux, Redhat Enterprise Linux Desktop, Ubuntu Ubuntu Linux.

## How do I fix CVE-1999-1572?

Apply the vendor's patch.

## Is CVE-1999-1572 being exploited?

There is no known exploitation of CVE-1999-1572 in the wild and no public exploit code.

## Other vulnerabilities in Debian Debian Linux

- [CVE-2015-3306](https://insights.sbomify.com/CVE-2015-3306/): ProFTPD Improper Access Control (critical 10.0, exploited in the wild)
- [CVE-2025-49113](https://insights.sbomify.com/CVE-2025-49113/): RoundCube Webmail Deserialization of Untrusted Data (critical 9.9, exploited in the wild)
- [CVE-2026-24061](https://insights.sbomify.com/CVE-2026-24061/): GNU InetUtils Argument Injection (critical 9.8, exploited in the wild)
- [CVE-2025-39682](https://insights.sbomify.com/CVE-2025-39682/): Linux Kernel Improper Check for Unusual or Exceptional Conditions (critical 9.8, exploited in the wild)
- [CVE-2024-9680](https://insights.sbomify.com/CVE-2024-9680/): Mozilla Firefox Use-After-Free (critical 9.8, exploited in the wild)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-1999-1572 and fix it if it is affected.

What it is: CVE-1999-1572 is a low-severity vulnerability in Debian Debian Linux, published on 29 Jan 2005. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-1999-1572 in the wild and no public exploit code.

Affected product: Debian Debian Linux. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-1999-1572/ (Markdown: https://insights.sbomify.com/CVE-1999-1572/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-1999-1572
- NVD: https://nvd.nist.gov/vuln/detail/CVE-1999-1572
- OSV: https://osv.dev/vulnerability/CVE-1999-1572

---
From sbomify Insights: https://insights.sbomify.com/CVE-1999-1572/
Summaries are generated and may contain mistakes; the official description above is the record.