CVE-2021-37721
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.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 · high confidenceA remote arbitrary command execution vulnerability exists in Aruba SD-WAN Software and Gateways and ArubaOS. The vulnerability allows an unauthenticated attacker to execute arbitrary commands on affected devices due to insufficient input validation. This affects multiple version branches of ArubaOS prior to the patched releases (8.6.0.4-2.2.0.4, 8.7.1.4, 8.6.0.9, 8.5.0.13, 8.3.0.16, 6.5.4.20, 6.4.4.25).
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.4>= 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.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 product and versionAccess the device CLI or web interface and run 'show version' or check the firmware version in the web UI under Maintenance > Firmware or similarAffected if The device is Aruba SD-WAN, ArubaOS, or Siemens Scalance W1750d and the version falls within the affected ranges
-
Compare ArubaOS version against affected rangesCheck if ArubaOS version is: 6.4.4.0 to 6.4.4.24, 6.5.4.0 to 6.5.4.19, 8.3.0.0 to 8.3.0.15, 8.5.0.0 to 8.5.0.12, 8.6.0.0 to 8.6.0.8, or 8.7.0.0 to 8.7.1.3Affected if The installed ArubaOS version is within any of these unpatched ranges
-
Compare Aruba SD-WAN version against affected rangesCheck if SD-WAN software version is 2.2.0.0 to 2.2.0.3Affected if The installed SD-WAN version is within this unpatched range
-
Confirm Siemens Scalance W1750d firmwareVerify the device model is Siemens Scalance W1750dAffected if The device is a Siemens Scalance W1750d (all versions are affected)
-
Check for unauthenticated management interface exposureReview network configuration to determine if the web management interface (ports 80/443) is accessible from untrusted networksAffected if The management interface is exposed to the internet or untrusted networks without VPN/IP allow-listing
A user is affected if they run any ArubaOS version listed in the affected ranges, Aruba SD-WAN 2.2.0.0-2.2.0.3, or any Siemens Scalance W1750d firmware, with the management interface accessible to 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.46.4.4.256.5.4.20
Apply the available patches from Aruba for the specific version branch in use. Organizations should upgrade to a patched version and verify the fix through penetration testing or vulnerability scanning.
ArubaOS 6.4.4.25+, 6.5.4.20+, 8.3.0.16+, 8.5.0.13+, 8.6.0.9+, 8.7.1.4+ / SD-WAN 2.2.0.4+
- 1. Identify the exact Aruba product and current firmware version using 'show version' or the management interface.
- 2. For SD-WAN devices: Upgrade to version 2.2.0.4 or later (or 8.6.0.4-2.2.0.4 if using that release train).
- 3. For ArubaOS devices on 6.4.x branch: Upgrade to version 6.4.4.25 or later.
- 4. For ArubaOS devices on 6.5.x branch: Upgrade to version 6.5.4.20 or later.
- 5. For ArubaOS devices on 8.3.x branch: Upgrade to version 8.3.0.16 or later.
- 6. For ArubaOS devices on 8.5.x branch: Upgrade to version 8.5.0.13 or later.
- 7. For ArubaOS devices on 8.6.x branch: Upgrade to version 8.6.0.9 or later.
- 8. For ArubaOS devices on 8.7.x branch: Upgrade to version 8.7.1.4 or later.
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation3.0 h
- Implementation4.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,648.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2021-37721 — 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-37721 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