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

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

- **Severity:** High 7.8 (`AV:N/AC:L/Au:N/C:C/I:N/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-p3mm-5q72-22q5

## What is CVE-2006-2102?

CVE-2006-2102 is a high-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 PowerISO 2.9 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-2102?

It affects 1 product.


Products: Poweriso Poweriso.

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

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

## Is CVE-2006-2102 being exploited?

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

Public exploit code:

- poweriso 2.9 - Directory Traversal (exploitdb)

## Other vulnerabilities in n/a

- [CVE-2021-21871](https://insights.sbomify.com/CVE-2021-21871/): Memory corruption in PowerISO (high 8.8)
- [CVE-2017-2817](https://insights.sbomify.com/CVE-2017-2817/): Memory corruption in PowerISO (high 8.8)
- [CVE-2017-2823](https://insights.sbomify.com/CVE-2017-2823/): Use after free in PowerIso (high 8.8)
- [CVE-2022-41992](https://insights.sbomify.com/CVE-2022-41992/): Memory corruption in PowerISO (high 7.8)

## Fix prompt for AI coding agents

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

What it is: CVE-2006-2102 is a high-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-2102 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-2102/ (Markdown: https://insights.sbomify.com/CVE-2006-2102/index.md)
```

## Sources

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

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