dbcve.org
ArubaosOperating system · Arubanetworks

CVE-2023-22788

HIGH · 8.8 CVSS v3.1 Published 2023-05-08
Fix available
A fix is available. Upgrade to 8.6.0.0 or later.
See remediation →
94/100
Remediation priority · Urgent
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
Multiple authenticated command injection vulnerabilities exist in the Aruba InstantOS and ArubaOS 10 command line interface. Successful exploitation of these vulnerabilities result in the ability to execute arbitrary commands as a privileged user on the underlying operating system.

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 in the Aruba InstantOS and ArubaOS CLI allow a logged-in attacker to execute arbitrary OS commands with elevated privileges. The vulnerabilities stem from improper input validation in CLI commands, enabling an authenticated user to break out of intended command boundaries and inject shell commands.

MitigationApply the vendor-provided firmware patches for Aruba InstantOS and ArubaOS 10. Restrict CLI access to trusted management networks and use least-privilege accounts to limit exposure.

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
ArubaosOperating system
Affected:>= 10.3.0.0, <= 10.3.1.0
InstantosOperating system
Affected:>= 6.4.0.0, <= 6.4.4.8-4.2.4.20>= 6.5.0.0, <= 6.5.4.23>= 8.4.0.0, < 8.6.0.0>= 8.6.0.0, <= 8.6.0.19>= 8.7.0.0, <= 8.9.0.0>= 8.10.0.0, <= 8.10.0.4

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

CVSS:3.1/AV:N/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 device OS and version
    Run the command 'show version' or 'show system info' in the CLI to obtain the installed ArubaOS or InstantOS version number
    Affected if The displayed version falls within any of the affected ranges: ArubaOS 10.3.0.0 to 10.3.1.0, or InstantOS 6.4.x, 6.5.x, 8.4.x to 8.10.x as listed in the CVE advisory
  2. Confirm CLI access is enabled
    Verify that the device CLI (command line interface) is accessible, typically via console, SSH, or telnet. Attempt to log in with any administrative account
    Affected if CLI access is available and an authenticated session can be established - the vulnerability requires an authenticated attacker to inject commands through the CLI
  3. Check for unexpected CLI command behavior
    If you have access to logs, review CLI audit logs or system logs for any anomalous commands that appear to break out of expected CLI command boundaries or execute shell metacharacters
    Affected if Logs show CLI commands containing shell operators (such as ;, |, &&, or backticks) that should not be present in normal CLI usage

You are affected if your device runs ArubaOS 10.3.0.0-10.3.1.0 or InstantOS within any of the listed version ranges AND the CLI interface is accessible to authenticated users, since the flaw allows an authenticated attacker to inject OS commands through the CLI.

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 8.6.0.0 or later
Fixed in 8.6.0.0
Interim mitigation

Apply the vendor-provided firmware patches for Aruba InstantOS and ArubaOS 10. Restrict CLI access to trusted management networks and use least-privilege accounts to limit exposure.

Recommended fix Moderate confidence

ArubaOS 10.3.2.0+ / InstantOS 6.4.4.9+ / 6.5.4.24+ / 8.6.0.20+

  1. 1. Identify the exact ArubaOS or InstantOS version currently installed via CLI: `show version` or `show inv`
  2. 2. Determine the appropriate upgrade path based on your current deployment model (ArubaOS or InstantOS)
  3. 3. Download the corresponding fixed firmware from the Aruba Support Portal (https://asp.arubanetworks.com)
  4. 4. For ArubaOS 10.x: Upgrade to version 10.3.2.0 or later which contains the security fixes
  5. 5. For InstantOS 6.4.x: Upgrade to version 6.4.4.9 or later
  6. 6. For InstantOS 6.5.x: Upgrade to version 6.5.4.24 or later
  7. 7. For InstantOS 8.4.x: Upgrade to version 8.6.0.0 or later
  8. 8. For InstantOS 8.6.x: Upgrade to version 8.6.0.20 or later
Caveat Review Aruba release notes for any configuration or feature changes between versions; test upgrade in non-production environment first

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

Fix this in Arubaos Scoped from the published advisory
  • Consultation4.0 h
  • Implementation12.0 h
  • Testing6.0 h
  • Review / QA3.0 h
25.0 hours of engineering $4,400
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,040.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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