dbcve.org
ArubaosOperating system · Arubanetworks

CVE-2023-22766

HIGH · 7.2 CVSS v3.1 Published 2023-03-01
Fix available
A fix is available. Upgrade to after 10.3.1.0 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 ArubaOS 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 vulnerability in ArubaOS command line interface allows authenticated attackers to execute arbitrary commands as privileged users (root/admin) on the underlying operating system. The vulnerability stems from insufficient input sanitization in the CLI, enabling attackers to break out of intended command contexts and inject OS-level commands.

MitigationRestrict CLI access to trusted, least-privilege accounts only; apply vendor patches when available; implement network segmentation to limit exposure to untrusted users.

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:>= 8.6.0.0, <= 8.6.0.19>= 8.10.0.0, <= 8.10.0.4>= 10.3.0.0, <= 10.3.1.0
Sd WanApplication
Affected:>= 8.7.0.0-2.3.0.0, <= 8.7.0.0-2.3.0.8

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 ArubaOS version
    Access the CLI and run 'show version' or 'show system information' to display the firmware version
    Affected if Version falls within 8.6.0.0-8.6.0.19, 8.10.0.0-8.10.0.4, or 10.3.0.0-10.3.1.0 for ArubaOS; or 8.7.0.0-2.3.0.0 to 8.7.0.0-2.3.0.8 for SD-Wan
  2. Confirm CLI access is enabled
    Verify the command line interface is accessible via console, SSH, or telnet by attempting to log in with valid credentials
    Affected if CLI interface is exposed and accessible with any valid user account
  3. Audit existing CLI accounts
    Run 'show user-database' or 'show local-user' to list all configured CLI users and their privilege levels
    Affected if Multiple accounts exist beyond the minimum required, increasing the attack surface for authenticated command injection
  4. Review recent CLI command history
    Check CLI logs or audit trails for suspicious commands that may indicate exploitation attempts, such as unusual command chaining or shell escapes
    Affected if Commands contain unexpected characters (semicolons, pipes, backticks) or attempt to invoke system utilities outside normal operations

A system is affected if it runs a vulnerable ArubaOS or SD-Wan version AND has CLI access enabled with any authenticated user account.

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 a release after 10.3.1.0
Interim mitigation

Restrict CLI access to trusted, least-privilege accounts only; apply vendor patches when available; implement network segmentation to limit exposure to untrusted users.

Recommended fix Moderate confidence

ArubaOS 8.6.0.20+, 8.10.0.5+, 10.3.1.1+ | SD-WAN 8.7.0.0-2.3.0.9+

  1. 1. Identify the current ArubaOS or SD-WAN version by running 'show version' in the CLI
  2. 2. Based on your current version line, upgrade to a version beyond the affected range: For ArubaOS 8.6.x, upgrade to 8.6.0.20 or later; For ArubaOS 8.10.x, upgrade to 8.10.0.5 or later; For ArubaOS 10.3.x, upgrade to 10.3.1.1 or later; For SD-WAN 8.7.0.0-2.3.x, upgrade to 8.7.0.0-2.3.0.9 or later
  3. 3. Download the upgrade image from the Aruba support portal (https://asp.arubanetworks.com)
  4. 4. Upload the upgrade image to the controller using 'copy tftp://<server>/<image> flash:' or via WebUI
  5. 5. Validate the image checksum if provided by Aruba
  6. 6. Install the upgrade using 'upgrade-software' command
  7. 7. Reboot the device using 'reload' command
  8. 8. After reboot, verify the new version with 'show version' and confirm the vulnerability is remediated
Caveat Review Aruba release notes for your specific upgrade path for any configuration or compatibility changes; test 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
  • 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-2023-22766 — 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-22766 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