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

> Remote attackers can write arbitrary files via directory traversal in ISO filenames, requiring user interaction to open the malicious image.

- **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:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 29 Apr 2006
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-wgwh-x7jp-xj7g

## What is CVE-2006-2099?

CVE-2006-2099 is a medium-severity path traversal vulnerability in n/a, published on 29 Apr 2006. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

### Official description

Directory traversal vulnerability in UltraISO 8.0.0.1392 allows remote attackers to write arbitrary files via a .. (dot dot) in a filename in an ISO image.

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

It affects 1 product.


Products: Ezb Systems Ultraiso.

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

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

## Is CVE-2006-2099 being exploited?

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

Public exploit code:

- ezb systems ultraiso 8.0.1392 - Directory Traversal (exploitdb)

## Other vulnerabilities in n/a

- [CVE-2007-2888](https://insights.sbomify.com/CVE-2007-2888/): Memory corruption in n/a (high 7.6)

## Fix prompt for AI coding agents

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

What it is: CVE-2006-2099 is a medium-severity path traversal vulnerability in n/a, published on 29 Apr 2006. An attacker can exploit it over the internet without logging in, 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-2006-2099 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-2006-2099/ (Markdown: https://insights.sbomify.com/CVE-2006-2099/index.md)
```

## Sources

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

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