dbcve.org
ArubaosOperating system · Arubanetworks

CVE-2023-22767

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 vulnerabilities in ArubaOS CLI allow authenticated users to execute arbitrary commands with elevated privileges on the underlying operating system.

MitigationApply vendor patches for ArubaOS immediately. Restrict CLI access to trusted, least-privilege users and network-isolate management interfaces.

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 access the WebUI dashboard to view the firmware version. In the WebUI, navigate to Maintenance > Firmware or check the dashboard overview.
    Affected if The displayed 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 within 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
    In the WebUI, navigate to Configuration > Management > CLI Settings or Configuration > System > Admin. Verify that CLI access (SSH or Telnet) is enabled under the management access settings.
    Affected if CLI access (SSH or Telnet) is enabled and the device is running an affected version.
  3. Check management interface exposure
    Review the interface configuration in Configuration > Network > Interfaces or Configuration > Management > Management IP. Identify which interfaces have management access (SSH/Telnet) enabled and whether they are exposed to untrusted networks.
    Affected if Management interfaces with CLI access enabled are reachable from untrusted networks or the internet.
  4. Review authenticated CLI user accounts
    In the WebUI, go to Configuration > Management > Administrators or Configuration > System > Admin Users. List all accounts with CLI access privileges. Also run 'show user-database' in the CLI to view local user accounts.
    Affected if Any enabled CLI user account exists on a device running an affected version, since even low-privilege authenticated users can execute elevated commands.
  5. Audit for suspicious command execution
    Run 'show audit-log' in the CLI or review logs in Configuration > Monitoring > Logs. Look for unexpected commands, particularly those involving shell execution, file manipulation, or privilege escalation patterns.
    Affected if Evidence of arbitrary command execution appears in logs from an authenticated CLI session.

A user is affected if their device runs a version within the listed ranges, has CLI access enabled, and has any authenticated user accounts 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 a release after 10.3.1.0
Interim mitigation

Apply vendor patches for ArubaOS immediately. Restrict CLI access to trusted, least-privilege users and network-isolate management interfaces.

Recommended fix Moderate confidence

ArubaOS 8.6.0.20 or later; 8.10.0.5 or later; 10.3.1.1 or later | SD-WAN 8.7.0.0-2.3.0.9 or later

  1. 1. Identify the currently installed ArubaOS or SD-WAN version using 'show version' in the CLI
  2. 2. Determine the appropriate upgrade path based on your current version branch (8.6.x, 8.10.x, 10.3.x, or SD-WAN)
  3. 3. Download the fixed ArubaOS or SD-WAN release from the Aruba secure support portal at https://asp.arubanetworks.com/
  4. 4. Upload the firmware file to the controller using 'copy tftp://<server>/<file> system:flash' or via WebUI
  5. 5. Verify the image integrity using 'verify image' command before booting
  6. 6. Boot the new image using 'reload' or schedule a maintenance window
  7. 7. After reboot, confirm the new version is running with 'show version'
  8. 8. Verify the vulnerability is remediated by confirming the version is beyond the affected ranges
Caveat Upgrading between major versions may require configuration review; test upgrade in staging environment first

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

Fix this in Arubaos Scoped from the published advisory
  • Consultation6.0 h
  • Implementation3.0 h
  • Testing3.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,550
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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