Sd Wan FirmwareOperating system · Cisco

CVE-2019-1626

HIGH · 8.8 CVSS v3.1 Published 2019-06-20
Fix available
A fix is available. Upgrade to after 18.3.6 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 vManage web-based UI (Web UI) of the Cisco SD-WAN Solution could allow an authenticated, remote attacker to gain elevated privileges on an affected vManage device. The vulnerability is due to a failure to properly authorize certain user actions in the device configuration. An attacker could exploit this vulnerability by logging in to the vManage Web UI and sending crafted HTTP requests to vManage. A successful exploit could allow attackers to gain elevated privileges and make changes to the configuration that they would not normally be authorized to make.

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

This is an authorization bypass vulnerability in Cisco SD-WAN vManage web UI where authenticated users can send crafted HTTP requests to escalate privileges beyond what their account is normally authorized for. The root cause is improper authorization checks on certain device configuration actions, allowing attackers to gain elevated privileges and make unauthorized configuration changes.

MitigationApply the Cisco patch for this vulnerability; in the interim, limit vManage web UI access to only trusted administrators and monitor for suspicious HTTP request patterns.

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

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 vManage firmware version
    Log into the vManage admin interface or use the CLI command 'show version' to retrieve the installed firmware version
    Affected if The installed version is 18.3.6 or any earlier version (18.3.x, 18.2.x, 18.1.x, 17.x, or earlier)
  2. Confirm vManage web UI is accessible
    Verify that the vManage web interface is running and reachable on the network
    Affected if The vManage web UI is exposed and accessible
  3. Review admin account modifications
    Check the vManage user administration panel for any unauthorized changes to user roles, permissions, or newly created administrative accounts
    Affected if There are unexpected admin accounts or modifications to existing account privileges that were not authorized
  4. Examine audit logs for configuration change requests
    Review vManage system logs and audit trails for any device configuration actions performed via the web UI that were initiated by users without proper authorization
    Affected if Logs show configuration changes made by users operating outside their normal authorization scope

Your environment is affected if you are running Cisco SD-WAN vManage firmware version 18.3.6 or earlier, and the vManage web UI is accessible to authenticated users who could exploit the authorization bypass.

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 a release after 18.3.6
Interim mitigation

Apply the Cisco patch for this vulnerability; in the interim, limit vManage web UI access to only trusted administrators and monitor for suspicious HTTP request patterns.

Fix this in Sd Wan Firmware Scoped from the published advisory
  • Consultation6.0 h
  • Implementation12.0 h
  • Testing10.0 h
  • Review / QA4.0 h
32.0 hours of engineering $5,580
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2019-1626 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

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-1626 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