dbcve.org
Video Surveillance ManagerApplication · Cisco

CVE-2013-3429

HIGH · 7.8 CVSS v2.0 Published 2013-07-25
Fix available
A fix is available. Upgrade to after 6.3.3 or later.
See remediation →
87/100
Remediation priority · High
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
Multiple directory traversal vulnerabilities in Cisco Video Surveillance Manager (VSM) before 7.0.0 allow remote attackers to read system files via a crafted URL, related to the Cisco_VSBWT (aka Broadware sample code) package, aka Bug ID CSCsv37163.

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

Multiple directory traversal vulnerabilities in Cisco Video Surveillance Manager (VSM) versions before 7.0.0 allow remote unauthenticated attackers to read arbitrary system files by crafting malicious URL sequences (such as ../../../'). The vulnerability exists in the Cisco_VSBWT (Broadware sample code) component, enabling path traversal attacks that bypass input validation to access sensitive files outside the intended web root directory.

MitigationUpgrade Cisco VSM to version 7.0.0 or later to obtain the patch for these directory traversal vulnerabilities. If immediate upgrade is not feasible, restrict network access to the VSM management interfaces and implement web application firewall rules to detect and block path traversal patterns in URLs.

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
None
Availability
None

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

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 Cisco VSM installed version
    Access the VSM server CLI and run 'show version' or check the web interface login page for version display. On the management server, check /opt/CSCOsvp/bin/version.txt or similar version files if accessible.
    Affected if The installed version is 6.3.3 or lower, OR matches any of these specific 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
  2. Verify Cisco_VSBWT component presence
    Inspect the web server configuration files (httpd.conf, web.xml) or examine the deployed web applications directory for a component named 'Cisco_VSBWT' or 'Broadware'. Check if the sample code application is deployed on the VSM server.
    Affected if The Cisco_VSBWT or Broadware sample code component is installed and deployed on the VSM server
  3. Confirm web interface is reachable
    Attempt to access the VSM web interface URLs such as https://<VSM-server>/ or check if port 80/443 is listening and accessible from the network. Use 'netstat -an | grep -E "(80|443)"' on the server to confirm HTTP/HTTPS services are running.
    Affected if The VSM web management interface is accessible over the network on HTTP or HTTPS ports

A user is affected if the Cisco VSM version is 6.3.3 or lower, or matches one of the specific affected versions (1.1.0 through 2.3.1), AND the Cisco_VSBWT/Broadware component is present, AND the web interface is network-accessible, allowing path traversal attacks via crafted URL sequences like '../../../'.

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.

From vendor data
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 patch for these directory traversal vulnerabilities. If immediate upgrade is not feasible, restrict network access to the VSM management interfaces and implement web application firewall rules to detect and block path traversal patterns in URLs.

Fix this in Video Surveillance Manager Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA3.0 h
21.0 hours of engineering $3,680
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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