dbcve.org
Sd Wan FirmwareOperating system · Cisco

CVE-2019-1625

HIGH · 7.8 CVSS v3.1 Published 2019-06-20
Fix available
A fix is available. Upgrade to 18.3.6 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 CLI of Cisco SD-WAN Solution could allow an authenticated, local attacker to elevate lower-level privileges to the root user on an affected device. The vulnerability is due to insufficient authorization enforcement. An attacker could exploit this vulnerability by authenticating to the targeted device and executing commands that could lead to elevated privileges. A successful exploit could allow the attacker to make configuration changes to the system as 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

Local privilege escalation vulnerability in Cisco SD-WAN CLI where insufficient authorization enforcement allows authenticated users with lower-level credentials to execute commands that elevate their privileges to root, enabling unauthorized system configuration changes.

MitigationApply Cisco's patch for this vulnerability; implement least-privilege access controls for CLI users and monitor for unauthorized privilege escalation activity.

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 Wan FirmwareOperating system
Affected:< 18.3.6= 18.4.0

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. Determine the installed SD-WAN firmware version
    Access the SD-WAN CLI or management interface and retrieve the firmware version using the 'show version' or 'show system information' command. Compare the output against the affected versions: < 18.3.6 or = 18.4.0.
    Affected if The installed firmware version is less than 18.3.6 or exactly 18.4.0.
  2. Verify CLI user accounts exist
    List all configured CLI users on the SD-WAN device using 'show users' or 'show running-config | include username' in the CLI. Identify whether multiple user accounts with different privilege levels are configured.
    Affected if There are multiple authenticated CLI users with varying privilege levels configured on the system.
  3. Review privilege authorization configuration
    Examine the CLI authorization settings using 'show privilege' or checking the user role assignments in the configuration. Look for any user roles that permit command execution beyond their assigned privilege level.
    Affected if The authorization configuration permits lower-privilege users to execute commands outside their assigned role scope.
  4. Check for unauthorized root-level command access
    Review system logs, audit logs, or use 'show log' commands to identify any instances where non-root users have executed root-level configuration commands.
    Affected if Logs or audit records show non-root users successfully executing commands that require root privileges.

The environment is affected if the SD-WAN firmware version is below 18.3.6 or exactly 18.4.0, and there are authenticated CLI users configured with privileges lower than root who can potentially escalate to root access.

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.3.6 or later
Fixed in 18.3.6
Interim mitigation

Apply Cisco's patch for this vulnerability; implement least-privilege access controls for CLI users and monitor for unauthorized privilege escalation activity.

Fix this in Sd Wan Firmware Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA3.0 h
21.0 hours of engineering $3,680
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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