dbcve.org
Sd WanApplication · Arubanetworks

CVE-2022-37905

HIGH · 8.8 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 →
94/100
Remediation priority · Urgent
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
Vulnerabilities in ArubaOS running on 7xxx series controllers exist that allows an attacker to execute arbitrary code during the boot sequence. Successful exploitation could allow an attacker to achieve permanent modification of 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

Arbitrary code execution vulnerability in ArubaOS on 7xxx series controllers that occurs during the device boot sequence, enabling an attacker to achieve permanent modification of the underlying operating system.

MitigationApply vendor-provided firmware updates from Aruba Networks to address the boot sequence vulnerability; coordinate a planned maintenance window for deployment and verify the update does not introduce regressions.

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

CVSS:3.1/AV:N/AC:L/PR:L/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 device model
    Access the controller CLI and run 'show version' or 'show inventory' to confirm the hardware model is a 7xxx series controller
    Affected if The device is an Aruba 7xxx series controller running the affected ArubaOS versions
  2. Determine the installed ArubaOS version
    Run 'show version' in the controller CLI or check via the web UI under Dashboard > Controller > 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, or exactly 10.3.0.0
  3. Check SD-WAN version if applicable
    If the device runs Aruba SD-WAN software, run 'show sd-wan version' or check the SD-WAN dashboard for the software version
    Affected if SD-WAN version is >=8.7.0.0-2.3.0.0 and <8.7.0.0-2.3.0.6
  4. Verify boot integrity
    Compare the current boot image hash or checksum against the officially released Aruba boot image for your version. Run 'show boot' to list active boot partitions and verify no unauthorized custom boot images are present
    Affected if The boot image has been modified or a custom boot sequence is active that was not applied through official Aruba firmware updates
  5. Confirm the device is reachable over management interfaces
    Verify you have CLI or web UI access to perform the version checks above
    Affected if Unable to retrieve version information - the device may be compromised or inaccessible

The environment is affected if the device is an Aruba 7xxx series controller running ArubaOS or SD-WAN versions that match the affected ranges listed above.

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 vendor-provided firmware updates from Aruba Networks to address the boot sequence vulnerability; coordinate a planned maintenance window for deployment and verify the update does not introduce regressions.

Recommended fix High confidence

ArubaOS: 6.5.4.22+ (6.5.x branch), 8.6.0.17+ (8.4-8.5.x branch), 8.7.1.9+ (8.7.x branch), 8.10.0.0+ (8.8-8.9.x branch) | SD-WAN: 8.7.0.0-2.3.0.6+

  1. 1. Identify the exact current ArubaOS or SD-WAN version running on the controller by checking the device management interface or using 'show version' command
  2. 2. Determine which version branch your current release belongs to (6.5.x, 8.4.x-8.5.x, 8.7.x, or 8.8.x-8.9.x)
  3. 3. For ArubaOS 6.5.x: Upgrade to version 6.5.4.22 or later
  4. 4. For ArubaOS 8.4.x-8.5.x: Upgrade to version 8.6.0.17 or later
  5. 5. For ArubaOS 8.7.x: Upgrade to version 8.7.1.9 or later
  6. 6. For ArubaOS 8.8.x-8.9.x: Upgrade to version 8.10.0.0 or later (or the latest stable 8.10.x release)
  7. 7. For SD-WAN (Aruba VSX): Upgrade to version 8.7.0.0-2.3.0.6 or later
  8. 8. Before upgrading, review Aruba's release notes for any migration requirements and backup the current configuration
Caveat Review Aruba upgrade guide for controller reboot requirements and ensure compatibility with any connected APs or mobility switches before upgrading

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
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA4.0 h
22.0 hours of engineering $3,860
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,176.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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