dbcve.org
Sd WanApplication · Arubanetworks

CVE-2022-37902

HIGH · 7.2 CVSS v3.1 Published 2022-12-12
Fix available
A fix is available. Upgrade to 6.5.4.23 / 8.6.0.18 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
Authenticated command injection vulnerabilities exist in the ArubaOS command line interface. Successful exploitation of these vulnerabilities results in the ability to execute arbitrary commands as a privileged user on the underlying operating system.

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

Authenticated command injection vulnerabilities exist in the ArubaOS command line interface. An attacker with valid CLI credentials can inject and execute arbitrary operating system commands with elevated (privileged) user rights. This grants the attacker full control over the underlying system.

MitigationApply the relevant Aruba OS patch or upgrade to a fixed version. If immediate patching is not feasible, restrict CLI access to trusted management networks only and enforce strong authentication credentials.

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:>= 8.7.0.0-2.3.0.0, < 8.7.0.0-2.3.0.7
ArubaosOperating system
Affected:>= 6.5.4.0, < 6.5.4.23>= 8.4.0.0, < 8.6.0.18>= 8.7.0.0, < 8.7.1.10>= 8.8.0.0, <= 8.9.0.3= 10.3.0.0

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 installed ArubaOS version
    Access the CLI and run 'show version' or 'show system information' to display the current OS version
    Affected if The displayed version falls within any of these ranges: 6.5.4.0 to 6.5.4.22; 8.4.0.0 to 8.6.0.17; 8.7.0.0 to 8.7.1.9; 8.8.0.0 to 8.9.0.3; 10.3.0.0; or for SD-WAN: 8.7.0.0-2.3.0.0 to 8.7.0.0-2.3.0.6
  2. Verify CLI access is enabled
    Confirm that the command-line interface is accessible on the device (typically via console, SSH, or telnet on management ports)
    Affected if CLI access is enabled and reachable from your management network
  3. Confirm valid CLI credentials exist
    Review user accounts configured with CLI access privileges using 'show user-database' or similar CLI command
    Affected if There are user accounts with CLI login capability (the vulnerability requires valid credentials to exploit)

You are affected if your device runs an ArubaOS version matching any of the affected ranges listed above AND the CLI is accessible with valid user credentials.

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 6.5.4.23 / 8.6.0.18 / 8.7.0.0-2.3.0.7 or later
Fixed in 6.5.4.238.6.0.188.7.0.0-2.3.0.7
Interim mitigation

Apply the relevant Aruba OS patch or upgrade to a fixed version. If immediate patching is not feasible, restrict CLI access to trusted management networks only and enforce strong authentication credentials.

Recommended fix High confidence

ArubaOS: 6.5.4.23+, 8.6.0.18+, 8.7.1.10+, or 8.9.0.4+/8.10.x latest; SD-WAN: 8.7.0.0-2.3.0.7+

  1. 1. Identify the currently installed ArubaOS or SD-WAN version by running 'show version' in the CLI
  2. 2. Based on the current version, determine the minimum fixed version required: For 6.5.x, upgrade to 6.5.4.23 or later; For 8.4.x to 8.5.x, upgrade to 8.6.0.18 or later; For 8.7.x, upgrade to 8.7.1.10 or later; For 8.8.x to 8.9.x, upgrade to 8.9.0.4 or later (or the latest stable 8.10.x release)
  3. 3. Download the appropriate upgrade image from the Aruba support portal (https://asp.arubanetworks.com)
  4. 4. Back up the current configuration using 'backup flash' or 'write mem' commands
  5. 5. Upload the new firmware image to the controller using 'copy tftp://<server>/<image> flash:' or via WebUI
  6. 6. Verify the image integrity using 'verify image' command
  7. 7. Reboot the device into the new image using 'reload' command
  8. 8. After reboot, verify the new version is running with 'show version'
Caveat Review Aruba upgrade guidelines for controller-specific migration notes; ensure compatibility with existing network topology and dependent systems before upgrading

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

Fix this in Sd Wan Scoped from the published advisory
  • Consultation6.0 h
  • Implementation12.0 h
  • Testing10.0 h
  • Review / QA6.0 h
34.0 hours of engineering $5,940
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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