dbcve.org
ArubaosOperating system · Arubanetworks

CVE-2024-31478

HIGH · 7.5 CVSS v3.1 Published 2024-05-14
Fix available
A fix is available. Upgrade to 8.6.0.24 / 8.10.0.11 or later.
See remediation →
84/100
Remediation priority · High
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
Multiple unauthenticated Denial-of-Service (DoS) vulnerabilities exists in the Soft AP daemon accessed via the PAPI protocol. Successful exploitation of these vulnerabilites result in the ability to interrupt the normal operation 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 confidence

Multiple unauthenticated denial-of-service vulnerabilities exist in the Soft AP daemon accessed via the PAPI protocol. An attacker can exploit these vulnerabilities without authentication to crash or interrupt the normal operation of affected Access Points, causing service disruption.

MitigationApply vendor patches when available; if no patch exists, consider network segmentation to limit exposure or implement rate limiting on PAPI protocol traffic to reduce attack surface.

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.1.1>= 10.5.0.0, < 10.5.1.1
InstantosOperating system
Affected:>= 6.4.0.0, < 8.6.0.24>= 8.7.0.0, < 8.10.0.11

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
None
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/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 operating system
    Run 'show version' or check the system management interface to confirm whether the device runs ArubaOS or HP InstantOS
    Affected if The device is not running ArubaOS or HP InstantOS (different products are not affected by this CVE)
  2. Check ArubaOS version
    If running ArubaOS, execute 'show version' and locate the firmware version string (e.g., 10.3.x.x)
    Affected if Version is >= 10.3.0.0 and < 10.4.1.1, OR >= 10.5.0.0 and < 10.5.1.1
  3. Check HP InstantOS version
    If running HP InstantOS, execute 'show version' and locate the firmware version string (e.g., 8.6.x.x)
    Affected if Version is >= 6.4.0.0 and < 8.6.0.24, OR >= 8.7.0.0 and < 8.10.0.11
  4. Verify PAPI protocol accessibility
    Check if PAPI (Palms Authentication Protocol Interface) is enabled and accessible on the management interface or VLAN. Run 'show papi status' or review the PAPI listener configuration
    Affected if PAPI protocol is enabled and reachable from an untrusted network segment (this is the attack vector)
  5. Confirm Soft AP daemon presence
    Verify that the Soft AP daemon is running on the device. Execute 'show process' or check the Soft AP service status via CLI
    Affected if Soft AP daemon is active and handling PAPI requests (the vulnerable component)

The device is affected if it runs a vulnerable version of ArubaOS or HP InstantOS within the specified ranges AND has the PAPI protocol exposed with Soft AP daemon active.

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.24 / 8.10.0.11 / 10.4.1.1 or later
Fixed in 8.6.0.248.10.0.1110.4.1.1
Interim mitigation

Apply vendor patches when available; if no patch exists, consider network segmentation to limit exposure or implement rate limiting on PAPI protocol traffic to reduce attack surface.

Recommended fix High confidence

ArubaOS: 10.4.1.1 or 10.5.1.1 (and later); InstantOS: 8.6.0.24 or 8.10.0.11 (and later)

  1. 1. Identify the exact ArubaOS or InstantOS version currently running on affected devices
  2. 2. Review the Aruba upgrade guide for your specific hardware platform to ensure compatibility
  3. 3. Create a complete configuration backup before upgrading
  4. 4. Schedule a maintenance window as upgrades may cause brief service interruptions
  5. 5. For ArubaOS: If running >= 10.3.0.0 and < 10.4.1.1, upgrade to 10.4.1.1 or later; if running >= 10.5.0.0 and < 10.5.1.1, upgrade to 10.5.1.1 or later
  6. 6. For InstantOS: If running >= 6.4.0.0 and < 8.6.0.24, upgrade to 8.6.0.24 or later; if running >= 8.7.0.0 and < 8.10.0.11, upgrade to 8.10.0.11 or later
  7. 7. After upgrade, verify the PAPI service is functioning normally and the Soft AP daemon is operational
  8. 8. Confirm the new firmware version is correctly reported on the device
Caveat Enterprise network firmware upgrades may introduce configuration or behavioral changes; test in lab environment before production deployment

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-2024-31478 — 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-2024-31478 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