dbcve.org
Videoscape Distribution Suite Service ManagerApplication · Cisco

CVE-2015-6417

MEDIUM · 6.5 CVSS v2.0 Published 2015-12-12
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
71/100
Remediation priority · Elevated
Remotely reachable 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 Videoscape Distribution Suite Service Manager (VDS-SM) 3.4.0 and earlier does not always use RBAC for backend database access, which allows remote authenticated users to read or write to database entries via (1) the GUI or (2) a crafted HTTP request, aka Bug ID CSCuv87025.

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 VDS-SM 3.4.0 and earlier fails to consistently enforce Role-Based Access Control (RBAC) when accessing the backend database. Authenticated users can bypass authorization checks to read or write database entries through the GUI interface or via crafted HTTP requests, exposing sensitive data or allowing unauthorized data manipulation.

MitigationApply the vendor patch for CSCuv87025 (upgrading beyond VDS-SM 3.4.0) to enforce RBAC consistently across all database access paths. If patching is immediately infeasible, restrict network access to the management interface to trusted administrators only.

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
Videoscape Distribution Suite Service ManagerApplication
Affected:= 3.0.0= 3.1.0= 3.2.0= 3.3.0= 3.4.0

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
Partial
Integrity
Partial
Availability
Partial

AV:N/AC:L/Au:S/C:P/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 VDS-SM is installed
    Locate the Cisco Videoscape Distribution Suite Service Manager installation on the system. Check for processes named vds-sm, vdss, or similar Cisco VDS components running on the system.
    Affected if The software is present and running on the system.
  2. Determine the installed version
    Access the VDS-SM management interface or use system commands to retrieve the version number. Common methods include checking the About section in the GUI, running 'show version' via CLI if available, or inspecting installed package information.
    Affected if The installed version is 3.0.0, 3.1.0, 3.2.0, 3.3.0, or 3.4.0 (or earlier).
  3. Verify RBAC enforcement on database access
    Log in to the VDS-SM GUI with a non-administrator account. Attempt to access database functions, query database entries, or navigate to backend database access features through the interface.
    Affected if Low-privilege authenticated users can read or write database entries without proper authorization.
  4. Test HTTP database access paths
    Send crafted HTTP requests to VDS-SM backend database endpoints using a lower-privilege account's credentials. Observe if unauthorized database operations succeed.
    Affected if HTTP requests from authenticated but non-privileged users can bypass RBAC to access or modify database data.
  5. Review user role assignments and database permissions
    Access the VDS-SM administrative console and review which roles have database access permissions. Compare assigned permissions against actual accessible database functions.
    Affected if Users with limited roles can access database features that should be restricted to administrator roles.

A system is affected if Cisco VDS-SM version 3.4.0 or earlier is running and authenticated users with limited privileges can bypass RBAC to read or modify database entries.

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
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Apply the vendor patch for CSCuv87025 (upgrading beyond VDS-SM 3.4.0) to enforce RBAC consistently across all database access paths. If patching is immediately infeasible, restrict network access to the management interface to trusted administrators only.

Fix this in Videoscape Distribution Suite Service Manager Scoped from the published advisory
  • Consultation8.0 h
  • Implementation24.0 h
  • Testing16.0 h
  • Review / QA8.0 h
56.0 hours of engineering $9,760
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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