CVE-2023-22769
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 · moderate confidenceAuthenticated command injection vulnerabilities exist in the ArubaOS command line interface that allow authenticated users to execute arbitrary commands as a privileged (root) user on the underlying operating system. The vulnerability stems from improper input sanitization in the CLI parsing mechanism, enabling attackers with valid credentials to break out of intended command boundaries and inject OS-level commands.
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.
-
Identify installed ArubaOS versionLog into the ArubaOS CLI and run: show version or show system information. Alternatively, check the WebUI under Monitoring > Dashboard > Overview.Affected if The version displayed 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.
-
Identify installed SD-WAN versionIf the device runs Aruba SD-WAN, log into the SD-WAN CLI or management interface and run: show version or show sd-wan version.Affected if The version displayed is between 8.7.0.0-2.3.0.0 and 8.7.0.0-2.3.0.8 inclusive.
-
Review CLI audit logs for suspicious commandsRun: show log all or show audit-log for recent CLI activity. Look for commands that appear to break out of expected CLI syntax, contain unusual characters, or execute system-level operations unexpected for the user role.Affected if Entries show commands containing shell metacharacters, multiple command separators, or unexpected privilege escalation.
-
Check for unauthorized or unexpected CLI usersRun: show users or show cli session to list currently active and recent CLI sessions.Affected if Sessions exist from users who should not have CLI access, or sessions show activity inconsistent with the user's expected role.
-
Verify CLI access controls are in placeReview the configuration with: show running-config | include cli or check the user role definitions under: show user-role. Confirm only authorized users have CLI-enabled roles.Affected if CLI access is granted to untrusted users or roles with excessive privileges.
You are affected if your ArubaOS version is 8.6.0.0-8.6.0.19, 8.10.0.0-8.10.0.4, or 10.3.1.0 or below, or your SD-WAN version is 8.7.0.0-2.3.0.0 through 8.7.0.0-2.3.0.8, and the CLI is accessible to users who are not strictly trusted.
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 the vendor-supplied ArubaOS patch or upgrade to a fixed version. Until patched, strictly limit CLI access to trusted, authorized personnel only and monitor for suspicious command activity.
ArubaOS 8.6.0.20+, 8.10.0.5+, 10.3.1.1+ | SD-WAN 8.7.0.0-2.3.0.9+
- Identify the currently installed ArubaOS or SD-WAN version using 'show version' in the CLI
- Determine the product line (ArubaOS or SD-WAN) and the specific version branch from the affected versions list
- For ArubaOS 8.6.x: Upgrade to version 8.6.0.20 or later
- For ArubaOS 8.10.x: Upgrade to version 8.10.0.5 or later
- For ArubaOS 10.3.x: Upgrade to version 10.3.1.1 or later
- For SD-WAN 8.7.0.0-x: Upgrade to version 8.7.0.0-2.3.0.9 or later
- After upgrade, verify the fix by checking 'show version' confirms the new version is installed
- Review that the command-line interface access is restricted to trusted administrative users only
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation3.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,680.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-22769 — 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-22769 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