dbcve.org
ArubaosOperating system · Arubanetworks

CVE-2024-31470

CRITICAL · 9.8 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 →
100/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 is a buffer overflow vulnerability in the underlying SAE (Simultaneous Authentication of Equals) service that could lead to unauthenticated remote code execution by sending specially crafted packets destined to the PAPI (Aruba's Access Point management protocol) UDP port (8211). Successful exploitation of this vulnerability results in the ability to execute arbitrary code as a privileged user on the underlying operating system.

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 confidence

A buffer overflow vulnerability exists in Aruba's SAE (Simultaneous Authentication of Equals) service that handles authentication for the PAPI (Access Point management protocol) on UDP port 8211. An unauthenticated attacker can send specially crafted packets to trigger the overflow and achieve remote code execution with privileged (root) system privileges.

MitigationApply the vendor patch from Aruba for affected products. As an interim control, restrict network access to UDP port 8211 to prevent untrusted sources from reaching the PAPI service.

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

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/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 operating system version
    Run 'show version' on the Aruba controller or access point to determine the installed ArubaOS or InstantOS version number
    Affected if The installed version falls within >= 10.3.0.0, < 10.4.1.1; >= 10.5.0.0, < 10.5.1.1 for ArubaOS, or >= 6.4.0.0, < 8.6.0.24; >= 8.7.0.0, < 8.10.0.11 for InstantOS
  2. Verify if PAPI service is running on UDP port 8211
    Run 'show ip interface' or 'show port status' to confirm UDP port 8211 is open and listening for PAPI protocol traffic
    Affected if UDP port 8211 is open and accessible on the device
  3. Confirm SAE authentication is enabled for PAPI
    Check the PAPI security configuration via 'show papi configuration' or review the SAE (Simultaneous Authentication of Equals) settings in the controller or AP management interface
    Affected if SAE authentication is enabled for the PAPI service on UDP port 8211
  4. Determine network exposure of UDP port 8211
    Review firewall rules or access control lists using 'show firewall' or 'show ip access-list' to identify if UDP port 8211 is exposed to untrusted networks
    Affected if UDP port 8211 is reachable from untrusted or external network segments

The environment is affected if the device runs a vulnerable ArubaOS or InstantOS version AND has UDP port 8211 (PAPI service with SAE) exposed to untrusted network sources.

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 the vendor patch from Aruba for affected products. As an interim control, restrict network access to UDP port 8211 to prevent untrusted sources from reaching the PAPI service.

Recommended fix High confidence

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

  1. 1. Identify all affected ArubaOS and InstantOS devices in the inventory
  2. 2. For ArubaOS devices: Schedule a maintenance window and upgrade to version 10.4.1.1 or later (for 10.3.x deployments), or to version 10.5.1.1 or later (for 10.5.x deployments)
  3. 3. For InstantOS devices: Upgrade to version 8.6.0.24 or later (for 6.4.x-8.5.x deployments), or to version 8.10.0.11 or later (for 8.7.x-8.9.x deployments)
  4. 4. Verify the upgrade completed successfully by checking the device GUI or CLI for the new version
  5. 5. Confirm the PAPI service (UDP port 8211) is still operational post-upgrade
  6. 6. Validate that SAE authentication functions correctly after the upgrade
Caveat Major version upgrades may introduce configuration or feature changes; review release notes before upgrading and test in a non-production environment

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

Fix this in Arubaos Scoped from the published advisory
  • Consultation4.0 h
  • Implementation4.0 h
  • Testing8.0 h
  • Review / QA4.0 h
20.0 hours of engineering $3,440
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,504.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-31470 — 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-31470 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