dbcve.org
Aos CxOperating system · Arubanetworks

CVE-2022-23682

HIGH · 7.8 CVSS v3.1 Published 2022-09-06
Fix available
A fix is available. Upgrade to 10.06.0220 / 10.08.1080 or later.
See remediation →
80/100
Remediation priority · High
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
Multiple vulnerabilities exist in the AOS-CX command line interface that could lead to authenticated command injection. A successful exploit could allow an attacker to execute arbitrary commands as root on the underlying operating system leading to complete switch compromise in ArubaOS-CX version(s): AOS-CX 10.09.xxxx: 10.09.1030 and below, AOS-CX 10.08.xxxx: 10.08.1030 and below, AOS-CX 10.06.xxxx: 10.06.0180 and below. Aruba has released upgrades for ArubaOS-CX 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

Multiple authenticated command injection vulnerabilities exist in the AOS-CX CLI that allow authenticated users to inject arbitrary OS commands, achieving root privilege escalation and full compromise of the switch. The vulnerability stems from insufficient input validation in CLI commands.

MitigationUpgrade ArubaOS-CX to version 10.09.1040 or later (for 10.09 branch), 10.08.1040 or later (for 10.08 branch), or 10.06.0181 or later (for 10.06 branch). Apply during a planned maintenance window following Aruba's upgrade procedures.

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.0220>= 10.08.0000, < 10.08.1080>= 10.09.0000, < 10.09.1040>= 10.10.0000, < 10.10.0002

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

CVSS:3.1/AV:L/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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify the ArubaOS-CX version
    Access the switch CLI and run the command: `show version` or `show system` to retrieve the installed firmware version
    Affected if The displayed version falls within these ranges: 10.06.0000 to 10.06.0219, 10.08.0000 to 10.08.1079, 10.09.0000 to 10.09.1039, or 10.10.0000 to 10.10.0001
  2. Confirm CLI access is available
    Verify that the CLI interface is accessible. This is typically enabled by default on AOS-CX switches. Check with: `show cli` or verify you can enter configuration mode with `configure terminal`
    Affected if CLI access is available to authenticated users - the vulnerability affects any authenticated user who can access the CLI
  3. Check for unauthorized privileged accounts
    Review user accounts with elevated privileges: `show user` and `show role` commands to see authenticated users and their assigned roles
    Affected if Unexpected accounts exist or unusual privilege escalation has occurred, indicating potential exploitation of this vulnerability

Your switch is affected if it runs ArubaOS-CX version 10.06.x below 10.06.0220, 10.08.x below 10.08.1080, 10.09.x below 10.09.1040, or 10.10.x below 10.10.0002 and has CLI access enabled for authenticated users.

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.0220 / 10.08.1080 / 10.09.1040 or later
Fixed in 10.06.022010.08.108010.09.1040
Interim mitigation

Upgrade ArubaOS-CX to version 10.09.1040 or later (for 10.09 branch), 10.08.1040 or later (for 10.08 branch), or 10.06.0181 or later (for 10.06 branch). Apply during a planned maintenance window following Aruba's upgrade procedures.

Recommended fix High confidence

Upgrade to 10.06.0220 or later for 10.06 branch; 10.08.1080 or later for 10.08 branch; 10.09.1040 or later for 10.09 branch; 10.10.0002 or later for 10.10 branch

  1. 1. Identify the current ArubaOS-CX version running on the switch using 'show version' command
  2. 2. Determine which version branch (10.06, 10.08, 10.09, or 10.10) the current installation belongs to
  3. 3. Download the appropriate fixed firmware from the Aruba support portal at https://asp.arubanetworks.com/
  4. 4. Upload the firmware to the switch via TFTP, FTP, or USB based on the switch model
  5. 5. Execute 'install-software <filename>' to install the new firmware image
  6. 6. After installation completes, reboot the switch using 'reload' command
  7. 7. Verify the new version is running with 'show version' and confirm it meets the minimum fixed version for your branch
Caveat Review Aruba release notes for migration path - some major version jumps may require intermediate upgrades; ensure proper downtime window as reload will cause brief network interruption

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
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA2.0 h
18.0 hours of engineering $3,200
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,120.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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