CVE-2023-45619
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 · uneditedThere is an arbitrary file deletion vulnerability in the RSSI service accessed by PAPI (Aruba's access point management protocol). Successful exploitation of this vulnerability results 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 confidenceAn arbitrary file deletion vulnerability exists in the RSSI service accessed via PAPI (Aruba's access point management protocol). Successful exploitation allows authenticated attackers to delete any file on the underlying operating system of affected Aruba access points, potentially disrupting normal operation and compromising system integrity.
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>= 10.3.0.0, < 10.4.0.3= 10.5.0.0>= 6.4.0.0, < 8.6.0.23>= 8.10.0.0, < 8.10.0.9>= 8.11.0.0, < 8.11.2.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
- 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 checksWork through these to decide whether this CVE applies to you.
-
Identify the installed operating system productRun 'show version' or check the system management interface to determine if the device runs ArubaOS or HP InstantOSAffected if The product is ArubaOS or HP InstantOS
-
Check the installed ArubaOS versionExecute 'show version' and note the firmware version string (for example: 10.3.x.x, 10.4.x.x, 10.5.x.x)Affected if Version is >= 10.3.0.0 and < 10.4.0.3, or exactly 10.5.0.0
-
Check the installed HP InstantOS versionExecute 'show version' and note the firmware version string (for example: 6.4.x.x, 8.6.x.x, 8.10.x.x, 8.11.x.x)Affected if Version is >= 6.4.0.0 and < 8.6.0.23, or >= 8.10.0.0 and < 8.10.0.9, or >= 8.11.0.0 and < 8.11.2.0
-
Verify PAPI service accessibilityCheck if TCP port 8211 (PAPI) is listening and accessible from management or untrusted network segments using 'show ip interface' and network scanning toolsAffected if PAPI service is exposed to untrusted or management network segments where attackers could authenticate
-
Confirm RSSI service is enabledExecute 'show rssi profile' or check the PAPI service configuration to verify the RSSI service is activeAffected if RSSI service is enabled and accessible via PAPI
The device is affected if it runs a version of ArubaOS or HP InstantOS within the affected ranges AND the PAPI/RSSI service is accessible to the attacker.
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.238.10.0.98.11.2.0
Apply Aruba's security patches for affected access point models; if patching is immediately infeasible, restrict network access to the PAPI service to trusted management segments to reduce attack surface.
ArubaOS: Upgrade to 10.4.0.3 or later (or 10.5.0.1+ if migrating to 10.5.x); InstantOS: Upgrade to 8.6.0.23+, 8.10.0.9+, or 8.11.2.0+ depending on the current version branch
- 1. Identify the exact ArubaOS or InstantOS version currently running on the affected device
- 2. For ArubaOS devices: If running >= 10.3.0.0 and < 10.4.0.3, or if running exactly 10.5.0.0, upgrade to version 10.4.0.3 or later
- 3. For InstantOS devices: 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. Download the appropriate firmware from the Aruba Networks support portal (www.arubanetworks.com)
- 5. Follow Aruba's standard upgrade procedure to apply the firmware update
- 6. After upgrading, verify the device is functioning normally and the vulnerability is resolved
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation8.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 $5,120.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-45619 — 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-45619 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