# CVE-2006-3535: Directory traversal vulnerability in Nullsoft SHOUTcast DSP before 1.9.7 allows remote attackers to read arbitrary files via unspecified vec


- **Severity:** Medium 5.0 (`AV:N/AC:L/Au:N/C:P/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 12 Jul 2006
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-8rff-fq9v-w6rx

## What is CVE-2006-3535?

CVE-2006-3535 is a medium-severity vulnerability in n/a, published on 12 Jul 2006. 

### Official description

Directory traversal vulnerability in Nullsoft SHOUTcast DSP before 1.9.7 allows remote attackers to read arbitrary files via unspecified vectors that are a "slight variation" of CVE-2006-3534.

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

It affects 1 product.


Products: Nullsoft Shoutcast Dsp.

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

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

## Is CVE-2006-3535 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2006-3535 is a medium-severity vulnerability in n/a, published on 12 Jul 2006. 
Exploitation: There is no known exploitation of CVE-2006-3535 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-3535/ (Markdown: https://insights.sbomify.com/CVE-2006-3535/index.md)
```

## Sources

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

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