dbcve.org
Sd WanApplication · Arubanetworks

CVE-2022-37901

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 · high confidence

Authenticated command injection vulnerability in ArubaOS CLI allows attackers with valid credentials to execute arbitrary commands with privileged (root) access to the underlying operating system.

MitigationApply available ArubaOS security patches; until patched, restrict CLI access to trusted users only and implement network segmentation to limit exposure.

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
    Run 'show version' or 'show system information' in the CLI. For SD-WAN, use 'show version' from the controller CLI.
    Affected if The version falls within any of these ranges: ArubaOS 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, or 10.3.0.0. SD-WAN versions 8.7.0.0-2.3.0.0 through 8.7.0.0-2.3.0.6 are also affected.
  2. Confirm the product type is vulnerable
    Identify whether the device runs ArubaOS or Aruba SD-WAN using 'show product-name' or 'show system info'.
    Affected if The device is ArubaOS or SD-WAN and the version matches the affected ranges listed above.
  3. Verify CLI access is enabled
    Check if the CLI management interface is accessible and enabled. Review 'show ip ssh' or 'show management-interface' to confirm SSH or console CLI access is active.
    Affected if CLI access (SSH, console, or telnet) is enabled and reachable from any network where untrusted users exist.
  4. Audit CLI user accounts
    Use 'show user-database' or 'show local-userdb' to list all configured CLI accounts. Check for unauthorized or unexpected accounts.
    Affected if There are unexpected CLI accounts, or the existing accounts may have been compromised by an attacker who exploited this vulnerability.
  5. Inspect for suspicious command history or cron jobs
    Review command history if accessible, and check for unexpected scheduled tasks using 'show cron' or similar commands. Look for unfamiliar scripts or commands in /var directory if you have root access.
    Affected if Unknown commands appear in history or unexpected cron jobs/scripts exist on the system.

A user is affected if the device runs ArubaOS or SD-WAN within the version ranges listed and has CLI access enabled, as the vulnerability allows authenticated attackers to gain root command execution.

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 available ArubaOS security patches; until patched, restrict CLI access to trusted users only and implement network segmentation to limit exposure.

Recommended fix High confidence

ArubaOS: 6.5.4.23, 8.6.0.18, 8.7.1.10, or >8.9.0.3 (latest stable); SD-WAN: 8.7.0.0-2.3.0.7 or later

  1. 1. Identify the current ArubaOS or SD-WAN version running on the affected device using 'show version' in the CLI
  2. 2. Determine which version branch your current installation falls into (6.5.x, 8.4.x, 8.7.x, or 8.8.x/8.9.x)
  3. 3. For ArubaOS 6.5.4.x: upgrade to version 6.5.4.23 or later
  4. 4. For ArubaOS 8.4.x/8.5.x: upgrade to version 8.6.0.18 or later
  5. 5. For ArubaOS 8.7.x: upgrade to version 8.7.1.10 or later
  6. 6. For ArubaOS 8.8.x/8.9.x: upgrade to a version higher than 8.9.0.3 (check Aruba support for latest stable release)
  7. 7. For SD-WAN: upgrade to version 8.7.0.0-2.3.0.7 or later
  8. 8. After upgrade, verify the new version is running with 'show version'
Caveat Major version upgrades may introduce behavioral changes; review Aruba release notes for migration considerations 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
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA3.0 h
21.0 hours of engineering $3,780
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,048.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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