# CVE-2006-3595: Missing authorization in n/a

> Remote attackers can access the Cisco Router Web Setup server with arbitrary privileges due to missing authentication in the default configuration.

- **Severity:** High 7.5 (`AV:N/AC:L/Au:N/C:P/I:P/A:P`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 14 Jul 2006
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-63x6-9wjm-8hc2

## What is CVE-2006-3595?

CVE-2006-3595 is a high-severity missing authorization vulnerability in n/a, published on 14 Jul 2006. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

The default configuration of IOS HTTP server in Cisco Router Web Setup (CRWS) before 3.3.0 build 31 does not require credentials, which allows remote attackers to access the server with arbitrary privilege levels, aka bug CSCsa78190.

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

It affects 1 product.


Products: Cisco Router Web Setup.

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

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

## Is CVE-2006-3595 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2006-3595 is a high-severity missing authorization vulnerability in n/a, published on 14 Jul 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-3595 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-3595/ (Markdown: https://insights.sbomify.com/CVE-2006-3595/index.md)
```

## Sources

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

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