dbcve.org
Video Surveillance ManagerApplication · Cisco

CVE-2013-3430

HIGH · 9.0 CVSS v2.0 Published 2013-07-25
Fix available
A fix is available. Upgrade to after 6.3.3 or later.
See remediation →
99/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click

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
Cisco Video Surveillance Manager (VSM) before 7.0.0 allows remote attackers to obtain sensitive configuration, archive, and log information via unspecified vectors, related to the Cisco_VSBWT (aka Broadware sample code) package, aka Bug ID CSCsv37288.

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 · high confidence

Cisco Video Surveillance Manager (VSM) versions prior to 7.0.0 contain an information disclosure vulnerability in the Cisco_VSBWT (Broadware sample code) package. Remote attackers can exploit unspecified vectors to obtain sensitive configuration files, archives, and log files, potentially revealing system credentials, network details, and operational information.

MitigationUpgrade Cisco VSM to version 7.0.0 or later to obtain the vendor patch. If immediate patching is not feasible, restrict network access to the VSM management interfaces and monitor for unauthorized access to configuration and log directories.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

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
Video Surveillance ManagerApplication
Affected:<= 6.3.3= 1.1.0= 1.2.1= 2.0.0= 2.1= 2.1.2= 2.1.3= 2.1.4= 2.1.6= 2.1.7= 2.3.0= 2.3.1

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
None
Confidentiality
Complete
Integrity
Partial
Availability
Partial

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

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify if Cisco VSM is installed
    Check the installed software or running services for Cisco Video Surveillance Manager. This may be visible in package lists, running processes, or installed applications on the system.
    Affected if Cisco VSM software is found on the system
  2. Determine the installed VSM version
    Use system commands to query the installed version of Cisco Video Surveillance Manager, such as checking installed packages, reviewing VSM about information, or examining version files if accessible.
    Affected if The installed version matches one of the affected versions: 6.3.3 or lower, or versions 1.1.0, 1.2.1, 2.0.0, 2.1, 2.1.2, 2.1.3, 2.1.4, 2.1.6, 2.1.7, 2.3.0, or 2.3.1
  3. Check for Cisco_VSBWT component presence
    Examine the VSM installation for the presence of the Cisco_VSBWT (Broadware sample code) package or component, which contains the vulnerable code.
    Affected if The Cisco_VSBWT package is installed and enabled as part of the VSM deployment
  4. Review accessible configuration and log directories
    Inspect the file system for exposed configuration files, archives, or log files that may be accessible through the vulnerability. Check directory permissions and network-accessible shares.
    Affected if Sensitive configuration files, archives, or logs are found accessible without proper authentication

A user is affected if Cisco Video Surveillance Manager is installed with a version prior to 7.0.0 and the Cisco_VSBWT component is present and accessible on the network.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 6.3.3
Interim mitigation

Upgrade Cisco VSM to version 7.0.0 or later to obtain the vendor patch. If immediate patching is not feasible, restrict network access to the VSM management interfaces and monitor for unauthorized access to configuration and log directories.

Recommended fix High confidence

Cisco Video Surveillance Manager 7.0.0 or later

  1. Identify the current version of Cisco Video Surveillance Manager running in your environment
  2. If the current version is 6.3.3 or lower, or is specifically version 1.1.0, 1.2.1, or 2.0.0, the system is vulnerable
  3. Plan and schedule an upgrade to Cisco Video Surveillance Manager version 7.0.0 or later
  4. Obtain the upgrade package from Cisco's official download portal (tools.cisco.com)
  5. Follow Cisco's standard upgrade procedure for VSM, ensuring proper backups are taken before proceeding
  6. After upgrade, verify the new version is 7.0.0 or later and confirm the vulnerability is resolved
Caveat As this is a major version upgrade (from 6.x to 7.x), review Cisco VSM 7.0 release notes for any configuration or compatibility changes before upgrading

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

Fix this in Video Surveillance Manager Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,930
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,088.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2013-3430 — 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-2013-3430 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