dbcve.org
Sd WanApplication · Arubanetworks

CVE-2022-37910

MEDIUM · 6.5 CVSS v3.1 Published 2022-12-12
Fix available
A fix is available. Upgrade to 6.5.4.22 / 8.6.0.17 or later.
See remediation →
71/100
Remediation priority · Elevated
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 buffer overflow vulnerability exists in the ArubaOS command line interface. Successful exploitation of this vulnerability results in a denial of service on the affected 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

A buffer overflow vulnerability in the ArubaOS command line interface allows authenticated attackers to trigger a denial of service condition by overflowing a buffer through specially crafted CLI input.

MitigationApply the Aruba OS firmware update provided by HPE Aruba to address this vulnerability. Restrict CLI access to trusted personnel only.

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.6
ArubaosOperating system
Affected:>= 6.5.4.0, < 6.5.4.22>= 8.4.0.0, < 8.6.0.17>= 8.7.0.0, < 8.7.1.9>= 8.8.0.0, < 10.3.0.1

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
Low
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
None
Availability
High

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/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. Determine ArubaOS version
    Access the device CLI and run 'show version' or access web UI and check the device dashboard for OS version information
    Affected if The displayed version falls within any of these ranges: 6.5.4.0 to 6.5.4.21, 8.4.0.0 to 8.6.0.16, 8.7.0.0 to 8.7.1.8, 8.8.0.0 to 10.3.0.0, or 8.7.0.0-2.3.0.0 to 8.7.0.0-2.3.0.5 for SD-WAN
  2. Identify product type
    Confirm whether the device is running ArubaOS or Aruba SD-WAN by checking the model number in 'show version' output or device labels
    Affected if Device is an Aruba SD-WAN or ArubaOS device and version falls within the affected ranges listed above
  3. Verify CLI access is enabled
    Check device configuration for CLI access settings using 'show running-config | include cli' or review access control lists that permit CLI access via console, SSH, or telnet
    Affected if CLI interface is accessible via any protocol (SSH, telnet, console) and the device version is in the affected list - the vulnerability is exploitable through authenticated CLI sessions

The environment is affected if the installed ArubaOS or SD-WAN version matches any of the specified vulnerable version ranges AND CLI access is enabled, allowing authenticated attackers to overflow the buffer through crafted CLI commands.

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.22 / 8.6.0.17 / 8.7.0.0-2.3.0.6 or later
Fixed in 6.5.4.228.6.0.178.7.0.0-2.3.0.6
Interim mitigation

Apply the Aruba OS firmware update provided by HPE Aruba to address this vulnerability. Restrict CLI access to trusted personnel only.

Recommended fix High confidence

ArubaOS Sd Wan: 8.7.0.0-2.3.0.6+ | ArubaOS 6.5.x: 6.5.4.22+ | ArubaOS 8.4.x: 8.6.0.17+ | ArubaOS 8.7.x: 8.7.1.9+ | ArubaOS 8.8.x/10.x: 10.3.0.1+

  1. 1. Identify the specific ArubaOS product line and current version running on the device using 'show version' command
  2. 2. For ArubaOS (Sd Wan) devices: Upgrade to version 8.7.0.0-2.3.0.6 or later
  3. 3. For ArubaOS devices on 6.5.x branch: Upgrade to version 6.5.4.22 or later
  4. 4. For ArubaOS devices on 8.4.x branch: Upgrade to version 8.6.0.17 or later
  5. 5. For ArubaOS devices on 8.7.x branch: Upgrade to version 8.7.1.9 or later
  6. 6. For ArubaOS devices on 8.8.x branch or 10.x branch: Upgrade to version 10.3.0.1 or later
  7. 7. After upgrade, verify the new version is installed using 'show version'
  8. 8. Test CLI functionality to confirm the system is operational
Caveat Review Aruba upgrade documentation for specific version migration paths; some upgrades may require intermediate steps for major version jumps

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

Fix this in Sd Wan Scoped from the published advisory
  • Consultation4.0 h
  • Implementation2.0 h
  • Testing4.0 h
  • Review / QA2.0 h
12.0 hours of engineering $2,120
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,392.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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