dbcve.org
5406r FirmwareOperating system · Arubanetworks

CVE-2022-23677

HIGH · 8.1 CVSS v3.1 Published 2022-05-10
Fix available
A fix is available. Upgrade to 16.02.0034 / 16.04.0024 or later.
See remediation →
90/100
Remediation priority · Urgent
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 remote execution of arbitrary code vulnerability was discovered in ArubaOS-Switch Devices version(s): ArubaOS-Switch 15.xx.xxxx: All versions; ArubaOS-Switch 16.01.xxxx: All versions; ArubaOS-Switch 16.02.xxxx: K.16.02.0033 and below; ArubaOS-Switch 16.03.xxxx: All versions; ArubaOS-Switch 16.04.xxxx: All versions; ArubaOS-Switch 16.05.xxxx: All versions; ArubaOS-Switch 16.06.xxxx: All versions; ArubaOS-Switch 16.07.xxxx: All versions; ArubaOS-Switch 16.08.xxxx: KB/WB/WC/YA/YB/YC.16.08.0024 and below; ArubaOS-Switch 16.09.xxxx: KB/WB/WC/YA/YB/YC.16.09.0019 and below; ArubaOS-Switch 16.10.xxxx: KB/WB/WC/YA/YB/YC.16.10.0019 and below; ArubaOS-Switch 16.11.xxxx: KB/WB/WC/YA/YB/YC.16.11.0003 and below. Aruba has released upgrades for ArubaOS-Switch Devices that address these security vulnerabilities.

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

A remote code execution vulnerability exists in multiple versions of ArubaOS-Switch Devices. The vulnerability allows remote attackers to execute arbitrary code on affected switches, potentially giving them full control over the device and the ability to move laterally within the network.

MitigationUpgrade ArubaOS-Switch to a version beyond the specified patched versions for each branch (K.16.02.0034 and above for 16.02.x, .16.08.0025 and above for 16.08.x variants, etc.) following Aruba's upgrade documentation and release notes.

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
5406r FirmwareOperating system
Affected:>= 15.00.0, <= 15.16.0023>= 16.01.0, < 16.02.0034>= 16.03.0, < 16.04.0024>= 16.05.0, < 16.08.0025>= 16.09.0, < 16.09.0020>= 16.10.0, < 16.10.0020>= 16.11.0, < 16.11.0004
2920 FirmwareOperating system
Affected:>= 15.00.0, <= 15.16.0023>= 16.01.0, < 16.02.0034>= 16.03.0, <= 16.04.0024>= 16.05.0, < 16.08.0025>= 16.09.0, < 16.09.0020>= 16.10.0, < 16.10.0020>= 16.11.0, < 16.11.0004
2930f FirmwareOperating system
Affected:>= 15.00.0, <= 15.16.0023>= 16.01.0, < 16.02.0034>= 16.03.0, <= 16.04.0024>= 16.05.0, < 16.08.0025>= 16.09.0, <= 16.09.0020>= 16.10.0, <= 16.10.0020>= 16.11.0, <= 16.11.0004
2930m FirmwareOperating system
Affected:>= 15.00.0, <= 15.16.0023>= 16.01.0, < 16.02.0034>= 16.03.0, <= 16.04.0024>= 16.05.0, < 16.08.0025>= 16.09.0, < 16.09.0020>= 16.10.0, < 16.10.0020>= 16.11.0, < 16.11.0004
2530 FirmwareOperating system
Affected:>= 15.00.0, <= 15.16.0023>= 16.01.0, < 16.02.0034>= 16.03.0, <= 16.04.0024>= 16.05.0, < 16.08.0025>= 16.09.0, < 16.09.0020>= 16.10.0, < 16.10.0020>= 16.11.0, < 16.11.0004
2540 FirmwareOperating system
Affected:>= 15.00.0, <= 15.16.0023>= 16.01.0, < 16.02.0034>= 16.03.0, <= 16.04.0024>= 16.05.0, < 16.08.0025>= 16.09.0, < 16.09.0020>= 16.10.0, < 16.10.0020>= 16.11.0, < 16.11.0004
5412r FirmwareOperating system
Affected:>= 15.00.0, <= 15.16.0023>= 16.01.0, < 16.02.0034>= 16.03.0, <= 16.04.0024>= 16.05.0, < 16.08.0025>= 16.09.0, < 16.09.0020>= 16.10.0, < 16.10.0020>= 16.11.0, < 16.11.0004
2615 FirmwareOperating system
Affected:>= 15.00.0, <= 15.16.0023>= 16.01.0, < 16.02.0034>= 16.03.0, <= 16.04.0024>= 16.05.0, < 16.08.0025>= 16.09.0, < 16.09.0020>= 16.10.0, < 16.10.0020>= 16.11.0, < 16.11.0004

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

