dbcve.org
Vedge 100 FirmwareOperating system · Cisco

CVE-2019-1650

HIGH · 8.8 CVSS v3.1 Published 2019-01-24
Fix available
A fix is available. Upgrade to 18.4.0 or later.
See remediation →
94/100
Remediation priority · Urgent
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
A vulnerability in the Cisco SD-WAN Solution could allow an authenticated, remote attacker to overwrite arbitrary files on the underlying operating system of an affected device. The vulnerability is due to improper input validation of the save command in the CLI of the affected software. An attacker could exploit this vulnerability by modifying the save command in the CLI of an affected device. A successful exploit could allow the attacker to overwrite arbitrary files on the underlying operating system of an affected device and escalate their privileges to the root user.

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

The Cisco SD-WAN Solution contains an improper input validation vulnerability in the CLI save command. An authenticated attacker can modify the save command to write arbitrary files to the underlying operating system and escalate privileges to root user.

MitigationApply the Cisco security update for CVE-2019-1650 when available. Until then, restrict CLI access to trusted personnel only and implement network segmentation to limit exposure.

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

CVSS:3.1/AV:N/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 the Cisco SD-WAN product
    Determine which SD-WAN component is deployed: Vedge 100/1000/2000/5000, Vbond Orchestrator, Vmanage Network Management, or Vsmart Controller. Check the device model or management interface for product identification.
    Affected if The device is any of these listed products.
  2. Check the installed version
    Access the CLI or management interface and retrieve the firmware/software version. For Vedge devices, use 'show version' or check the firmware version in the device management console. For Vmanage, Vbond, or Vsmart, check the software version through the management interface or 'show version' command.
    Affected if The product is Vedge with any firmware version, or Vbond/Vmanage/Vsmart with any version, or Cisco SD-WAN software version is below 18.4.0.
  3. Verify CLI access is available
    Confirm that CLI access (SSH or console) is enabled and accessible. The vulnerability requires an authenticated attacker to access the CLI to exploit the improper input validation in the save command.
    Affected if CLI access is enabled and reachable on the device.
  4. Review save command functionality
    Examine the CLI save command configuration and its allowed parameters. The vulnerability allows path traversal through the save command to write files outside the intended directory.
    Affected if The save command permits arbitrary file path specification without proper validation.

A user is affected if they are running any version of Cisco Vedge, Vbond, Vmanage, Vsmart, or Cisco SD-WAN software prior to version 18.4.0, and CLI access is available to 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 Cisco security update for CVE-2019-1650 when available. Until then, restrict CLI access to trusted personnel only and implement network segmentation to limit exposure.

Fix this in Vedge 100 Firmware Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA4.0 h
22.0 hours of engineering $3,860
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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