dbcve.org
Aos CxOperating system · Arubanetworks

CVE-2022-23683

HIGH · 7.2 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 →
78/100
Remediation priority · High
Remotely reachable 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
Authenticated command injection vulnerabilities exist in the AOS-CX Network Analytics Engine via NAE scripts. Successful exploitation of these vulnerabilities result in the ability to execute arbitrary commands as a privileged user on the underlying operating system, leading to a complete compromise of the switch running AOS-CX in ArubaOS-CX Switches version(s): AOS-CX 10.10.xxxx: 10.10.0002 and below, AOS-CX 10.09.xxxx: 10.09.1030 and below, AOS-CX 10.08.xxxx: 10.08.1070 and below, AOS-CX 10.06.xxxx: 10.06.0210 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

Authenticated command injection vulnerabilities exist in the AOS-CX Network Analytics Engine through NAE scripts. An authenticated attacker can inject arbitrary commands that execute with elevated privileges on the underlying operating system, achieving full system compromise of the ArubaOS-CX switch.

MitigationApply Aruba's released firmware upgrades for the specific AOS-CX version branches (10.10, 10.09, 10.08, 10.06) to address the command injection vulnerabilities. Prioritize upgrading switches running affected versions to their respective patched 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.0220>= 10.08.0000, < 10.08.1080>= 10.09.0000, < 10.09.1040>= 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
High
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:H/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 installed AOS-CX firmware version
    Run 'show version' on the switch CLI to retrieve the current AOS-CX software version
    Affected if The installed version falls within any of these ranges: 10.06.0000-10.06.0219, 10.08.0000-10.08.1079, 10.09.0000-10.09.1039, or 10.10.0000-10.10.0999
  2. Verify Network Analytics Engine status
    Run 'show nae' or check NAE configuration via 'show running-config | include nae' to determine if NAE scripts are enabled
    Affected if NAE is enabled and the firmware version is in an affected range listed above
  3. Review configured NAE scripts
    List all NAE scripts with 'show nae script' and inspect their configurations for any suspicious command invocations or unintended parameters
    Affected if Custom or unexpected NAE scripts exist in an environment running an affected version
  4. Check for unexpected processes or command execution
    Run 'show processes' or 'show tech' to identify any unusual processes that may indicate command injection activity
    Affected if Unexpected processes are running that were not initiated by an administrator

The environment is likely affected if the switch runs an AOS-CX version within the affected ranges and has NAE scripts enabled or configured.

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

Apply Aruba's released firmware upgrades for the specific AOS-CX version branches (10.10, 10.09, 10.08, 10.06) to address the command injection vulnerabilities. Prioritize upgrading switches running affected versions to their respective patched releases.

Recommended fix High confidence

AOS-CX 10.06.0220 or later (10.06.x branch); 10.08.1080 or later (10.08.x branch); 10.09.1040 or later (10.09.x branch); 10.10.1000 or later (10.10.x branch)

  1. 1. Identify the current AOS-CX version by running 'show version' on the switch CLI
  2. 2. Determine which version branch your device is running (10.06.x, 10.08.x, 10.09.x, or 10.10.x)
  3. 3. Download the appropriate fixed software version from the Aruba support portal: https://asp.arubanetworks.com/
  4. 4. Upload the firmware to the switch using 'copy tftp://<server>/<file> system:','5. Reboot the switch into the new firmware using 'reload' command
  5. 6. After reboot, verify the new version is installed using 'show version' and confirm it meets the minimum fixed version for your branch
Caveat Standard firmware upgrade - plan for brief downtime during reload; review 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
  • Consultation6.0 h
  • Implementation12.0 h
  • Testing6.0 h
  • Review / QA3.0 h
27.0 hours of engineering $4,800
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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