Vision Dynamic Signage DirectorApplication · Cisco
CVE-2019-1917
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 · uneditedA vulnerability in the REST API interface of Cisco Vision Dynamic Signage Director could allow an unauthenticated, remote attacker to bypass authentication on an affected system. The vulnerability is due to insufficient validation of HTTP requests. An attacker could exploit this vulnerability by sending a crafted HTTP request to an affected system. A successful exploit could allow the attacker to execute arbitrary actions through the REST API with administrative privileges on the affected system. The REST API is enabled by default and cannot be disabled.
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 confidenceA critical authentication bypass vulnerability exists in the REST API of Cisco Vision Dynamic Signage Director. The flaw stems from insufficient validation of HTTP requests, allowing unauthenticated remote attackers to send crafted requests that bypass authentication entirely. Successful exploitation grants the attacker full administrative privileges to execute arbitrary actions through the REST API.
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
Vision Dynamic Signage DirectorApplication
<= 5.0>= 6.0, <= 6.1= 5.0= 6.1CVSS 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
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
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 version of Cisco Vision Dynamic Signage DirectorAccess the administration interface or check the software version through the built-in system information page, typically found under Settings > System > About in the web management consoleAffected if The installed version is 5.0, 6.0, or 6.1 (or any version <= 5.0 or between 6.0 and 6.1 inclusive)
-
Confirm REST API is enabledLocate the REST API configuration settings within the Cisco Vision Dynamic Signage Director administration panel, typically under Settings > Integration or Settings > APIAffected if The REST API feature is enabled and accessible in the environment
-
Check network accessibility of the REST API endpointVerify if the REST API port (default HTTPS port 443 or custom configured port) is exposed to untrusted networks by reviewing firewall rules, network ACLs, or performing a port scan from an external locationAffected if The REST API endpoint is reachable from networks outside the trusted internal segment
-
Review API access logs for unauthorized administrative actionsExamine the Cisco Vision Dynamic Signage Director logs, typically stored in /opt/cisco/vision/logs or accessible through the admin console under Logs > API Logs, for any administrative API calls originating from unexpected IP addresses without corresponding authentication eventsAffected if Administrative API actions are logged without prior successful authentication events in the audit trail
A defender is affected if they are running Cisco Vision Dynamic Signage Director version 5.0, 6.0, or 6.1 with the REST API enabled and exposed to network paths where unauthenticated attackers could send crafted HTTP requests.
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.
dbcve · scopedApply vendor patches when available; until then, implement strict network segmentation and firewall rules to restrict access to the affected system's IP address, as the REST API cannot be disabled.
Version 6.2 or later
- Identify the current Cisco Vision Dynamic Signage Director version by accessing the administration console or checking system documentation
- Navigate to the Cisco Software Download page for Vision Dynamic Signage Director at tools.cisco.com or contact Cisco TAC to obtain the fixed release
- Download and install version 6.2 or later (the first fixed release that addresses CVE-2019-1917)
- After upgrade, verify the REST API authentication bypass is resolved by confirming that unauthenticated requests are properly rejected
- Review all administrative accounts and API keys for any unauthorized changes made during the vulnerability window
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in Vision Dynamic Signage Director
Scoped from the published advisory
- Consultation3.0 h
- Implementation6.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,224.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2019-1917 — 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-2019-1917 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