CVE-2024-31475
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 Central Communications 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 affected 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 Central Communications service accessed via PAPI (Aruba's access point management protocol). An attacker can delete arbitrary files on the underlying operating system of affected Aruba Access Points, potentially disrupting normal operations 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.1.1>= 10.5.0.0, < 10.5.1.1>= 6.4.0.0, < 8.6.0.24>= 8.7.0.0, < 8.10.0.11CVSS 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 device firmware versionAccess the Aruba Access Point CLI or web interface and run 'show version' or check the system information page to obtain the exact firmware versionAffected if The installed version falls within >= 10.3.0.0 and < 10.4.1.1, OR >= 10.5.0.0 and < 10.5.1.1 for ArubaOS; OR >= 6.4.0.0 and < 8.6.0.24, OR >= 8.7.0.0 and < 8.10.0.11 for InstantOS
-
Confirm PAPI service statusRun 'show papi status' or check the AP's service configuration to determine if the PAPI (Aruba Access Point Management Protocol) service is enabledAffected if PAPI service is enabled and accessible on the device (this is the attack vector for the vulnerability)
-
Review system logs for file deletion eventsCheck system logs using 'show log all' or review audit logs for patterns of unexpected file deletion commands, particularly involving system files or configuration filesAffected if Logs show unexpected or unauthorized file deletion operations that were not initiated by legitimate administrative actions
-
Inspect for missing or modified critical filesCompare current critical system files and configurations against known-good backups or baseline, focusing on /flash, /var, and system configuration directoriesAffected if Critical system files, certificates, or configuration files are missing or have been unexpectedly modified
A device is affected if it runs a vulnerable ArubaOS or InstantOS version (within the ranges listed) AND has the PAPI service enabled, with exploitation indicated by unauthorized file deletions in logs or missing system files.
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.248.10.0.1110.4.1.1
Apply vendor-provided patches or firmware updates for Aruba Access Points to address this vulnerability. If patches are unavailable, restrict network access to the PAPI service and monitor for signs of exploitation.
ArubaOS 10.4.1.1+ or 10.5.1.1+; InstantOS 8.6.0.24+ or 8.10.0.11+
- 1. Identify the current ArubaOS or InstantOS version running on the affected device
- 2. For ArubaOS: If running version 10.3.x.x, upgrade to version 10.4.1.1 or later; if running version 10.5.x.x, upgrade to version 10.5.1.1 or later
- 3. For InstantOS: If running version 6.4.x.x, upgrade to version 8.6.0.24 or later; if running version 8.7.x.x through 8.9.x.x, upgrade to version 8.10.0.11 or later
- 4. Download the appropriate upgrade image from the official Aruba Networks support portal (support.hpe.com or www.arubanetworks.com)
- 5. Follow Aruba's standard upgrade procedure for your deployment model (standalone, controller-based, or Instant)
- 6. After upgrade, verify the Central Communications service (PAPI) is functioning normally
- 7. Confirm the device is running a fixed version by checking the OS version
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation3.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,224.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-31475 — 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-2024-31475 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