dbcve.org
Arubaos CxOperating system · Hpe

CVE-2023-3718

HIGH · 8.8 CVSS v3.1 Published 2023-08-01
Fix available
A fix is available. Upgrade to after 10.11.1010 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
An authenticated command injection vulnerability exists in the AOS-CX command line interface. Successful exploitation of this vulnerability results in the ability to execute arbitrary commands on the underlying operating system as a privileged user on the affected switch. This allows an attacker to fully compromise the underlying operating system on the device running AOS-CX.

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 AOS-CX switch CLI allows a logged-in attacker to execute arbitrary operating system commands with privileged (root) permissions, leading to complete operating system compromise of the network switch.

MitigationRestrict CLI access to trusted, authorized personnel only; implement network segmentation to limit exposure; apply vendor patches from Aruba when available.

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
Arubaos CxOperating system
Affected:>= 10.10.0000, <= 10.10.1050>= 10.11.0000, <= 10.11.1010

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 AOS-CX version
    Execute 'show version' in the switch CLI or check via console to retrieve the installed AOS-CX software version number
    Affected if The displayed version falls within 10.10.0000-10.10.1050 or 10.11.0000-10.11.1010
  2. Confirm CLI access is enabled
    Verify that the switch CLI management interface is accessible and functional (this is the default and primary management method on AOS-CX switches)
    Affected if CLI access is available to any user account (the vulnerability requires authenticated CLI access)
  3. Identify user account access
    Review which user accounts exist on the switch using 'show user' or 'show running-config' to see configured local users
    Affected if Any user account with CLI login privileges exists (the vulnerability affects any authenticated user, not just administrators)
  4. Check for unusual command execution logs
    Review switch logs and command history for any unexpected or unauthorized CLI commands that may indicate exploitation
    Affected if Logs show CLI commands that were not initiated by authorized administrators or show suspicious patterns indicative of command injection

Your environment is affected if the AOS-CX switch runs a version between 10.10.0000-10.10.1050 or 10.11.0000-10.11.1010 and the CLI is accessible to any authenticated user.

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.11.1010
Interim mitigation

Restrict CLI access to trusted, authorized personnel only; implement network segmentation to limit exposure; apply vendor patches from Aruba when available.

Recommended fix High confidence

Upgrade to AOS-CX 10.10.1051 or later, or 10.11.1011 or later (or latest stable 10.12.x release)

  1. 1. Backup the current switch configuration using 'copy running-config startup-config' or via console/USB
  2. 2. Access the AOS-CX switch through console or management interface
  3. 3. Verify current firmware version using 'show version' command
  4. 4. Download the fixed firmware version (10.10.1051 or later for 10.10.x branch, 10.11.1011 or later for 10.11.x branch) from Aruba support portal
  5. 5. Upload the firmware image to the switch using 'copy <source> flash:' command
  6. 6. Schedule the firmware upgrade during a maintenance window as it may cause a brief disruption
  7. 7. Execute 'firmware upgrade' command to install the new image
  8. 8. Reboot the switch using 'reload' command
Caveat Firmware upgrades may cause brief connectivity interruption; test in lab environment first and ensure configuration compatibility with the new version

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

Fix this in Arubaos Cx Scoped from the published advisory
  • Consultation4.0 h
  • Implementation16.0 h
  • Testing8.0 h
  • Review / QA4.0 h
32.0 hours of engineering $5,600
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,960.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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