dbcve.org
ArubaosOperating system · Arubanetworks

CVE-2024-31482

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
An unauthenticated Denial-of-Service (DoS) vulnerability exists in the ANSI escape code service accessed via the PAPI protocol. Successful exploitation of this vulnerability results 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

An unauthenticated attacker can send malicious ANSI escape codes through the PAPI protocol to the ANSI escape code service on affected Access Points, causing a denial of service. This vulnerability requires no authentication and can interrupt normal operation of the wireless access point.

MitigationApply vendor-supplied firmware/patch updates for the Access Point when available, or implement network-level filtering to restrict unauthorized PAPI protocol access until a fix can be deployed.

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 device product and OS version
    Access the Access Point CLI or web interface and retrieve the firmware/OS version. On CLI this is typically shown by running 'show version' or similar system information command.
    Affected if The installed version falls within ArubaOS versions >= 10.3.0.0 and < 10.4.1.1, or >= 10.5.0.0 and < 10.5.1.1; OR HP InstantOS versions >= 6.4.0.0 and < 8.6.0.24, or >= 8.7.0.0 and < 8.10.0.11
  2. Confirm the device is an Aruba AP running PAPI service
    Verify the Access Point is an Aruba Networks product that supports the PAPI (Protocol for Access Point Interface) protocol. Check if PAPI service is listening on the expected port (typically UDP port 8211) by examining network listening services or reviewing the AP configuration.
    Affected if The device is an Aruba AP with PAPI protocol enabled and accessible on the network
  3. Verify ANSI escape code service is enabled
    Check the AP configuration for the ANSI escape code service functionality. This service handles ANSI escape code processing for the PAPI protocol.
    Affected if The ANSI escape code service is enabled and processing PAPI protocol traffic

Your environment is affected if you have an Aruba Networks or HP InstantOS Access Point running a version within the affected ranges AND the PAPI protocol service with ANSI escape code handling is accessible to unauthenticated network attackers.

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-supplied firmware/patch updates for the Access Point when available, or implement network-level filtering to restrict unauthorized PAPI protocol access until a fix can be deployed.

Recommended fix High confidence

ArubaOS: 10.4.1.1 or 10.5.1.1; InstantOS: 8.6.0.24 or 8.10.0.11 (depending on current branch)

  1. Identify the exact version of ArubaOS or InstantOS running on the affected device
  2. If running ArubaOS version 10.3.x: upgrade to ArubaOS version 10.4.1.1 or later
  3. If running ArubaOS version 10.5.x: upgrade to ArubaOS version 10.5.1.1 or later
  4. If running InstantOS version 6.4.x through 8.6.x: upgrade to InstantOS version 8.6.0.24 or later
  5. If running InstantOS version 8.7.x through 8.10.x: upgrade to InstantOS version 8.10.0.11 or later
  6. After upgrade, verify the device is operational and the PAPI protocol service is functioning normally
Caveat Review Aruba upgrade documentation for specific upgrade path requirements and potential downtime considerations

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-31482 — 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-31482 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