dbcve.org
Vedge 100 FirmwareOperating system · Cisco

CVE-2019-1646

HIGH · 7.8 CVSS v3.1 Published 2019-01-24
Fix available
A fix is available. Upgrade to 18.4.0 or later.
See remediation →
80/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 local CLI of the Cisco SD-WAN Solution could allow an authenticated, local attacker to escalate privileges and modify device configuration files. The vulnerability exists because user input is not properly sanitized for certain commands at the CLI. An attacker could exploit this vulnerability by sending crafted commands to the CLI of an affected device. A successful exploit could allow the attacker to establish an interactive session with elevated privileges. The attacker could then use the elevated privileges to further compromise the device or obtain additional configuration data from the device.

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

A command injection vulnerability in the local CLI of Cisco SD-WAN Solution allows authenticated users to escape their privilege boundaries. Insufficient input sanitization on certain CLI commands enables crafted inputs to execute with elevated privileges, allowing modification of device configuration files and further compromise.

MitigationApply the vendor-supplied patch for Cisco SD-WAN. Restrict CLI access to only essential personnel, implement least-privilege access controls, and monitor CLI command logs for anomalous patterns indicative of exploitation attempts.

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
Vedge 100 FirmwareOperating system
Affected:all versions
Vedge 1000 FirmwareOperating system
Affected:all versions
Vedge 2000 FirmwareOperating system
Affected:all versions
Vedge 5000 FirmwareOperating system
Affected:all versions
Sd WanApplication
Affected:< 18.4.0
Vbond OrchestratorApplication
Affected:all versions
Vmanage Network ManagementApplication
Affected:all versions
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
Local
Complexity
Low
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:L/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 device model and firmware version
    Access the device CLI and run `show version` or `show hardware` to identify the device model (Vedge 100/1000/2000/5000, Vbond, Vmanage, or Vsmart) and current firmware/software version
    Affected if Device is a Cisco Vedge, Vbond Orchestrator, Vmanage, or Vsmart running software version below 18.4.0, or any version for Vedge 100/1000/2000/5000 models where all versions are affected
  2. Confirm CLI access is available
    Verify that local CLI access is enabled and accessible to authenticated users by checking the device configuration for CLI-related settings or attempting to access the CLI interface
    Affected if Local CLI is accessible to authenticated users (this is the attack vector for CVE-2019-1646)
  3. Check SD-WAN software release version
    Run `show software` or `show version` to obtain the exact SD-WAN software release number
    Affected if Software release is earlier than 18.4.0 for Cisco SD-WAN products (this is the primary version threshold)
  4. Review user privilege assignments
    Examine user privilege levels and role assignments in the device configuration using `show users` or similar commands to identify which authenticated users have CLI access
    Affected if Any authenticated user with CLI access exists on an affected version, as they could potentially exploit the command injection

You are affected if you are running any Cisco SD-WAN product (Vedge, Vbond, Vmanage, Vsmart) with software version below 18.4.0 and have CLI access enabled for authenticated users.

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 the vendor-supplied patch for Cisco SD-WAN. Restrict CLI access to only essential personnel, implement least-privilege access controls, and monitor CLI command logs for anomalous patterns indicative of exploitation attempts.

Fix this in Vedge 100 Firmware Scoped from the published advisory
  • Consultation3.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
12.0 hours of engineering $2,130
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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