CVE-2021-37718
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 · uneditedA 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 confidenceThis is a remote command execution vulnerability in Aruba SD-WAN Software, Gateways, and ArubaOS. The vulnerability allows unauthenticated attackers to execute arbitrary commands on affected devices. Successful exploitation could give attackers full control over the SD-WAN infrastructure and connected networks.
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>= 2.2.0.0, < 2.2.0.6>= 8.3.0.0, < 8.3.0.16>= 8.5.0.0, < 8.5.0.12>= 8.6.0.0, < 8.6.0.7>= 8.7.0.0, < 8.7.1.4all versionsCVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Identify the Aruba product typeDetermine if the device is running Aruba SD-WAN Software, ArubaOS on controllers/gateways, or Siemens Scalance W1750d. Check the product model and software type via the device CLI or management interface.Affected if The device is any of these three product types: Aruba SD-WAN, ArubaOS (controllers/gateways), or Siemens Scalance W1750d firmware.
-
Check Aruba SD-WAN versionRun 'show version' or access the SD-WAN management GUI to locate the software version number. Compare it against the affected range: >= 2.2.0.0 and < 2.2.0.6.Affected if The installed SD-WAN software version is 2.2.0.0 through 2.2.0.5.x.
-
Check ArubaOS versionExecute 'show version' on the ArubaOS device CLI or check the controller GUI for the OS version. Compare against affected ranges: 8.3.0.0-8.3.0.15, 8.5.0.0-8.5.0.11, 8.6.0.0-8.6.0.6, and 8.7.0.0-8.7.1.3.Affected if The installed ArubaOS version falls within any of these four vulnerable ranges.
-
Check Siemens Scalance W1750d firmwareAccess the Scalance W1750d web interface or CLI and retrieve the firmware version information.Affected if Any version of Siemens Scalance W1750d firmware is running, as all versions are affected.
-
Assess network exposure of management interfaceReview firewall rules and access lists to determine if the device management interface (HTTP/HTTPS/SSH) is reachable from untrusted networks or the internet.Affected if The management interface is exposed to untrusted networks, enabling unauthenticated attackers to reach the vulnerable service.
Your environment is affected if you are running any of the specified product types (Aruba SD-WAN, ArubaOS, or Scalance W1750d) with a version number within the affected ranges and the management interface is network-accessible to potential attackers.
Generated from the published advisory. Verify against your own configuration.
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 · scoped2.2.0.68.3.0.168.5.0.12
Apply the vendor-released patches by upgrading to ArubaOS versions 8.6.0.4-2.2.0.6, 8.7.1.4, 8.6.0.7, 8.5.0.12, 8.3.0.16 or later, and ensure SD-WAN software is updated to the fixed release versions.
Aruba 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+
- Identify the specific Aruba product and version currently installed (SD-WAN or ArubaOS)
- For Aruba SD-WAN: Upgrade to version 2.2.0.6 or later
- For ArubaOS 8.3.x: Upgrade to version 8.3.0.16 or later
- For ArubaOS 8.5.x: Upgrade to version 8.5.0.12 or later
- For ArubaOS 8.6.x: Upgrade to version 8.6.0.7 or later
- For ArubaOS 8.7.x: Upgrade to version 8.7.1.4 or later
- For Scalance W1750d: Contact Siemens for specific firmware patch availability
- After upgrade, verify the new version is running and confirm the vulnerability is resolved
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,176.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2021-37718 — 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 sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2021-37718 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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