dbcve.org
Vedge 100 FirmwareOperating system · Cisco

CVE-2019-1648

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 user group configuration of the Cisco SD-WAN Solution could allow an authenticated, local attacker to gain elevated privileges on an affected device. The vulnerability is due to a failure to properly validate certain parameters included within the group configuration. An attacker could exploit this vulnerability by writing a crafted file to the directory where the user group configuration is located in the underlying operating system. A successful exploit could allow the attacker to gain root-level privileges and take full control of 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 · high confidence

Local privilege escalation vulnerability in Cisco SD-WAN user group configuration. An authenticated attacker with local access can write a crafted file to the group configuration directory, bypassing validation of certain parameters to gain root-level privileges and full device control.

MitigationApply Cisco-provided patches for affected SD-WAN software versions; review and validate user group configurations for unauthorized or suspicious entries; restrict local administrative access to minimize attack surface.

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 the Cisco SD-WAN product and version
    Run 'show version' or access the device CLI to determine the exact firmware/software version and product model (Vedge 100, 1000, 2000, 5000, Vbond, Vmanage, or Vsmart)
    Affected if The product is any Vedge model (all versions affected) or the version is below 18.4.0 for Cisco SD-WAN, or any version of Vbond/Vmanage/Vsmart
  2. Verify local administrative access is enabled
    Check if local user authentication and console/SSH access to the device management interface is configured and active
    Affected if Local authentication and management access are enabled, providing an attacker the authentication required to exploit this flaw
  3. Inspect user group configuration directory
    Locate and review configuration files in the user group configuration directory (typically under /config or /etc directory structure). Use 'ls' or 'find' to locate group configuration files and examine their contents for any unexpected or unauthorized group entries
    Affected if Suspicious or unauthorized user group entries exist in the configuration that were not created by legitimate administrators
  4. Review user group file permissions and ownership
    Check file permissions on group configuration files using 'ls -la' to see if they are writable by non-privileged users or if any files have unexpected modification timestamps
    Affected if Configuration files have permissive write access or show recent unexpected modifications
  5. Compare current configuration against known-good baseline
    Review the current user group configuration against documented baselines or backup copies to identify unauthorized changes or entries
    Affected if The current configuration contains group entries or parameters that differ from the expected baseline configuration

The environment is affected if the device runs any version of Cisco Vedge (all versions), Cisco Vbond, Vmanage, or Vsmart (all versions), or Cisco SD-WAN below version 18.4.0, and local administrative access is available to authenticate and write to the user group configuration directory.

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-provided patches for affected SD-WAN software versions; review and validate user group configurations for unauthorized or suspicious entries; restrict local administrative access to minimize attack surface.

Fix this in Vedge 100 Firmware Scoped from the published advisory
  • Consultation6.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA4.0 h
24.0 hours of engineering $4,260
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,816.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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