CVE-2023-22768
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 · uneditedAuthenticated 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 confidenceAuthenticated command injection vulnerabilities exist in the ArubaOS command line interface. An attacker with valid CLI credentials can inject arbitrary OS commands that execute with elevated privileges on the underlying operating system.
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>= 8.6.0.0, <= 8.6.0.19>= 8.10.0.0, <= 8.10.0.4>= 10.3.0.0, <= 10.3.1.0>= 8.7.0.0-2.3.0.0, <= 8.7.0.0-2.3.0.8CVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Determine ArubaOS versionLog into the Aruba CLI and run 'show version' or 'show system' to display the OS versionAffected 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
-
Determine SD-WAN versionLog into the Aruba SD-WAN CLI and run 'show version' to display the software versionAffected if The displayed version is between 8.7.0.0-2.3.0.0 and 8.7.0.0-2.3.0.8 inclusive
-
Confirm CLI access is enabledVerify that the command-line interface is accessible on the device (it is enabled by default on ArubaOS)Affected if CLI access is available to any administrative user account
You are affected if your ArubaOS or SD-WAN version falls within the listed vulnerable ranges and CLI administrative access is enabled.
Generated from the published advisory. Verify against your own configuration.
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 · scopedApply vendor-supplied patches for ArubaOS. Until patched, limit CLI access to trusted administrative users only and monitor for indicators of compromise.
ArubaOS: 8.6.0.20+ / 8.10.0.5+ / 10.3.1.1+; SD-WAN: 8.7.0.0-2.3.0.9+
- 1. Identify the exact ArubaOS or SD-WAN version currently installed by running 'show version' in the CLI
- 2. Determine which product line and version branch your device is running (ArubaOS 8.6.x, 8.10.x, 10.3.x, or SD-WAN)
- 3. For ArubaOS 8.6.x: Upgrade to version 8.6.0.20 or later (recommended: 8.7.x or 8.8.x stable release)
- 4. For ArubaOS 8.10.x: Upgrade to version 8.10.0.5 or later
- 5. For ArubaOS 10.3.x: Upgrade to version 10.3.1.1 or later (recommended: 10.4.x stable release)
- 6. For SD-WAN: Upgrade to version 8.7.0.0-2.3.0.9 or later
- 7. Download the firmware from the Aruba support portal (https://asp.arubanetworks.com)
- 8. Upload the firmware to the device using 'upgrade-software' or through the WebUI
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation8.0 h
- Implementation40.0 h
- Testing16.0 h
- Review / QA8.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $20,224.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-22768 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2023-22768 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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