# CVE-2010-0593: Information disclosure in n/a

> Authenticated attackers can obtain sensitive password information from Cisco routers and video cameras via crafted URLs or privilege abuse.

- **Severity:** Critical 9.0 (`AV:N/AC:L/Au:S/C:C/I:C/A:C`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 22 Apr 2010
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-5m7m-mrc8-69mh

## What is CVE-2010-0593?

CVE-2010-0593 is a critical vulnerability in n/a, published on 22 Apr 2010. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

The Cisco RVS4000 4-port Gigabit Security Router before 1.3.2.0, PVC2300 Business Internet Video Camera before 1.1.2.6, WVC200 Wireless-G PTZ Internet Video Camera before 1.1.1.15, WVC210 Wireless-G PTZ Internet Video Camera before 1.1.1.15, and WVC2300 Wireless-G Business Internet Video Camera before 1.1.2.6 do not properly restrict read access to passwords, which allows context-dependent attackers to obtain sensitive information, related to (1) access by remote authenticated users to a PVC2300 or WVC2300 via a crafted URL, (2) leveraging setup privileges on a WVC200 or WVC210, and (3) leveraging administrative privileges on an RVS4000, aka Bug ID CSCte64726.

Weakness: CWE-264

## Which versions are affected by CVE-2010-0593?

It affects 5 products.


Products: Cisco Pvc2300, Cisco Rvs4000, Cisco Wvc200, Cisco Wvc210, Cisco Wvc2300.

## How do I fix CVE-2010-0593?

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

## Is CVE-2010-0593 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2010-0593 and fix it if it is affected.

What it is: CVE-2010-0593 is a critical vulnerability in n/a, published on 22 Apr 2010. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2010-0593 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-2010-0593/ (Markdown: https://insights.sbomify.com/CVE-2010-0593/index.md)
```

## Sources

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

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