Sd WanApplication · Arubanetworks

CVE-2021-37719

HIGH · 7.2 CVSS v3.1 Published 2021-09-07
Fix available
A fix is available. Upgrade to 2.2.0.4 / 6.4.4.25 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 remote arbitrary command execution vulnerability was discovered in Aruba SD-WAN Software and Gateways; Aruba Operating System Software version(s): Prior to 8.6.0.4-2.2.0.4; Prior to 8.7.1.4, 8.6.0.9, 8.5.0.13, 8.3.0.16, 6.5.4.20, 6.4.4.25. Aruba has released patches for Aruba SD-WAN Software and Gateways and ArubaOS that address this security vulnerability.

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

This is a remote arbitrary command execution vulnerability in Aruba SD-WAN Software, Gateways, and ArubaOS. The vulnerability allows an attacker to execute arbitrary commands on affected devices without authentication, likely through a specific interface or service exposed by the software.

MitigationApply the patches released by Aruba for the affected versions (8.6.0.4-2.2.0.4 and later; 8.7.1.4, 8.6.0.9, 8.5.0.13, 8.3.0.16, 6.5.4.20, 6.4.4.25 and later). In the interim, restrict network access to management interfaces and monitor for suspicious 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 WanApplication
Affected:>= 2.2.0.0, < 2.2.0.4
ArubaosOperating system
Affected:>= 6.4.4.0, < 6.4.4.25>= 6.5.4.0, < 6.5.4.20>= 8.3.0.0, < 8.3.0.16>= 8.5.0.0, < 8.5.0.13>= 8.6.0.0, < 8.6.0.9>= 8.7.0.0, < 8.7.1.4

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. Identify the Aruba product type
    Determine whether the device is running Aruba SD-WAN software or ArubaOS. Check the device dashboard, CLI prompt, or firmware filename.
    Affected if The device is either Aruba SD-WAN or ArubaOS
  2. Check SD-WAN version
    Run 'show version' or access the SD-WAN controller UI to view the installed software version.
    Affected if Version is >= 2.2.0.0 and < 2.2.0.4
  3. Check ArubaOS version
    Run 'show version' in the CLI or check the device web interface to obtain the ArubaOS version number.
    Affected if Version matches any of these ranges: >= 6.4.4.0 and < 6.4.4.25; >= 6.5.4.0 and < 6.5.4.20; >= 8.3.0.0 and < 8.3.0.16; >= 8.5.0.0 and < 8.5.0.13; >= 8.6.0.0 and < 8.6.0.9; >= 8.7.0.0 and < 8.7.1.4
  4. Verify management interface exposure
    Check network configuration to determine if the SD-WAN or ArubaOS management interface (typically ports 443, 80, or SSH) is accessible from untrusted networks such as the internet or DMZ.
    Affected if Management interface is exposed to untrusted networks without firewall restrictions

You are affected if the device runs Aruba SD-WAN version 2.2.0.0 through 2.2.0.3.x, or ArubaOS version within any of the six vulnerable ranges listed, AND the management interface is network-accessible to an attacker.

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.

dbcve · scoped
Upgrade available Upgrade to 2.2.0.4 / 6.4.4.25 / 6.5.4.20 or later
Fixed in 2.2.0.46.4.4.256.5.4.20
Interim mitigation

Apply the patches released by Aruba for the affected versions (8.6.0.4-2.2.0.4 and later; 8.7.1.4, 8.6.0.9, 8.5.0.13, 8.3.0.16, 6.5.4.20, 6.4.4.25 and later). In the interim, restrict network access to management interfaces and monitor for suspicious activity.

Recommended fix High confidence

Upgrade to SD-WAN 2.2.0.4+ or ArubaOS 6.4.4.25+, 6.5.4.20+, 8.3.0.16+, 8.5.0.13+, 8.6.0.9+, or 8.7.1.4+ depending on your current branch

  1. 1. Identify the current ArubaOS or SD-WAN version by running 'show version' or checking the web UI
  2. 2. Determine which product line and version family applies (SD-WAN or ArubaOS)
  3. 3. For SD-WAN: Upgrade to version 2.2.0.4 or later
  4. 4. For ArubaOS 6.4.x: Upgrade to version 6.4.4.25 or later
  5. 5. For ArubaOS 6.5.x: Upgrade to version 6.5.4.20 or later
  6. 6. For ArubaOS 8.3.x: Upgrade to version 8.3.0.16 or later
  7. 7. For ArubaOS 8.5.x: Upgrade to version 8.5.0.13 or later
  8. 8. For ArubaOS 8.6.x: Upgrade to version 8.6.0.9 or later
Caveat Standard ArubaOS/SD-WAN upgrade procedures apply; review release notes for any known issues before upgrading

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Sd Wan Scoped from the published advisory
  • Consultation4.0 h
  • Implementation6.0 h
  • Testing8.0 h
  • Review / QA4.0 h
22.0 hours of engineering $3,800
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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