dbcve.org
Pvc2300Hardware / appliance · Cisco

CVE-2010-0593

HIGH · 9.0 CVSS v2.0 Published 2010-04-22
Fix available
A fix is available. Upgrade to after 1.3.1.0 or later.
See remediation →
96/100
Remediation priority · Urgent
Remotely reachable Zero-click Patch available

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis
How this class of weakness works · CWE-264

A legacy NVD category covering weaknesses where permissions or privileges are assigned, checked, or dropped incorrectly, so an action ends up running with more access than it should. It is an umbrella label from older records, not a single flaw. The remedy depends on the specific case, but the throughline is least privilege with explicit, checked transitions wherever privilege changes.

General guidance for the permissions, privileges & access controls class — the official description and references above are authoritative for this specific CVE. Want a bespoke review and a reviewed fix? Ask our team →

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Pvc2300Hardware / appliance
Affected:<= 1.1.1.4
Wvc200Hardware / appliance
Affected:<= 1.1.0.15= 1.1.0.12
Wvc210Hardware / appliance
Affected:<= 1.1.0.15= 1.1.0.12
Wvc2300Hardware / appliance
Affected:<= 1.1.1.4
Rvs4000Hardware / appliance
Affected:<= 1.3.1.0= 1.3.0.5

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Authentication
Single
Confidentiality
Complete
Integrity
Complete
Availability
Complete

AV:N/AC:L/Au:S/C:C/I:C/A:C

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to a release after 1.3.1.0
Vendor patch www.cisco.com →
Recommended fix High confidence

RVS4000: upgrade to 1.3.2.0 or later; PVC2300: upgrade to 1.1.2.6 or later; WVC200: upgrade to 1.1.1.15 or later; WVC210: upgrade to 1.1.1.15 or later; WVC2300: upgrade to 1.1.2.6 or later

  1. Identify the exact model number (RVS4000, PVC2300, WVC200, WVC210, or WVC2300) of the Cisco device
  2. Access the device's web-based administration interface
  3. Navigate to the Administration or System settings section to locate the firmware version information
  4. Compare current firmware version against the fixed releases: RVS4000 requires 1.3.2.0 or later; PVC2300 and WVC2300 require 1.1.2.6 or later; WVC200 and WVC210 require 1.1.1.15 or later
  5. If the current version is below the fixed release, download the appropriate firmware update from Cisco's support website (www.cisco.com)
  6. Access the firmware upgrade or software update section in the device administration interface
  7. Upload the downloaded firmware file and apply the update
  8. Allow the device to reboot and complete the upgrade process
Caveat Firmware upgrades on embedded devices may reset configuration to defaults; backup current configuration before upgrading and restore after reboot

Generated from the published advisory — verify against the referenced sources before acting.

We can identify the exact fixed release, upgrade, and verify it in staging — typical engagement from $1,950. Get the upgrade done

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2010-0593 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2010-0593 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data