CVE-2023-22772
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 web-based management 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 confidenceAuthenticated path traversal vulnerability in ArubaOS web-based management interface allows attackers with valid credentials to traverse directory structures and delete arbitrary files on the underlying operating system through unsanitized input in file deletion functions.
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.7.0.0-2.3.0.0, <= 8.7.0.0-2.3.0.8>= 8.6.0.0, <= 8.6.0.19>= 8.10.0.0, <= 8.10.0.4>= 10.3.0.0, <= 10.3.1.0CVSS 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.
-
Determine ArubaOS or SD-WAN versionAccess the device CLI or web management interface and retrieve the installed firmware version. In CLI this is typically done with 'show version' or similar command. In web UI, version is usually visible in login page footer or system status page.Affected if The installed version falls within these ranges: ArubaOS 8.6.0.0 to 8.6.0.19, 8.10.0.0 to 8.10.0.4, 10.3.0.0 to 10.3.1.0; or SD-WAN 8.7.0.0-2.3.0.0 to 8.7.0.0-2.3.0.8.
-
Verify web-based management interface is enabledCheck device configuration or status to confirm the web-based management interface (HTTP/HTTPS) is currently active and accessible. This is typically found in device management settings or interface configurations.Affected if Web-based management interface is enabled and reachable.
-
Confirm file deletion functionality existsLocate the file deletion or file management feature within the web management interface. This may be in maintenance, backup, diagnostics, or file management sections of the UI.Affected if File deletion functions are present and accessible through the web interface.
-
Check authentication access to management interfaceDetermine whether valid administrative credentials exist for the web management interface. The vulnerability requires authenticated access.Affected if Valid credentials for the web management interface are configured or obtainable.
A user is affected if the device runs a vulnerable ArubaOS or SD-WAN version within the specified ranges AND has the web-based management interface enabled with accessible file deletion functionality.
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 · scopedRestrict access to the ArubaOS management interface to trusted IPs only, implement strict input validation and path sanitization on all file operations, and apply vendor patches when available.
ArubaOS: 8.6.0.20+, 8.10.0.5+, 10.3.2.0+ | Sd Wan: 8.7.0.0-2.3.0.9+
- 1. Identify the current installed version of ArubaOS or Sd Wan using 'show version' command
- 2. Determine the product family (ArubaOS or Sd Wan) and hardware platform
- 3. Access Aruba support portal at https://asp.arubanetworks.com to download the fixed software version
- 4. For ArubaOS 8.6.x: Upgrade to version 8.6.0.20 or later
- 5. For ArubaOS 8.10.x: Upgrade to version 8.10.0.5 or later
- 6. For ArubaOS 10.3.x: Upgrade to version 10.3.2.0 or later
- 7. For Sd Wan (8.7.0.0-2.3.x): Upgrade to version 8.7.0.0-2.3.0.9 or later
- 8. Upload the new firmware to the device using 'upgrade-software' or web interface
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-22772 — 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-22772 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