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

> Local attackers can exploit a race condition in Unzip to modify permissions of arbitrary files via hard link attacks during decompression.

- **Severity:** Low 1.2 (`AV:L/AC:H/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:** 5 Aug 2005
- **Updated:** 7 Aug 2024
- **Also known as:** DEBIAN-CVE-2005-2475, DSA-903-1, GHSA-3m3m-6r6c-8m58

## What is CVE-2005-2475?

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

### Official description

Race condition in Unzip 5.52 allows local users to modify permissions of arbitrary files via a hard link attack on a file while it is being decompressed, whose permissions are changed by Unzip after the decompression is complete.

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

It affects 1 product.


Products: Info-Zip Unzip.

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

Apply the vendor's patch.

## Is CVE-2005-2475 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2018-1000033](https://insights.sbomify.com/CVE-2018-1000033/): Information disclosure in n/a (critical 9.1)
- [CVE-2018-1000034](https://insights.sbomify.com/CVE-2018-1000034/): Information disclosure in n/a (critical 9.1)
- [CVE-2018-1000031](https://insights.sbomify.com/CVE-2018-1000031/): Memory corruption in n/a (high 7.8)
- [CVE-2018-1000032](https://insights.sbomify.com/CVE-2018-1000032/): Memory corruption in n/a (high 7.8)
- [CVE-2005-0602](https://insights.sbomify.com/CVE-2005-0602/): Privilege escalation in n/a (medium 6.2)

## Fix prompt for AI coding agents

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

What it is: CVE-2005-2475 is a low-severity vulnerability in n/a, published on 5 Aug 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-2475 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-2475/ (Markdown: https://insights.sbomify.com/CVE-2005-2475/index.md)
```

## Sources

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

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