# CVE-2005-1039: Race condition in n/a

> Local attackers can exploit a race condition in coreutils commands to modify permissions of arbitrary files, potentially leading to privilege escalation.

- **Severity:** Low 3.7 (`AV:L/AC:H/Au:N/C:P/I:P/A:P`)
- **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:** 10 Apr 2005
- **Updated:** 16 Sep 2024
- **Also known as:** DEBIAN-CVE-2005-1039, GHSA-94gh-mvm8-54cf

## What is CVE-2005-1039?

CVE-2005-1039 is a low-severity vulnerability in n/a, published on 10 Apr 2005. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

Race condition in Core Utilities (coreutils) 5.2.1, when (1) mkdir, (2) mknod, or (3) mkfifo is running with the -m switch, allows local users to modify permissions of other files.

## Which versions are affected by CVE-2005-1039?

It affects 1 product.


Products: Gnu Coreutils.

## How do I fix CVE-2005-1039?

Upgrade to a fixed version.

## Is CVE-2005-1039 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2015-4042](https://insights.sbomify.com/CVE-2015-4042/): Integer overflow in n/a (critical 9.8)
- [CVE-2015-4041](https://insights.sbomify.com/CVE-2015-4041/): Memory corruption in n/a (high 7.8)
- [CVE-2017-18018](https://insights.sbomify.com/CVE-2017-18018/): Race condition in n/a (high 7.1)
- [CVE-2024-0684](https://insights.sbomify.com/CVE-2024-0684/): Coreutils: heap overflow in split --line-bytes with very long lines (medium 5.5)
- [CVE-2015-1865](https://insights.sbomify.com/CVE-2015-1865/): Race condition in n/a (medium 5.1)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2005-1039 and fix it if it is affected.

What it is: CVE-2005-1039 is a low-severity vulnerability in n/a, published on 10 Apr 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-2005-1039 in the wild and no public exploit code.

Affected product: n/a. 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-2005-1039/ (Markdown: https://insights.sbomify.com/CVE-2005-1039/index.md)
```

## Sources

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

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