CVE-2023-35977
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 · uneditedVulnerabilities exist which allow an authenticated attacker to access sensitive information on the ArubaOS command line interface. Successful exploitation could allow access to data beyond what is authorized by the users existing privilege level.
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 confidenceAn authenticated attacker with valid CLI credentials can exploit vulnerabilities in ArubaOS to access sensitive information beyond their authorized privilege level. This represents a privilege escalation or information disclosure issue in the command-line interface of Aruba's network 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>= 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
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- None
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N
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 ArubaOS versionLog into the device via console or SSH and execute 'show version' or 'show system information' to retrieve the running ArubaOS versionAffected if The displayed version falls within any of these ranges: >= 6.5.4.0 and < 8.6.0.21; >= 8.7.0.0 and < 8.10.0.7; >= 8.11.0.0 and < 8.11.1.1; >= 10.4.0.0 and < 10.4.0.2
-
Verify CLI access is enabledConfirm the command-line interface is accessible by attempting to log in via console, SSH, or telnet. Use 'show ip ssh' or 'show telnet' to check if remote CLI access methods are enabledAffected if CLI access (SSH, telnet, or console) is enabled and the device is running an affected ArubaOS version
-
Review user accounts with CLI privilegesExecute 'show user-database' or 'show local-user' to list all accounts that have CLI access. Identify accounts with elevated privileges or those that may have more access than intendedAffected if Multiple user accounts exist with CLI access and the device runs an affected ArubaOS version
A device is affected if it runs any ArubaOS version within the four affected ranges and has CLI access enabled for authenticated users.
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 ArubaOS patches to address the privilege escalation vulnerability. Review user account privileges and restrict CLI access to only necessary personnel until the patch is deployed.
Upgrade to the minimum fixed version for your current branch: 8.6.0.21, 8.10.0.7, 8.11.1.1, or 10.4.0.2
- Identify the current ArubaOS version by running 'show version' on the CLI
- Determine which version branch the current installation falls into based on the affected version ranges
- For versions >= 6.5.4.0 and < 8.6.0.21: upgrade to ArubaOS 8.6.0.21 or later in the 8.6.x branch
- For versions >= 8.7.0.0 and < 8.10.0.7: upgrade to ArubaOS 8.10.0.7 or later in the 8.10.x branch
- For versions >= 8.11.0.0 and < 8.11.1.1: upgrade to ArubaOS 8.11.1.1 or later in the 8.11.x branch
- For versions >= 10.4.0.0 and < 10.4.0.2: upgrade to ArubaOS 10.4.0.2 in the 10.4.x branch
- Download the appropriate upgrade image from the Aruba support portal
- Upload the image to the controller and execute 'upgrade-software' command
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,176.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-35977 — 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-35977 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