dbcve.org
5406r FirmwareOperating system · Arubanetworks

CVE-2022-23676

CRITICAL · 9.8 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 →
100/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 · moderate confidence

A remote code execution vulnerability exists in multiple versions of ArubaOS-Switch. The critical CVSS score of 9.8 indicates the flaw is exploitable remotely without authentication, allowing attackers to execute arbitrary code on affected switch devices.

MitigationApply Aruba's released firmware upgrades for ArubaOS-Switch devices; specific patched versions vary by branch (e.g., K.16.02.0034 or higher for 16.02.xxxx branch).

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
3810m 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

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
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/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
    Log into the switch CLI and run 'show system information' or check the device label/serial number to confirm the exact model (e.g., 5406r, 3810m, 2920, 2930f, 2930m, 2530, 2540, 5412r)
    Affected if The model is not one of the eight listed affected models (5406r, 3810m, 2920, 2930f, 2930m, 2530, 2540, 5412r)
  2. Determine the installed firmware version
    Run 'show version' or 'show flash' in the switch CLI to retrieve the current firmware version string (e.g., WC.15.16.0023, YA.16.10.0019)
    Affected if Unable to retrieve the firmware version from the device
  3. Compare version against affected ranges for 15.x branches
    If firmware starts with 15.x, check if the version falls within: >= 15.00.0 AND <= 15.16.0023. If yes, the device is affected.
    Affected if The installed version is 15.00.0 through 15.16.0023 inclusive
  4. Compare version against affected ranges for 16.01.x and 16.03.x branches
    For 16.01.x versions: affected if < 16.02.0034. For 16.03.x versions: affected if < 16.04.0024 (or <= 16.04.0024 for some models). Check the exact version string.
    Affected if The installed version is 16.01.x less than 16.02.0034, or 16.03.x less than (or equal to per model) 16.04.0024
  5. Compare version against affected ranges for 16.05.x through 16.11.x branches
    Check if version is in any of these ranges: 16.05.x < 16.08.0025, 16.09.x < 16.09.0020, 16.10.x < 16.10.0020, or 16.11.x < 16.11.0004
    Affected if The installed version falls within any of these vulnerable ranges
  6. Verify if management interface is network accessible
    Confirm whether the switch management IP/interface is reachable from untrusted networks (check VLAN configuration, ACLs, and management interface binding)
    Affected if The switch management interface is exposed to untrusted networks and the firmware version is within the affected ranges

The device is affected if it is one of the eight supported switch models (5406r, 3810m, 2920, 2930f, 2930m, 2530, 2540, 5412r) AND its firmware version falls within any of the vulnerable version ranges listed.

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

Apply Aruba's released firmware upgrades for ArubaOS-Switch devices; specific patched versions vary by branch (e.g., K.16.02.0034 or higher for 16.02.xxxx branch).

Recommended fix High confidence

Upgrade to the minimum fixed version for your branch: 16.02.0034, 16.08.0025, 16.09.0020, 16.10.0020, or 16.11.0004 (or later stable releases)

  1. 1. Identify the exact model and current firmware version of the ArubaOS-Switch device using the CLI command 'show version' or through the web interface.
  2. 2. Access the Aruba support portal at https://asp.arubanetworks.com/ to download the appropriate fixed firmware version for your device model.
  3. 3. For firmware branch 16.02.x: Upgrade to version K.16.02.0034 or later.
  4. 4. For firmware branch 16.08.x: Upgrade to version KB/WB/WC/YA/YB/YC.16.08.0025 or later.
  5. 5. For firmware branch 16.09.x: Upgrade to version KB/WB/WC/YA/YB/YC.16.09.0020 or later.
  6. 6. For firmware branch 16.10.x: Upgrade to version KB/WB/WC/YA/YB/YC.16.10.0020 or later.
  7. 7. For firmware branch 16.11.x: Upgrade to version KB/WB/WC/YA/YB/YC.16.11.0004 or later.
  8. 8. Upload the firmware to the switch using the CLI command 'copy tftp://<server>/<firmware-file> system:slot1' or via the web interface under Maintenance > Firmware Upload.
Caveat Review Aruba release notes for your specific model before upgrading; some hardware platforms may have specific compatibility considerations or feature changes in newer firmware branches

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 / 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-23676 — 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-23676 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