CVE-2023-35975
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 · uneditedAn authenticated path traversal vulnerability exists in the ArubaOS command line interface. Successful exploitation of this vulnerability results in the ability to delete arbitrary files in 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 confidenceThis is an authenticated path traversal vulnerability in the ArubaOS command-line interface that allows an authenticated attacker to delete arbitrary files on the underlying operating system. The vulnerability stems from improper input validation in CLI commands, enabling attackers to use directory traversal sequences (such as ../) to access files outside intended directories.
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
- None
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/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.
-
Verify ArubaOS versionRun 'show version' in the CLI or check the WebUI dashboard for the installed ArubaOS version numberAffected if The installed version is >= 6.5.4.0 and < 8.6.0.21, OR >= 8.7.0.0 and < 8.10.0.7, OR >= 8.11.0.0 and < 8.11.1.1, OR >= 10.4.0.0 and < 10.4.0.2
-
Confirm CLI access is enabledCheck if the command-line interface is accessible via console, SSH, or telnet by attempting to connect or reviewing access control settingsAffected if CLI access is permitted to untrusted or unauthorized users
-
Review CLI audit logs for delete commandsExamine CLI logs for commands containing 'delete file' or similar operations, especially those using path traversal patterns (../)Affected if Logs show delete operations referencing paths outside expected directories
-
Inspect recent CLI command historyRun 'show cli history' or review system logs for recent commands executed by authenticated users, focusing on file manipulation commandsAffected if Unexpected or unauthorized file delete commands appear in the command history
A system is affected if it runs an ArubaOS version within the listed vulnerable ranges AND has CLI access available to an authenticated attacker who could exploit the path traversal to delete arbitrary files.
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 for ArubaOS; until patched, limit CLI access to trusted personnel only and monitor for unusual delete operations.
8.6.0.21 (for 6.5.x branch), 8.10.0.7 (for 8.7.x branch), 8.11.1.1 (for 8.11.x branch), or 10.4.0.2 (for 10.4.x branch)
- 1. Determine the current ArubaOS version by running 'show version' in the CLI
- 2. Identify which version branch your current installation belongs to (6.5.x, 8.7.x, 8.11.x, or 10.4.x)
- 3. Navigate to the Aruba Support Portal at https://asp.arubanetworks.com and download the appropriate fixed version for your branch: 8.6.0.21 for 6.5.x, 8.10.0.7 for 8.7.x, 8.11.1.1 for 8.11.x, or 10.4.0.2 for 10.4.x
- 4. Upload the firmware image to the Aruba controller via SCP, FTP, or through the WebUI
- 5. From CLI, execute 'upgrade-software' or from WebUI navigate to Maintenance > Firmware > Upgrade to initiate the upgrade process
- 6. After the device reboots, verify the new version by running 'show version' and confirming it matches the target fixed release
- 7. Test that the CLI functionality is operational and the path traversal vulnerability is no longer present
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-35975 — 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-35975 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