# CVE-2006-1715: Path traversal in n/a

> User-assisted attackers can create files in arbitrary directories via crafted archive files in TUGZip, requiring user interaction to open the malicious archive.

- **Severity:** Medium 5.0 (`AV:N/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:** No
- **Published:** 11 Apr 2006
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-pwrr-gj7q-m6c7

## What is CVE-2006-1715?

CVE-2006-1715 is a medium-severity path traversal vulnerability in n/a, published on 11 Apr 2006. 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 Christian Kindahl TUGZip 3.4.0.0, 3.3.0.0, and 3.1.0.2 allow user-assisted attackers to create files in arbitrary directories via a .. (dot dot) in an archive pack with a crafted (1) .gz, (2) .jar, (3) .rar, or (4) .zip file.

## Which versions are affected by CVE-2006-1715?

It affects 1 product.


Products: Tugzip Tugzip.

## How do I fix CVE-2006-1715?

No fix has been published for CVE-2006-1715 yet. Limit exposure of the affected software until one is available.

## Is CVE-2006-1715 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2005-4594](https://insights.sbomify.com/CVE-2005-4594/): Memory corruption in n/a (high 7.5)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2006-1715 and fix it if it is affected.

What it is: CVE-2006-1715 is a medium-severity path traversal vulnerability in n/a, published on 11 Apr 2006. 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-2006-1715 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-2006-1715/ (Markdown: https://insights.sbomify.com/CVE-2006-1715/index.md)
```

## Sources

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

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