dbcve.org
ArubaosOperating system · Arubanetworks

CVE-2023-35973

HIGH · 7.2 CVSS v3.1 Published 2023-07-05
Fix available
A fix is available. Upgrade to 8.6.0.21 / 8.10.0.7 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 vulnerabilities in the ArubaOS command line interface allow an authenticated attacker to execute arbitrary commands as a privileged user on the underlying operating system. The vulnerability exists in the CLI parsing logic where user-supplied input is not properly sanitized before being passed to system shell commands.

MitigationApply vendor-supplied patches for ArubaOS. If no patch is available, restrict CLI access to trusted management networks and use role-based access controls to limit which authenticated users can access privileged command modes.

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:>= 6.5.4.0, < 8.6.0.21>= 8.7.0.0, < 8.10.0.7>= 8.11.0.0, < 8.11.1.1>= 10.4.0.0, < 10.4.0.2

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. Determine ArubaOS version
    Log into the device CLI and run 'show version' or access the web management interface to view the system information. Note the exact version number displayed.
    Affected if The installed version falls within one of these ranges: >= 6.5.4.0 and < 8.6.0.21; OR >= 8.7.0.0 and < 8.10.0.7; OR >= 8.11.0.0 and < 8.11.1.1; OR >= 10.4.0.0 and < 10.4.0.2
  2. Verify CLI access is enabled
    Confirm that the command line interface is accessible on the device. This can be done by attempting to access the device via console, SSH, or Telnet if those services are configured.
    Affected if The CLI interface is accessible and accepts authentication credentials.
  3. Identify management interface exposure
    Check the device configuration for enabled management interfaces (SSH, Telnet, console) and their binding addresses. Review the 'show ip interface' or similar command output to identify management plane exposure.
    Affected if The device has CLI access (SSH, console, or Telnet) exposed to untrusted networks or the internet.
  4. Check for privileged command access
    Review the user roles and privileges configured on the device. Determine whether standard or limited-authentication users can access privileged command modes (enable mode, privileged exec mode, or equivalent).
    Affected if Authenticated users with any privilege level can access CLI command modes that interact with system operations.

The environment is affected if the device runs an ArubaOS version within the specified vulnerable ranges AND the CLI interface is accessible to the attacker for authentication.

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.21 / 8.10.0.7 / 8.11.1.1 or later
Fixed in 8.6.0.218.10.0.78.11.1.1
Interim mitigation

Apply vendor-supplied patches for ArubaOS. If no patch is available, restrict CLI access to trusted management networks and use role-based access controls to limit which authenticated users can access privileged command modes.

Recommended fix High confidence

8.6.0.21, 8.10.0.7, 8.11.1.1, or 10.4.0.2 (depending on your current branch - choose the minimum fixed version in your release line)

  1. Review current ArubaOS version using 'show version' command in the CLI
  2. Plan upgrade during a scheduled maintenance window to minimize business impact
  3. Back up current configuration using 'backup flash' or via Aruba's management interface
  4. For ArubaOS 6.5.x: Upgrade to version 8.6.0.21 or later (consider upgrading to a supported 8.x branch)
  5. For ArubaOS 8.6.x: Upgrade to version 8.6.0.21 or later
  6. For ArubaOS 8.7.x - 8.9.x: Upgrade to version 8.10.0.7 or later
  7. For ArubaOS 8.10.x: Upgrade to version 8.10.0.7 or later
  8. For ArubaOS 8.11.x: Upgrade to version 8.11.1.1 or later
Caveat Upgrading across major version branches (e.g., 6.5 to 8.x or 8.x to 10.x) may require configuration changes or controller hardware firmware updates; review Aruba's upgrade guide before proceeding

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

Fix this in Arubaos Scoped from the published advisory
  • Consultation6.0 h
  • Implementation12.0 h
  • Testing8.0 h
  • Review / QA4.0 h
30.0 hours of engineering $5,280
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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