Sd WanApplication · Arubanetworks

CVE-2021-37717

HIGH · 7.2 CVSS v3.1 Published 2021-09-07
Fix available
A fix is available. Upgrade to 2.2.0.6 / 8.3.0.16 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.6; Prior to 8.7.1.4, 8.6.0.7, 8.5.0.12, 8.3.0.16. 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

A remote arbitrary command execution vulnerability in Aruba SD-WAN Software and Gateways and ArubaOS allows authenticated or unauthenticated remote attackers to execute arbitrary commands on affected devices, likely through improper input validation or authentication bypass in the SD-WAN management interface or gateway firmware.

MitigationApply vendor-released patches for affected versions: upgrade to 8.6.0.4-2.2.0.6 or later for the 8.6.x branch; upgrade to 8.7.1.4, 8.6.0.7, 8.5.0.12, or 8.3.0.16 or later for respective branches as specified in the Aruba security 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:>= 2.2.0.0, < 2.2.0.6
ArubaosOperating system
Affected:>= 8.3.0.0, < 8.3.0.16>= 8.5.0.0, < 8.5.0.12>= 8.6.0.0, < 8.6.0.6>= 8.7.0.0, < 8.7.1.4
Scalance W1750d FirmwareOperating system
Affected:all versions

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 product type
    Determine if the device is running Aruba SD-WAN, ArubaOS, or Siemens Scalance W1750d. Check the system firmware or management interface for the product name.
    Affected if The product is Aruba SD-WAN, ArubaOS, or Siemens Scalance W1750d
  2. Check Aruba SD-WAN version
    Access the SD-WAN management interface or use CLI command 'show version' to retrieve the installed software version.
    Affected if Version is >= 2.2.0.0 and < 2.2.0.6
  3. Check ArubaOS version
    Access the device CLI or web interface and run 'show version' or check the system information page to determine the ArubaOS version.
    Affected if Version falls within any of these ranges: >= 8.3.0.0 and < 8.3.0.16, OR >= 8.5.0.0 and < 8.5.0.12, OR >= 8.6.0.0 and < 8.6.0.6, OR >= 8.7.0.0 and < 8.7.1.4
  4. Check Siemens Scalance W1750d firmware version
    Access the device web interface or CLI and check the firmware version information.
    Affected if Any version of Siemens Scalance W1750d firmware is installed

The environment is affected if the device runs Aruba SD-WAN version 2.2.0.0 to 2.2.0.5, ArubaOS versions 8.3.0.0-8.3.0.15, 8.5.0.0-8.5.0.11, 8.6.0.0-8.6.0.5, or 8.7.0.0-8.7.1.3, or any version of Siemens Scalance W1750d firmware.

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.6 / 8.3.0.16 / 8.5.0.12 or later
Fixed in 2.2.0.68.3.0.168.5.0.12
Interim mitigation

Apply vendor-released patches for affected versions: upgrade to 8.6.0.4-2.2.0.6 or later for the 8.6.x branch; upgrade to 8.7.1.4, 8.6.0.7, 8.5.0.12, or 8.3.0.16 or later for respective branches as specified in the Aruba security advisory.

Recommended fix High confidence

SD-WAN: 2.2.0.6; ArubaOS 8.3.x: 8.3.0.16; ArubaOS 8.5.x: 8.5.0.12; ArubaOS 8.6.x: 8.6.0.7; ArubaOS 8.7.x: 8.7.1.4; Scalance W1750d: Contact vendor

  1. Identify the specific product and version in use (SD-WAN, ArubaOS, or Scalance W1750d)
  2. For SD-WAN: Upgrade to version 2.2.0.6 or later
  3. For ArubaOS 8.3.x: Upgrade to version 8.3.0.16 or later
  4. For ArubaOS 8.5.x: Upgrade to version 8.5.0.12 or later
  5. For ArubaOS 8.6.x: Upgrade to version 8.6.0.7 or later
  6. For ArubaOS 8.7.x: Upgrade to version 8.7.1.4 or later
  7. For Scalance W1750d: Contact vendor for patch availability, as no fixed version is specified in the advisory
  8. After upgrade, verify the system is functioning correctly and the vulnerability is resolved
Caveat Review Aruba release notes for any behavioral changes or configuration requirements when upgrading between major version branches

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

Fix this in Sd Wan Scoped from the published advisory
  • Consultation2.0 h
  • Implementation3.0 h
  • Testing4.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,900
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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