dbcve.org
Vedge 100 FirmwareOperating system · Cisco

CVE-2021-1510

HIGH · 7.5 CVSS v3.1 Published 2021-05-06
Fix available
A fix is available. Upgrade to 20.4.1 / 20.5.1 or later.
See remediation →
84/100
Remediation priority · High
Remotely reachable No privileges 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
Multiple vulnerabilities in Cisco SD-WAN vEdge Software could allow an attacker to execute arbitrary code as the root user or cause a denial of service (DoS) condition on an affected device. For more information about these vulnerabilities, see the Details section of this advisory.

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 · moderate confidence

Multiple vulnerabilities in Cisco SD-WAN vEdge Software allow an authenticated attacker to execute arbitrary code with root privileges or cause a denial of service condition on affected devices. The CVSS 7.5 score indicates high severity due to the potential for complete system compromise.

MitigationApply the vendor-supplied patches for Cisco SD-WAN vEdge Software as referenced in the Cisco security advisory. If patching is not immediately possible, restrict network access to management interfaces and monitor for indicators of compromise.

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:>= 20.4, < 20.4.1>= 20.5, < 20.5.1= 19.2.99
Vedge 1000 FirmwareOperating system
Affected:>= 20.4, < 20.4.1>= 20.5, < 20.5.1= 19.2.99
Vedge 100b FirmwareOperating system
Affected:>= 20.4, < 20.4.1>= 20.5, < 20.5.1= 19.2.99
Vedge 100m FirmwareOperating system
Affected:>= 20.4, < 20.4.1>= 20.5, < 20.5.1= 19.2.99
Vedge 100wm FirmwareOperating system
Affected:>= 20.4, < 20.4.1>= 20.5, < 20.5.1= 19.2.99
Vedge 2000 FirmwareOperating system
Affected:>= 20.4, < 20.4.1>= 20.5, < 20.5.1= 19.2.99
Vedge 5000 FirmwareOperating system
Affected:>= 20.4, < 20.4.1>= 20.5, < 20.5.1= 19.2.99
Vedge Cloud FirmwareOperating system
Affected:>= 20.4, < 20.4.1>= 20.5, < 20.5.1= 19.2.99

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
None
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
None
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/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 Cisco vEdge device model
    Run 'show version' or 'show hardware' in the vEdge CLI to confirm the model (Vedge 100, 1000, 100b, 100m, 100wm, 2000, 5000, or Cloud)
    Affected if Device model is one of: Vedge 100, 1000, 100b, 100m, 100wm, 2000, 5000, or Cloud
  2. Retrieve installed firmware version
    Execute 'show version' command in the vEdge CLI and note the firmware version displayed in the output
    Affected if Version matches 19.2.99, or is >= 20.4 and < 20.4.1, or is >= 20.5 and < 20.5.1
  3. Verify management interface access
    Review 'show configuration' or interface settings to confirm whether management protocols (HTTP/HTTPS/SSH) are exposed to untrusted networks
    Affected if Management interfaces are accessible from outside trusted networks, enabling the authenticated attacker vector

The environment is affected if the device is a Cisco vEdge model running firmware version 19.2.99, any 20.4.x before 20.4.1, or any 20.5.x before 20.5.1, with management access available to potential attackers.

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 20.4.1 / 20.5.1 or later
Fixed in 20.4.120.5.1
Interim mitigation

Apply the vendor-supplied patches for Cisco SD-WAN vEdge Software as referenced in the Cisco security advisory. If patching is not immediately possible, restrict network access to management interfaces and monitor for indicators of compromise.

Fix this in Vedge 100 Firmware Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA2.0 h
20.0 hours of engineering $3,500
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,600.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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