dbcve.org
ArubaosOperating system · Arubanetworks

CVE-2023-45617

HIGH · 8.2 CVSS v3.1 Published 2023-11-14
Fix available
A fix is available. Upgrade to 8.6.0.23 / 8.10.0.9 or later.
See remediation →
91/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click

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 · unedited
There are arbitrary file deletion vulnerabilities in the CLI service accessed by PAPI (Aruba's access point management protocol). Successful exploitation of these vulnerabilities result in the ability to delete arbitrary files on the underlying operating system, which could lead to the ability to interrupt normal operation and impact the integrity of the access point.

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 confidence

Arbitrary file deletion vulnerabilities exist in the CLI service accessed by PAPI (Aruba's access point management protocol). Successful exploitation allows attackers to delete any file on the underlying operating system, which can disrupt normal operation and compromise the integrity of Aruba access points.

MitigationApply vendor-supplied firmware updates for affected Aruba access point products. Restrict network access to the PAPI service to trusted management networks only.

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
ArubaosOperating system
Affected:>= 10.3.0.0, < 10.4.0.3= 10.5.0.0
InstantosOperating system
Affected:>= 6.4.0.0, < 8.6.0.23>= 8.10.0.0, < 8.10.0.9>= 8.11.0.0, < 8.11.2.0

CVSS 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
None
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
Low
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify the installed firmware version
    Access the Aruba access point CLI or web interface and retrieve the current OS version using 'show version' command or checking the system status page
    Affected if The displayed version falls within any of these ranges: ArubaOS >= 10.3.0.0 and < 10.4.0.3, or ArubaOS = 10.5.0.0, or InstantOS >= 6.4.0.0 and < 8.6.0.23, or InstantOS >= 8.10.0.0 and < 8.10.0.9, or InstantOS >= 8.11.0.0 and < 8.11.2.0
  2. Confirm the PAPI service status
    Check if the PAPI (Aruba AP Management Protocol) service is enabled on the device using 'show papi status' or reviewing the management interface configuration
    Affected if PAPI service is listed as enabled or running on the device
  3. Verify network accessibility of the PAPI service
    Determine if the PAPI port (typically UDP 8211) is exposed to untrusted networks by reviewing firewall rules, ACLs, or network segmentation configuration
    Affected if The PAPI port is accessible from networks other than trusted management networks

The environment is affected if the installed ArubaOS or InstantOS version matches any of the affected version ranges AND the PAPI service is enabled and accessible from accessible network segments.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 · scoped
Upgrade available Upgrade to 8.6.0.23 / 8.10.0.9 / 8.11.2.0 or later
Fixed in 8.6.0.238.10.0.98.11.2.0
Interim mitigation

Apply vendor-supplied firmware updates for affected Aruba access point products. Restrict network access to the PAPI service to trusted management networks only.

Recommended fix High confidence

ArubaOS: 10.4.0.3 or later (10.5.x branch: 10.5.1.0 or later); InstantOS: 8.6.0.23, 8.10.0.9, or 8.11.2.0 or later depending on existing branch

  1. 1. Identify the exact ArubaOS or InstantOS version currently installed using 'show version' command
  2. 2. For ArubaOS: If running >= 10.3.0.0 and < 10.4.0.3, upgrade to 10.4.0.3 or later; if running 10.5.0.0, upgrade to 10.5.1.0 or later
  3. 3. For InstantOS: If running >= 6.4.0.0 and < 8.6.0.23, upgrade to 8.6.0.23 or later; if running >= 8.10.0.0 and < 8.10.0.9, upgrade to 8.10.0.9 or later; if running >= 8.11.0.0 and < 8.11.2.0, upgrade to 8.11.2.0 or later
  4. 4. Download the appropriate firmware from Aruba's support portal (https://asp.arubanetworks.com)
  5. 5. Upload the firmware to the controller or Instant AP via WebUI or SCP
  6. 6. Execute 'upgrade' command or use WebUI to initiate the firmware upgrade
  7. 7. Verify the upgrade completed successfully and the new version is running
  8. 8. After upgrade, confirm the vulnerability is resolved by checking the release notes for the new version
Caveat Review release notes for any configuration changes or deprecated features; test in non-production environment first

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Arubaos Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA4.0 h
22.0 hours of engineering $3,860
Get the upgrade done

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 locally
dbcve dependency scanner

Check whether your project pulls in CVE-2023-45617 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2023-45617 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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