# CVE-2008-3329: Path traversal in n/a

> Attackers can execute arbitrary code via crafted URLs when the browser is configured to use only proxies.

- **Severity:** Critical 9.3 (`AV:N/AC:M/Au:N/C:C/I:C/A:C`)
- **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:** 27 Jul 2008
- **Updated:** 7 Aug 2024
- **Also known as:** DEBIAN-CVE-2008-3329, GHSA-6j4p-vq7v-x6g8

## What is CVE-2008-3329?

CVE-2008-3329 is a critical path traversal vulnerability in n/a, published on 27 Jul 2008. 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

Unspecified vulnerability in Links before 2.1, when "only proxies" is enabled, has unknown impact and attack vectors related to providing "URLs to external programs."

Weakness: CWE-59 (Improper Link Resolution Before File Access)

## Which versions are affected by CVE-2008-3329?

It affects 1 product.


Products: Twibright Links.

## How do I fix CVE-2008-3329?

Upgrade to a fixed version.

## Is CVE-2008-3329 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2017-11114](https://insights.sbomify.com/CVE-2017-11114/): Memory corruption in n/a (medium 5.5)
- [CVE-2013-6050](https://insights.sbomify.com/CVE-2013-6050/): Integer overflow in n/a (medium 4.3)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2008-3329 and fix it if it is affected.

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

## Sources

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

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