dbcve.org
Sd WanApplication · Arubanetworks

CVE-2022-37907

HIGH · 7.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 →
84/100
Remediation priority · High
Remotely reachable No privileges 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 vulnerability exists in the ArubaOS bootloader on 7xxx series controllers which can result in a denial of service (DoS) condition on an impacted system. A successful attacker can cause a system hang which can only be resolved via a power cycle of the impacted controller.

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 vulnerability exists in the ArubaOS bootloader on 7xxx series controllers that allows an attacker to cause a denial of service by hanging the system, which can only be recovered via power cycle. The bootloader is the first code executed at device startup, making this a low-level system compromise.

MitigationApply vendor-provided patches for ArubaOS when available; until then, restrict physical and network access to controller management interfaces to minimize attack surface.

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

CVSS:3.1/AV:N/AC:L/PR:N/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. Identify the device model
    Run 'show version' or 'show system info' on the controller CLI to confirm the hardware model
    Affected if Device is NOT a 7xxx series controller - this specific vulnerability only affects 7xxx series hardware
  2. Check the ArubaOS version
    Run 'show version' to display the currently installed ArubaOS version
    Affected if Version matches any of these ranges: 6.5.4.0-6.5.4.21, 8.4.0.0-8.6.0.16, 8.7.0.0-8.7.1.8, or 8.8.0.0-10.3.0.0
  3. Check bootloader accessibility
    Verify if bootloader console or management interface is reachable via console port or network management. Boot messages at device startup can be observed via console connection.
    Affected if Bootloader is accessible (via console or network) on an affected device version

Device is affected if it is a 7xxx series controller running an ArubaOS version within the vulnerable ranges listed above and the bootloader is accessible to an attacker.

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 patches for ArubaOS when available; until then, restrict physical and network access to controller management interfaces to minimize attack surface.

Recommended fix High confidence

ArubaOS: upgrade to 6.5.4.22 (for 6.5.4.x), 8.6.0.17 (for 8.4.x-8.5.x), 8.7.1.9 (for 8.7.x), or 10.3.0.1 (for 8.8.x+); Sd Wan: upgrade to 8.7.0.0-2.3.0.6

  1. 1. Identify the current ArubaOS version installed on the controller by checking the system information or running 'show version'
  2. 2. Based on the current version, determine the appropriate target fixed version from the upgrade path
  3. 3. Download the appropriate ArubaOS upgrade image from the official Aruba support portal (https://asp.arubanetworks.com)
  4. 4. Back up the current controller configuration using 'backup flash' or the WebUI
  5. 5. Upload the new firmware image to the controller via WebUI, CLI ('copy tftp://<server>/<image> flash:'), or SCP
  6. 6. Verify the image was uploaded successfully by checking the flash directory
  7. 7. Reboot the controller into the new image using 'reload' command or via WebUI
  8. 8. After the controller restarts, verify the new version is running with 'show version'
Caveat Major version upgrades (e.g., 8.6 to 10.3) may require configuration review; ensure compatibility with managed APs and downstream devices 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
  • Implementation6.0 h
  • Testing4.0 h
  • Review / QA2.0 h
16.0 hours of engineering $2,840
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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