Videoscape Distribution Suite Service ManagerApplication · Cisco
CVE-2015-6364
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 · uneditedCisco Content Delivery System Manager Software 3.2 on Videoscape Distribution Suite Service Manager allows remote attackers to obtain sensitive information via crafted URLs in REST API requests, aka Bug ID CSCuv86960.
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 · moderate confidenceCisco Content Delivery System Manager Software 3.2 contains an information disclosure vulnerability in its REST API. Remote unauthenticated attackers can craft specific URLs to access sensitive information that should not be exposed, likely due to missing or insufficient authorization checks on REST API endpoints.
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
<= 3.2.0CVSS 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
- Partial
- Integrity
- None
- Availability
- None
AV:N/AC:L/Au:N/C:P/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 checksWork through these to decide whether this CVE applies to you.
-
Identify installed product and versionLocate the Cisco Content Delivery System Manager or Videoscape Distribution Suite Service Manager installation and determine its version number. This is typically found in the software's about page, a version file, or by querying the system inventory.Affected if The installed version is Cisco Videoscape Distribution Suite Service Manager 3.2.0 or lower.
-
Verify REST API service is runningCheck if the REST API service component is running on the system. This may involve checking running processes, listening network ports (commonly 8080, 8443, or custom API ports), or the service management console.Affected if The REST API service is exposed and running on the system.
-
Confirm API endpoint accessibilityAttempt to access the REST API endpoints without authentication. Check if the API base URL (typically /api, /rest, or /CDSManager) responds to unauthenticated requests.Affected if The REST API endpoints are accessible without any authentication credentials.
-
Check for authorization configuration gapsReview the REST API configuration files or access control settings to determine if authorization validation is properly enforced on all API endpoints.Affected if Authorization checks are missing or insufficient on REST API endpoints.
A system is affected if it runs Cisco Videoscape Distribution Suite Service Manager version 3.2.0 or lower with the REST API service exposed and accessible without authentication.
Generated from the published advisory. Verify against your own configuration.
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 dataRestrict access to REST API endpoints and implement proper authorization validation for all API requests. Validate and sanitize URL parameters to prevent unauthorized access to sensitive data.
Fix this in Videoscape Distribution Suite Service Manager
Scoped from the published advisory
- Consultation4.0 h
- Implementation8.0 h
- Testing4.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,408.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2015-6364 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2015-6364 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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