dbcve.org
Sd WanApplication · Cisco

CVE-2019-1647

HIGH · 8.0 CVSS v3.0 Published 2019-01-24
Fix available
A fix is available. Upgrade to 18.4.0 or later.
See remediation →
82/100
Remediation priority · High
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
A vulnerability in the Cisco SD-WAN Solution could allow an authenticated, adjacent attacker to bypass authentication and have direct unauthorized access to other vSmart containers. The vulnerability is due to an insecure default configuration of the affected system. An attacker could exploit this vulnerability by directly connecting to the exposed services. An exploit could allow the attacker to retrieve and modify critical system files.

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 confidence

The Cisco SD-WAN vSmart controllers have an insecure default configuration that exposes services directly. An authenticated attacker with adjacent network access can bypass authentication mechanisms and connect directly to these exposed services, allowing unauthorized access to other vSmart containers and the ability to retrieve and modify critical system files.

MitigationApply Cisco's patches for this vulnerability and reconfigure the system to disable insecure default settings. Restrict access to exposed services and implement proper authentication controls per Cisco's hardening guidelines.

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
Sd WanApplication
Affected:< 18.4.0
Vsmart ControllerApplication
Affected:all versions

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
Adjacent
Complexity
Low
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.0/AV:A/AC:L/PR:L/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 checks

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

  1. Identify Cisco vSmart controllers in your environment
    Locate all Cisco SD-WAN vSmart controller devices or virtual machines running the vSmart controller software. Check your inventory or use network discovery to find devices running the vSmart controller process.
    Affected if You have any Cisco vSmart controllers deployed in your network.
  2. Check the installed vSmart software version
    Access the vSmart controller CLI and run the command to display the software version, typically 'show version' or 'show software'. Compare the version number against the affected range of versions prior to 18.4.0.
    Affected if The vSmart controller version is < 18.4.0 (or if the version cannot be determined but the device is a Vsmart Controller).
  3. Verify network exposure of vSmart management services
    Review network access control lists, firewall rules, and segment configurations to determine if vSmart management or control plane services (such as HTTP, HTTPS, or other management interfaces) are accessible from network segments where unauthorized users could reside.
    Affected if Management or control services on the vSmart controller are exposed to adjacent or untrusted network segments without proper access restrictions.
  4. Check for default service accessibility
    From a host on an adjacent network segment, attempt to reach typical vSmart management ports (commonly 443/tcp, 8080/tcp, or as documented in Cisco SD-WAN deployment guides) to confirm if the controller responds to connection attempts without requiring authentication.
    Affected if The vSmart controller accepts connections on exposed service ports from unauthorized adjacent network hosts.
  5. Confirm authentication configuration for exposed services
    Review the vSmart controller configuration to verify whether default authentication settings have been modified or whether service-level access controls have been explicitly configured to prevent unauthenticated access.
    Affected if The controller is using default configuration with services exposed and no explicit authentication controls applied to the accessible ports.

You are affected if you operate any Cisco vSmart controller with software version < 18.4.0 (or any version of Vsmart Controller) that has management or control services exposed to adjacent networks without proper authentication hardening.

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 18.4.0 or later
Fixed in 18.4.0
Interim mitigation

Apply Cisco's patches for this vulnerability and reconfigure the system to disable insecure default settings. Restrict access to exposed services and implement proper authentication controls per Cisco's hardening guidelines.

Fix this in Sd Wan Scoped from the published advisory
  • Consultation6.0 h
  • Implementation12.0 h
  • Testing6.0 h
  • Review / QA3.0 h
27.0 hours of engineering $4,800
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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