CVE-2023-22773
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 path traversal vulnerabilities exist in the ArubaOS command line interface. Successful exploitation of these vulnerabilities result 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 · high confidenceAuthenticated path traversal vulnerabilities in the ArubaOS command line interface allow authenticated attackers to delete arbitrary files on the underlying operating system by manipulating file paths in CLI 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
- None
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:H/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.
-
Identify the installed ArubaOS versionLog into the device CLI and execute 'show version' or 'show controller-info' to display the running OS version. Alternatively, check the web management interface under Diagnostics or System Information.Affected if The displayed version number 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 for ArubaOS; or within 8.7.0.0-2.3.0.0 to 8.7.0.0-2.3.0.8 for SD-WAN.
-
Verify CLI access is enabledCheck user account configuration via 'show user' or 'show privilege' commands in the CLI, or review the enablement of CLI access in the device management settings.Affected if CLI access is available for any user account (the vulnerability requires authenticated CLI access to exploit).
-
Check for file operation CLI commandsReview the CLI command set available to user accounts, particularly commands related to file manipulation such as 'delete', 'remove', or file management operations.Affected if The CLI includes file deletion or file path manipulation capabilities accessible to the authenticated user.
-
Confirm management interface exposureVerify that the device management interface (CLI over SSH or console) is accessible from the network where attackers could connect.Affected if The CLI management interface is reachable from untrusted networks, increasing exposure to authenticated attackers.
A device is affected if it runs an ArubaOS or SD-WAN version within the specified affected ranges and has CLI access enabled for any user account.
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 dataApply the vendor-supplied ArubaOS patch to address the path traversal vulnerability and review user CLI privilege assignments to ensure least privilege.
- Consultation4.0 h
- Implementation4.0 h
- Testing8.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 $5,504.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-22773 — 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-22773 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