dbcve.org
Sd WanApplication · Cisco

CVE-2020-3180

HIGH · 7.8 CVSS v3.1 Published 2020-07-16
Fix available
A fix is available. Upgrade to 18.3.6 / 18.4.5 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 Cisco SD-WAN Solution Software could allow an unauthenticated, local attacker to access an affected device by using an account that has a default, static password. This account has root privileges. The vulnerability exists because the affected software has a user account with a default, static password. An attacker could exploit this vulnerability by remotely connecting to an affected system by using this account. A successful exploit could allow the attacker to log in by using this account with root privileges.

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

Cisco SD-WAN Solution Software contains a hardcoded default account with static credentials that grants root-level privileges. An unauthenticated attacker can remotely connect to affected devices using this account to gain full administrative control.

MitigationImmediately change or disable the default account credentials and rotate to strong, unique passwords. Update to a patched Cisco SD-WAN version following Cisco's advisory.

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 WanApplication
Affected:>= 18.3.0, < 18.3.6>= 18.4.0, < 18.4.5>= 19.2.0, < 19.2.2

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 installed SD-WAN software version
    Access the device CLI or admin interface and run the command to display the software version (typically 'show version' or available via the vmanage dashboard under 'Maintenance > Software Upgrade')
    Affected if The installed version falls within these ranges: 18.3.0 through 18.3.5, 18.4.0 through 18.4.4, or 19.2.0 through 19.2.1
  2. Confirm the device is running Cisco SD-WAN
    Verify the device is a Cisco SD-WAN vedge router, vmanage, vbond, or vsmart controller by checking the system type in the CLI ('show system info' or 'show device-role') or admin interface
    Affected if The device is identified as a Cisco SD-WAN component (vedge, vmanage, vbond, or vsmart)
  3. Check for unauthorized or unexpected user accounts
    List all local user accounts on the system using 'show users' or by reviewing the user database in the SD-WAN admin interface under 'Administration > User Management'
    Affected if An unexpected default account with administrative or root-level privileges exists that was not created by your organization
  4. Verify if default/root access is exposed externally
    Review the device's authentication configuration and access settings. Check if remote authentication is enabled and whether the default administrative interface (typically ports 443, 22, or 12346) is accessible from untrusted networks
    Affected if The device allows remote administrative access and the hardcoded default account is still enabled
  5. Inspect authentication logs for unauthorized access
    Review authentication and system logs for the SD-WAN device (via 'show log' or the vmanage logging interface) focusing on authentication events, especially those from IP addresses outside your organization
    Affected if There are successful authentication events using a default or unknown account, or authentication attempts using the hardcoded credentials

A user is affected if they are running any Cisco SD-WAN version in the ranges 18.3.0-18.3.5, 18.4.0-18.4.4, or 19.2.0-19.2.1 AND the hardcoded default administrative account remains enabled on the device.

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 / 18.4.5 / 19.2.2 or later
Fixed in 18.3.618.4.519.2.2
Interim mitigation

Immediately change or disable the default account credentials and rotate to strong, unique passwords. Update to a patched Cisco SD-WAN version following Cisco's advisory.

Fix this in Sd Wan Scoped from the published advisory
  • Consultation2.0 h
  • Implementation1.0 h
  • Testing2.0 h
  • Review / QA1.0 h
6.0 hours of engineering $1,060
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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