dbcve.org
Aos CxOperating system · Arubanetworks

CVE-2022-23680

HIGH · 8.8 CVSS v3.1 Published 2022-09-06
Fix available
A fix is available. Upgrade to 10.06.0210 / 10.08.1070 or later.
See remediation →
95/100
Remediation priority · Urgent
Remotely reachable No privileges

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
AOS-CX lacks Anti-CSRF protections in place for state-changing operations. This can potentially be exploited by an attacker to execute commands in the context of another user in ArubaOS-CX Switches version(s): AOS-CX 10.10.xxxx: 10.10.0002 and below, AOS-CX 10.09.xxxx: 10.09.1020 and below, AOS-CX 10.08.xxxx: 10.08.1060 and below, AOS-CX 10.06.xxxx: 10.06.0200 and below. Aruba has released upgrades for ArubaOS-CX Switch Devices that address this security vulnerability.

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

AOS-CX web management interface lacks anti-CSRF tokens for state-changing operations, allowing attackers to craft malicious requests that execute in the context of an authenticated administrator's session.

MitigationUpgrade AOS-CX to version 10.10.0003 or later (10.09.1021+, 10.08.1061+, 10.06.0201+) as provided by Aruba's firmware releases.

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
Aos CxOperating system
Affected:>= 10.06.0000, < 10.06.0210>= 10.08.0000, < 10.08.1070>= 10.09.0000, < 10.09.1030>= 10.10.0000, < 10.10.1000

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
Required
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:R/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. Verify AOS-CX is deployed
    Run 'show version' or 'show system' on the switch CLI to confirm the device is running Aruba AOS-CX firmware
    Affected if The device is not an Aruba AOS-CX switch
  2. Identify the AOS-CX version
    Execute 'show version' and note the firmware version number displayed (for example, 10.08.1050)
    Affected if The displayed version falls within any of these ranges: 10.06.0000-10.06.0209, 10.08.0000-10.08.1069, 10.09.0000-10.09.1029, or 10.10.0000-10.10.0999
  3. Confirm web management interface is accessible
    Attempt to reach the switch web UI over HTTPS (typically port 443) from an authorized management network
    Affected if The web interface responds and accepts administrator authentication
  4. Inspect web requests for CSRF protection
    Log into the web management interface, open browser developer tools, and examine state-changing actions (such as creating a user, changing settings, or applying config) for the presence of a CSRF token or parameter in the HTTP request headers or body
    Affected if State-changing requests contain no CSRF token or anti-CSRF parameter

You are affected if the device runs AOS-CX firmware version 10.06.0000-10.06.0209, 10.08.0000-10.08.1069, 10.09.0000-10.09.1029, or 10.10.0000-10.10.0999 AND the web management interface is accessible and lacks CSRF tokens in state-changing operations.

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 10.06.0210 / 10.08.1070 / 10.09.1030 or later
Fixed in 10.06.021010.08.107010.09.1030
Interim mitigation

Upgrade AOS-CX to version 10.10.0003 or later (10.09.1021+, 10.08.1061+, 10.06.0201+) as provided by Aruba's firmware releases.

Recommended fix High confidence

Upgrade to AOS-CX 10.06.0210+ (for 10.06.x branch), 10.08.1070+ (for 10.08.x branch), 10.09.1030+ (for 10.09.x branch), or 10.10.1000+ (for 10.10.x branch)

  1. 1. Identify the currently installed AOS-CX version by running 'show version' on the switch CLI
  2. 2. Determine which version branch your current version belongs to (10.06.x, 10.08.x, 10.09.x, or 10.10.x)
  3. 3. For version 10.06.x: Upgrade to AOS-CX version 10.06.0210 or later
  4. 4. For version 10.08.x: Upgrade to AOS-CX version 10.08.1070 or later
  5. 5. For version 10.09.x: Upgrade to AOS-CX version 10.09.1030 or later
  6. 6. For version 10.10.x: Upgrade to AOS-CX version 10.10.1000 or later
  7. 7. Download the appropriate firmware from the Aruba support portal (https://asp.arubanetworks.com)
  8. 8. Upload the firmware to the switch using 'copy <source> system:']
Caveat Standard firmware upgrade risks apply - ensure proper backup of configuration and plan for brief downtime; review Aruba release notes for any configuration changes between versions

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

Fix this in Aos Cx Scoped from the published advisory
  • Consultation4.0 h
  • Implementation24.0 h
  • Testing12.0 h
  • Review / QA8.0 h
48.0 hours of engineering $8,360
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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