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

> Attackers can overwrite arbitrary files via OBEX transfers when the recursive option is enabled, requiring user interaction to initiate the session.

- **Severity:** Low 2.6 (`AV:N/AC:H/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:** Yes
- **Published:** 15 May 2006
- **Updated:** 7 Aug 2024
- **Also known as:** DEBIAN-CVE-2006-2366, GHSA-xg56-wphw-5jwj

## What is CVE-2006-2366?

CVE-2006-2366 is a low-severity path traversal vulnerability in n/a, published on 15 May 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

ircp_io.c in libopenobex for ircp 1.2, when ircp is run with the -r option, does not prompt the user when overwriting files, which allows user-assisted remote attackers to overwrite dangerous files via an arbitrary destination file name in an OBEX File Transfer session.

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

It affects 1 product.


Products: Openobex Openobex.

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

Apply the vendor's patch.

## Is CVE-2006-2366 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2006-2366 is a low-severity path traversal vulnerability in n/a, published on 15 May 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: There is no known exploitation of CVE-2006-2366 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-2366/ (Markdown: https://insights.sbomify.com/CVE-2006-2366/index.md)
```

## Sources

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

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