CVSS:3.1/AV:N/AC:H/PR:N/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 switch model
    Run 'show version' on the Aruba switch CLI to display the device model name
    Affected if The model is one of: 5406r, 2920, 2930f, 2930m, 2530, 2540, 5412r, or 2615
  2. Retrieve the installed firmware version
    Run 'show version' and locate the firmware version string (typically shown as something like 15.xx.xxxx or 16.xx.xxxx)
    Affected if The device is running any firmware version within the ranges listed in the CVE
  3. Compare version against the affected ranges
    Match your installed firmware version against the version ranges in the CVE for your specific model. For example, version 15.16.0023 is vulnerable, as is 16.10.0019, but 16.11.0004 is not.
    Affected if The installed version falls within any of the vulnerable ranges (for 15.x, any version from 15.00.0 through 15.16.0023; for 16.x, check the specific sub-range limits listed in the CVE)

The device is affected if it is one of the listed models and runs a firmware version that matches the vulnerable ranges in the CVE.

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 16.02.0034 / 16.04.0024 / 16.08.0025 or later
Fixed in 16.02.003416.04.002416.08.0025
Interim mitigation

Upgrade ArubaOS-Switch to a version beyond the specified patched versions for each branch (K.16.02.0034 and above for 16.02.x, .16.08.0025 and above for 16.08.x variants, etc.) following Aruba's upgrade documentation and release notes.

Recommended fix High confidence

ArubaOS-Switch firmware K.16.02.0034+ (16.02 branch), K.16.04.0024+ (16.04 branch), KB/WB/WC/YA/YB/YC.16.08.0025+ (16.08 branch), KB/WB/WC/YA/YB/YC.16.09.0020+ (16.09 branch), KB/WB/WC/YA/YB/YC.16.10.0020+ (16.10 branch), or KB/WB/WC/YA/YB/YC.16.11.0004+ (16.11 branch)

  1. 1. Identify the exact model of ArubaOS-Switch device (5406r, 2920, 2930f, 2930m, 2530, 2540, 5412r, or 2615)
  2. 2. Determine the current firmware version by accessing the switch CLI (show version) or web interface
  3. 3. Consult the Aruba Networks support portal at www.arubanetworks.com for the appropriate firmware version for your specific switch model
  4. 4. Download the fixed firmware version: For 16.02.x branch use K.16.02.0034 or later; For 16.04.x branch use K.16.04.0024 or later; For 16.08.x branch use KB/WB/WC/YA/YB/YC.16.08.0025 or later; For 16.09.x branch use KB/WB/WC/YA/YB/YC.16.09.0020 or later; For 16.10.x branch use KB/WB/WC/YA/YB/YC.16.10.0020 or later; For 16.11.x branch use KB/WB/WC/YA/YB/YC.16.11.0004 or later
  5. 5. Upload the firmware to the switch via TFTP, FTP, or the web interface
  6. 6. Reboot the switch to apply the new firmware
  7. 7. Verify the upgrade was successful by running 'show version' and confirming the fixed version number
Caveat Firmware upgrades may cause temporary network disruption; ensure you have a maintenance window and backup configuration before upgrading

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

Fix this in 5406r Firmware Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA2.0 h
20.0 hours of engineering $3,500
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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