CVE-2022-37904
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 · uneditedVulnerabilities 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 · moderate confidenceVulnerability in ArubaOS on 7xxx series controllers allows authenticated or unauthenticated attackers (exact access level unclear from description) to execute arbitrary code during the boot sequence. This enables persistent compromise of the operating system through permanent modification, likely via firmware tampering or secure boot bypass.
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>= 8.7.0.0-2.3.0.0, < 8.7.0.0-2.3.0.6>= 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.03= 10.3.0.0CVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Determine the ArubaOS versionAccess the controller CLI and run 'show version' or 'show boot', or check via the WebUI under Diagnostics or System InformationAffected if The version output matches any of the affected 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 8.9.0.3, or exactly 10.3.0.0; for SD-WAN: 8.7.0.0-2.3.0.0 to 8.7.0.0-2.3.0.5
-
Identify the hardware modelRun 'show version' or 'show controller-info' to retrieve the hardware model numberAffected if The model is a 7xxx series controller (e.g., 7005, 7008, 7010, 7024, 7030, 7040) or an SD-WAN device running the affected versions
-
Verify the boot image integrityRun 'show boot' or 'show flash' to list installed boot images and their checksums; compare against known-good values from Aruba support if availableAffected if Boot images show unexpected modifications, multiple unauthorized images, or checksum mismatches
-
Check for unauthorized firmware in flash storageRun 'show flash' or access the controller file system via CLI with appropriate privileges to list all firmware filesAffected if Firmware files exist that were not explicitly uploaded by your administration team, or unknown boot entries are present
You are affected if your controller runs a 7xxx series model or SD-WAN device with ArubaOS version matching the affected ranges listed above, or if boot/firmware integrity checks reveal unexpected modifications.
Generated from the published advisory. Verify against your own configuration.
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 · scoped6.5.4.228.6.0.178.7.0.0-2.3.0.6
Apply vendor-supplied ArubaOS firmware patch for 7xxx series controllers; verify system integrity post-patch and review secure boot configuration to ensure chain-of-trust validation.
ArubaOS: 6.5.4.22+, 8.6.0.17+, 8.7.1.9+, or 8.10.0.0+ (depending on branch); Sd Wan: 8.7.0.0-2.3.0.6+
- 1. Identify the current ArubaOS version running on the controller by accessing the controller's CLI and running 'show version' or via the WebUI dashboard.
- 2. Determine which version branch your current installation belongs to (6.5.x, 8.4.x-8.5.x, 8.6.x, 8.7.x, or 8.8.x-8.9.x).
- 3. For Sd Wan installations: Upgrade to version 8.7.0.0-2.3.0.6 or later.
- 4. For ArubaOS controllers on branch 6.5.x: Upgrade to version 6.5.4.22 or later.
- 5. For ArubaOS controllers on branch 8.4.x-8.5.x: Upgrade to version 8.6.0.17 or later.
- 6. For ArubaOS controllers on branch 8.7.x: Upgrade to version 8.7.1.9 or later.
- 7. For ArubaOS controllers on branch 8.8.x-8.9.x: Upgrade to version 8.10.0.0 or later (a version greater than 8.9.03).
- 8. Before upgrading, back up the controller configuration using 'backup flash' or via the WebUI.
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation8.0 h
- Testing12.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $7,616.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-37904 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2022-37904 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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