# CVE-2005-0602: Privilege escalation in n/a

> Local attackers can gain privileges by tricking users into extracting setuid or setgid files using Unzip without proper warnings.

- **Severity:** Medium 6.2 (`AV:L/AC:H/Au:N/C:C/I:C/A:C`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** A user has to click or open something
- **Fix available:** Yes
- **Published:** 1 Mar 2005
- **Updated:** 7 Aug 2024
- **Also known as:** DEBIAN-CVE-2005-0602, GHSA-h78h-jj63-v974

## What is CVE-2005-0602?

CVE-2005-0602 is a medium-severity vulnerability in n/a, published on 1 Mar 2005. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.

### Official description

Unzip 5.51 and earlier does not properly warn the user when extracting setuid or setgid files, which may allow local users to gain privileges.

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

It affects 1 product.


Products: Info-Zip Unzip.

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

Upgrade to a fixed version.

## Is CVE-2005-0602 being exploited?

There is no known exploitation of CVE-2005-0602 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-4667](https://insights.sbomify.com/CVE-2005-4667/): Memory corruption in n/a (low 3.7)

## Fix prompt for AI coding agents

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

What it is: CVE-2005-0602 is a medium-severity vulnerability in n/a, published on 1 Mar 2005. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2005-0602 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-0602/ (Markdown: https://insights.sbomify.com/CVE-2005-0602/index.md)
```

## Sources

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

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