CVE-2024-31474
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 CLI 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 · high confidenceArbitrary file deletion vulnerability in the CLI service accessed via PAPI (Aruba's Access Point management protocol). An authenticated attacker can delete arbitrary files on the underlying operating system of the affected Access Point, leading to service disruption and integrity compromise.
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 the Aruba product and firmware versionRun 'show version' on the AP CLI or check the controller management interface for the firmware build. For ArubaOS, use 'show version' in the CLI. For HP InstantOS, use 'show system information' or check the Instant AP web UI under Administration > System > Firmware.Affected 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 HP InstantOS.
-
Confirm PAPI service accessibilityCheck if UDP port 8211 (PAPI) is open and reachable on the AP or controller. Use 'show ip interface' and verify PAPI is bound to management or control-plane interfaces. Review network access control lists or firewall rules that permit PAPI traffic from untrusted sources.Affected if PAPI service is exposed to untrusted network segments or the internet.
-
Verify authentication configuration for PAPIReview the AP or controller configuration for PAPI authentication settings. Use 'show running-config | include papi' or check the security settings in the web UI under Management > Security. Ensure shared secrets or certificates are not default/weak.Affected if PAPI authentication is disabled, uses default credentials, or allows unauthenticated command execution.
-
Inspect system logs for file deletion eventsCheck system logs using 'show log system' or review syslog/audit logs for patterns indicating file deletion commands. Look for entries involving CLI file operations or the 'delete' command executed via PAPI from unexpected sources.Affected if Logs show unauthorized file deletion attempts or successful deletions of system files from user accounts not expected to have such privileges.
You are affected if your ArubaOS or HP InstantOS version is within the specified vulnerable ranges AND PAPI is accessible to untrusted networks, regardless of authentication status.
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-supplied firmware updates from Aruba Networks. If patches are unavailable, implement network segmentation to restrict PAPI access to trusted management interfaces only.
ArubaOS: 10.4.1.1 or later / 10.5.1.1 or later; InstantOS: 8.6.0.24 or later / 8.10.0.11 or later
- 1. Identify the currently installed ArubaOS or InstantOS version by running 'show version' in the CLI
- 2. For ArubaOS 10.3.x devices, upgrade to version 10.4.1.1 or later
- 3. For ArubaOS 10.5.x devices, upgrade to version 10.5.1.1 or later
- 4. For InstantOS 6.4.x through 8.5.x devices, upgrade to version 8.6.0.24 or later
- 5. For InstantOS 8.7.x through 8.9.x devices, upgrade to version 8.10.0.11 or later
- 6. Download the appropriate firmware from the official Aruba support portal (support.hpe.com or www.arubanetworks.com)
- 7. Upload the firmware to the Aruba controller or Instant AP using the CLI command 'copy <source> flash:' or via the WebUI
- 8. Execute the upgrade using 'upgrade-software' CLI command or via the WebUI
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation8.0 h
- Testing12.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 $7,616.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-31474 — 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-31474 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