# CVE-2005-0161: Path traversal in n/a

> Attackers can overwrite arbitrary files via directory traversal in ACE archives, requiring user interaction to open the malicious file.

- **Severity:** Low 2.1 (`AV:L/AC:L/Au:N/C:N/I:P/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** A user has to click or open something
- **Fix available:** Yes
- **Published:** 24 Feb 2005
- **Updated:** 7 Aug 2024
- **Also known as:** DEBIAN-CVE-2005-0161, GHSA-m9jq-p64q-5v4g

## What is CVE-2005-0161?

CVE-2005-0161 is a low-severity path traversal vulnerability in n/a, published on 24 Feb 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

Multiple directory traversal vulnerabilities in unace 1.2b allow attackers to overwrite arbitrary files via an ACE archive containing (1) ../ sequences or (2) absolute pathnames.

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

It affects 1 product.


Products: E-Merge Unace.

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

Upgrade to a fixed version.

## Is CVE-2005-0161 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2005-0161 exists.

Public exploit code:

- Winace UnAce 1.x - ACE Archive Directory Traversal (exploitdb)

## Other vulnerabilities in n/a

- [CVE-2005-0160](https://insights.sbomify.com/CVE-2005-0160/): Memory corruption in n/a (medium 5.1)

## Fix prompt for AI coding agents

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

What it is: CVE-2005-0161 is a low-severity path traversal vulnerability in n/a, published on 24 Feb 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: It is not confirmed as exploited in the wild, but public exploit code for CVE-2005-0161 exists.

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-0161/ (Markdown: https://insights.sbomify.com/CVE-2005-0161/index.md)
```

## Sources

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

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