CVE-2023-35974
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 vulnerability in the ArubaOS command line interface allows a remote authenticated attacker to execute arbitrary OS-level commands with privileged (root) user rights. The vulnerability exists in the CLI parsing mechanism and can be exploited by sending specially crafted commands through the authenticated CLI session.
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>= 6.5.4.0, < 8.6.0.21>= 8.7.0.0, < 8.10.0.7>= 8.11.0.0, < 8.11.1.1>= 10.4.0.0, < 10.4.0.2CVSS 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 versionAccess the CLI and run 'show version' or 'show system information' to retrieve the current ArubaOS version numberAffected if The installed version falls within any of these ranges: 6.5.4.0 to 8.6.0.20, 8.7.0.0 to 10.4.0.1, 8.10.0.0 to 8.10.0.6, or 8.11.0.0 to 8.11.1.0 (versions before the fixed releases)
-
Verify CLI access is enabledCheck if the CLI service is accessible by attempting to connect to the device via console, SSH, or telnet. Review 'show ip ssh' or 'show telnet' to confirm CLI access methods are enabledAffected if CLI access (SSH, telnet, or console) is enabled and exposed to network attackers
-
Review CLI command logs for suspicious activityExecute 'show logging -r' or review CLI audit logs for unusual or malformed commands, especially commands containing shell metacharacters like ; | & $ or backticksAffected if Logs show unexpected CLI commands that could indicate exploitation attempts or successful command injection
-
Check for unauthorized user sessionsRun 'show users' or 'show user-table' to list active and recent authenticated CLI sessions, and compare against known administrative accountsAffected if Unknown or unexpected user accounts have active CLI sessions
-
Inspect for unexpected cron jobs or system modificationsReview the device configuration with 'show configuration' and check for unauthorized cron jobs, scripts, or system modifications that could indicate post-exploitation activityAffected if Configuration contains unfamiliar cron jobs, scripts, or modifications not authored by your organization
You are affected if your ArubaOS version is within the vulnerable version ranges AND CLI access is enabled, particularly if unauthenticated or untrusted network access to CLI is possible.
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 · scoped8.6.0.218.10.0.78.11.1.1
Apply the vendor-supplied patch from Aruba Networks for affected ArubaOS versions. Restrict CLI access to trusted administrative IPs only and enforce strong authentication policies to reduce attack surface.
ArubaOS 8.6.0.21, 8.10.0.7, 8.11.1.1, or 10.4.0.2 (depending on your current branch); recommend upgrading to latest stable 10.4.x or 8.10.x branch for long-term support
- 1. Back up the current ArubaOS configuration using the command: `backup flash` or via the WebUI.
- 2. Download the appropriate fixed ArubaOS firmware from the Aruba Networks support portal: https://asp.arubanetworks.com/
- 3. Upload the new firmware to the Aruba device via WebUI or SCP: `copy scp: <server> <file> flash:`
- 4. Verify the firmware image integrity: `verify image flash:`
- 5. Boot from the new image: `boot system flash:`
- 6. After reboot, confirm the version: `show version` and verify it matches the fixed release (8.6.0.21, 8.10.0.7, 8.11.1.1, or 10.4.0.2 or later).
- 7. Verify the command injection vulnerability is no longer present by attempting the documented exploitation method.
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-35974 — 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-35974 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