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

> Local attackers can execute arbitrary code by placing malicious configuration files in the current working directory, affecting Lynx users.

- **Severity:** Medium 4.6 (`AV:L/AC:L/Au:N/C:P/I:P/A:P`)
- **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:** 27 Oct 2008
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-cg3w-xm4w-x9rw

## What is CVE-2006-7234?

CVE-2006-7234 is a medium-severity path traversal vulnerability in n/a, published on 27 Oct 2008. 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

Untrusted search path vulnerability in Lynx before 2.8.6rel.4 allows local users to execute arbitrary code via malicious (1) .mailcap and (2) mime.types files in the current working directory.

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

It affects 1 product.


Products: Lynx Lynx.

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

Upgrade to a fixed version.

## Is CVE-2006-7234 being exploited?

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

Public exploit code:

- Lynx 2.8 - '.mailcap'/'.mime.type' Local Code Execution (exploitdb)

## Other vulnerabilities in n/a

- [CVE-2008-4690](https://insights.sbomify.com/CVE-2008-4690/): Command injection in n/a (critical 10.0)
- [CVE-2016-9179](https://insights.sbomify.com/CVE-2016-9179/): Server-side request forgery in n/a (high 7.5)
- [CVE-2010-2810](https://insights.sbomify.com/CVE-2010-2810/): Memory corruption in n/a (medium 6.8)

## Fix prompt for AI coding agents

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

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

## Sources

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

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