Sd Wan FirmwareOperating system · Cisco

CVE-2019-12629

HIGH · 7.2 CVSS v3.1 Published 2020-01-26
Fix available
A fix is available. Upgrade to 18.3.0 or later.
See remediation →
78/100
Remediation priority · High
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 WebUI of the Cisco SD-WAN Solution could allow an authenticated, remote attacker to inject and execute arbitrary commands with vmanage user privileges on an affected system. The vulnerability is due to insufficient input validation of data parameters for certain fields in the affected solution. An attacker could exploit this vulnerability by configuring a malicious username on the login page of the affected solution. A successful exploit could allow the attacker to inject and execute arbitrary commands with vmanage user privileges on an affected system.

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

A command injection vulnerability in the Cisco SD-WAN Solution WebUI allows authenticated remote attackers to execute arbitrary commands with vmanage user privileges. The flaw exists due to insufficient input validation on the username field during login, allowing malicious payload injection that gets executed with the privileges of the vmanage user account.

MitigationApply Cisco's official patch for CVE-2019-12629 when available. In the interim, restrict access to the SD-WAN WebUI to trusted networks only and monitor for suspicious login attempts with unusual username 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.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
Network
Complexity
Low
Privileges
High
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:H/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. Confirm Cisco SD-WAN vManage is deployed
    Identify whether the target system is a Cisco SD-WAN vManage instance by reviewing system documentation, network diagrams, or logging into the device CLI and checking the product identification.
    Affected if The system is a Cisco SD-WAN vManage deployment
  2. Check SD-WAN firmware version
    Log into the vManage WebUI or CLI and navigate to the version or system information page to retrieve the installed firmware version. Compare this version against the 18.3.0 threshold.
    Affected if The installed firmware version is below 18.3.0
  3. Verify WebUI is network-accessible
    Review firewall rules, ACLs, or interface configurations to determine if the vManage WebUI interface (typically ports 443 or 8443) is accessible from networks outside the trusted administrative zone.
    Affected if The WebUI is exposed to untrusted or external networks
  4. Confirm authentication is enabled
    Check the vManage authentication settings to verify whether local user authentication is enabled for WebUI access.
    Affected if Local authentication is enabled on the vManage WebUI

The environment is affected if it runs Cisco SD-WAN vManage with firmware version below 18.3.0, has the WebUI exposed, and uses local authentication.

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.0 or later
Fixed in 18.3.0
Interim mitigation

Apply Cisco's official patch for CVE-2019-12629 when available. In the interim, restrict access to the SD-WAN WebUI to trusted networks only and monitor for suspicious login attempts with unusual username patterns.

Fix this in Sd Wan Firmware Scoped from the published advisory
  • Consultation4.0 h
  • Implementation6.0 h
  • Testing4.0 h
  • Review / QA3.0 h
17.0 hours of engineering $3,020
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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