# CVE-2006-3290: Information disclosure in n/a

> Remote attackers can obtain usernames and directory paths by accessing sensitive files directly via URL in Cisco WCS.

- **Severity:** Medium 5.0 (`AV:N/AC:L/Au:N/C:P/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 28 Jun 2006
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-3rjp-6929-2mrw

## What is CVE-2006-3290?

CVE-2006-3290 is a medium-severity vulnerability in n/a, published on 28 Jun 2006. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

HTTP server in Cisco Wireless Control System (WCS) for Linux and Windows before 3.2(51) stores sensitive information under the web root with insufficient access control, which allows remote attackers to obtain usernames and directory paths via a direct URL request.

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

It affects 1 product.


Products: Cisco Wireless Control System.

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

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

## Is CVE-2006-3290 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2007-5382](https://insights.sbomify.com/CVE-2007-5382/): Hardcoded credentials in n/a (critical 10.0)
- [CVE-2007-2034](https://insights.sbomify.com/CVE-2007-2034/): Privilege escalation in n/a (critical 9.0)
- [CVE-2007-2035](https://insights.sbomify.com/CVE-2007-2035/): Information disclosure in n/a (high 7.8)
- [CVE-2007-2032](https://insights.sbomify.com/CVE-2007-2032/): Hardcoded credentials in n/a (high 7.5)
- [CVE-2006-3285](https://insights.sbomify.com/CVE-2006-3285/): Hardcoded credentials in n/a (high 7.5)

## Fix prompt for AI coding agents

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

What it is: CVE-2006-3290 is a medium-severity vulnerability in n/a, published on 28 Jun 2006. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2006-3290 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-3290/ (Markdown: https://insights.sbomify.com/CVE-2006-3290/index.md)
```

## Sources

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

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