CVE-2023-22774
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 · moderate confidenceThis is an authenticated path traversal vulnerability in the ArubaOS command-line interface that allows authenticated attackers to delete arbitrary files on the underlying operating system. The attacker needs valid CLI credentials to exploit this flaw, which could lead to denial of service or further compromise of the network device.
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 versionAccess the device CLI and run the command to display the OS version (typically 'show version' or 'show system information')Affected if The displayed version 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 8.7.0.0-2.3.0.0 through 8.7.0.0-2.3.0.8 for SD-WAN
-
Confirm CLI access is enabledVerify that the command-line interface service is running and accessible (check 'show cli status' or similar administrative command)Affected if CLI access is available and authenticated users can execute file-related commands
-
Review CLI command logs for path traversal patternsExamine device logs, audit logs, or command history for suspicious CLI commands containing directory traversal sequences (such as '../' or absolute paths used in file deletion or file operation commands)Affected if Logs show CLI commands attempting to access files outside the expected configuration directories, particularly delete or remove file operations with traversal patterns
-
Check for unauthorized file deletion activityReview system logs or file integrity monitoring alerts for any unexpected file deletion events, especially of system configuration files or critical operating system filesAffected if Files have been deleted that were not part of normal administrative operations
-
Identify CLI accounts with elevated privilegesList all CLI user accounts and their privilege levels using the appropriate administrative command (such as 'show user' or 'show cli users')Affected if Multiple CLI accounts exist beyond the minimum required, increasing the attack surface for credential theft
-
Audit recent CLI session activityReview CLI session logs or audit trails for any sessions originating from unexpected locations or occurring at unusual times, focusing on sessions that executed file manipulation commandsAffected if Recent CLI sessions show file operation commands that were not initiated by authorized administrators
The environment is affected if the device runs an ArubaOS or SD-WAN version within the specified ranges and the CLI interface is accessible to authenticated users, enabling potential path traversal exploitation.
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 · scopedApply the vendor-supplied ArubaOS patch when available, enforce least-privilege for CLI accounts, and monitor for unauthorized configuration changes or file deletion attempts.
ArubaOS 8.6.0.20+, 8.10.0.5+, 10.3.1.1+ or SD-WAN 8.7.0.0-2.3.0.9+ depending on product line
- 1. Identify the current ArubaOS or SD-WAN version running on the affected device using 'show version' command in CLI
- 2. Based on the current version, determine the minimum fixed release for your product line: For ArubaOS 8.6.x, upgrade to 8.6.0.20 or later; For ArubaOS 8.10.x, upgrade to 8.10.0.5 or later; For ArubaOS 10.3.x, upgrade to 10.3.1.1 or later; For SD-WAN 8.7.0.0-2.3.x, upgrade to 8.7.0.0-2.3.0.9 or later
- 3. Download the appropriate firmware from the Aruba support portal (https://asp.arubanetworks.com)
- 4. Backup the current configuration using 'backup flash' or 'write mem' commands
- 5. Upload the new firmware image to the device using 'copy tftp://<server>/<image> system:flash' or via WebUI
- 6. Boot the new image using 'boot system <image>' command
- 7. Verify the upgrade completed successfully with 'show version' to confirm the new version is running
- 8. Test that the CLI functionality works normally post-upgrade
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation6.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 $4,544.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-22774 — 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-22774 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