CVE-2023-22790
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 · uneditedMultiple authenticated command injection vulnerabilities exist in the Aruba InstantOS and ArubaOS 10 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 in Aruba InstantOS and ArubaOS 10 CLI allow attackers to inject and execute arbitrary OS commands with elevated (privileged) user rights. Multiple injection points exist in the command-line interface.
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>= 10.3.0.0, <= 10.3.1.0>= 6.4.0.0, <= 6.4.4.8-4.2.4.20>= 6.5.0.0, <= 6.5.4.23>= 8.4.0.0, < 8.6.0.0>= 8.6.0.0, <= 8.6.0.19>= 8.7.0.0, <= 8.9.0.0>= 8.10.0.0, <= 8.10.0.4CVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Identify the product and versionAccess the device CLI and run 'show version' or 'show system info' to display the installed ArubaOS or InstantOS version numberAffected if The displayed version falls within any of the affected ranges: ArubaOS 10.3.0.0-10.3.1.0, InstantOS 6.4.0.0-6.4.4.8-4.2.4.20, 6.5.0.0-6.5.4.23, 8.4.0.0-8.5.x.x, 8.6.0.0-8.6.0.19, 8.7.0.0-8.9.0.0, or 8.10.0.0-8.10.0.4
-
Confirm the product typeRun 'show inventory' or 'show controller' to confirm whether the device runs ArubaOS or InstantOSAffected if The product is ArubaOS version 10.3.x.x or InstantOS any version in the 6.4.x, 6.5.x, 8.4.x, 8.6.x, 8.7.x, 8.8.x, 8.9.x, or 8.10.x branches
-
Verify CLI interface accessibilityCheck if the device CLI (SSH, telnet, or console) is accessible from untrusted networks by reviewing access control lists, management interface bindings, and firewall rulesAffected if CLI access is permitted from outside trusted management networks or the internet-facing interface
-
Review authenticated CLI user accountsRun 'show users' or 'show user-list' to list accounts with CLI access privilegesAffected if There are user accounts with CLI login capability, particularly any with elevated or privileged rights
Your environment is affected if the device runs ArubaOS 10.3.0.0-10.3.1.0 or InstantOS within any of the listed version ranges and the CLI is accessible to an attacker who can obtain valid credentials.
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.
From vendor data8.6.0.0
Apply Aruba's security patches immediately. Until patched, restrict CLI access to trusted IP addresses only, use network segmentation, and disable external management interfaces where possible.
- Consultation3.0 h
- Implementation2.0 h
- Testing6.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,840.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-22790 — 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-22790 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