dbcve.org
ArubaosOperating system · Arubanetworks

CVE-2024-42399

MEDIUM · 5.3 CVSS v3.1 Published 2024-08-06
Fix available
A fix is available. Upgrade to 8.10.0.13 / 8.12.0.2 or later.
See remediation →
62/100
Remediation priority · Elevated
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 exist in the Soft AP daemon accessed via the PAPI protocol. Successful exploitation of these vulnerabilities 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

Multiple unauthenticated Denial-of-Service vulnerabilities exist in the Soft AP daemon accessed via the PAPI protocol. These vulnerabilities allow remote attackers to disrupt normal operation of the affected Access Point without any authentication credentials.

MitigationApply vendor patches or firmware updates for the Soft AP daemon when available; consider network segmentation to limit PAPI protocol exposure and implement rate limiting on management interfaces as a defensive measure.

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.4.0.0, < 10.4.1.2= 10.6.0.0
InstantosOperating system
Affected:>= 8.10.0.0, < 8.10.0.13>= 8.12.0.0, < 8.12.0.2

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
Low

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L

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 product and firmware version
    Run 'show version' on the Aruba controller or Instant AP device to obtain the exact firmware version
    Affected if The firmware version falls within >= 10.4.0.0 and < 10.4.1.2, or equals 10.6.0.0 for ArubaOS; or within >= 8.10.0.0 and < 8.10.0.13, or >= 8.12.0.0 and < 8.12.0.2 for HP InstantOS
  2. Confirm Soft AP daemon is running
    Run 'show process' or check the Soft AP daemon process status via CLI - look for 'softap' or 'sap' daemon processes
    Affected if The Soft AP daemon process is active on the device
  3. Verify PAPI protocol exposure
    Check if PAPI protocol (port 8211 UDP/TCP) is listening or accessible - run 'show ip interface' or check management interface configurations for PAPI bindings
    Affected if PAPI protocol is enabled and accessible on management or AP management interfaces
  4. Check for unauthenticated access to management interfaces
    Verify whether the management interface (WebUI or CLI) allows unauthenticated access or if PAPI is reachable from non-privileged network segments
    Affected if Management interfaces or PAPI service is accessible without authentication from network perspective

The environment is affected if the device runs a vulnerable ArubaOS or InstantOS version (within the specified ranges), has the Soft AP daemon running, and has PAPI protocol exposed to unauthenticated network access.

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.10.0.13 / 8.12.0.2 / 10.4.1.2 or later
Fixed in 8.10.0.138.12.0.210.4.1.2
Interim mitigation

Apply vendor patches or firmware updates for the Soft AP daemon when available; consider network segmentation to limit PAPI protocol exposure and implement rate limiting on management interfaces as a defensive measure.

Recommended fix High confidence

ArubaOS: 10.4.1.2+ or 10.6.1.0+; InstantOS: 8.10.0.13+ or 8.12.0.2+

  1. Identify the exact ArubaOS or InstantOS version currently installed on the affected Access Point
  2. For ArubaOS 10.4.0.0-10.4.1.1: Upgrade to version 10.4.1.2 or later
  3. For ArubaOS 10.6.0.0: Upgrade to a version higher than 10.6.0.0 (e.g., 10.6.1.0 or later)
  4. For InstantOS 8.10.0.0-8.10.0.12: Upgrade to version 8.10.0.13 or later
  5. For InstantOS 8.12.0.0-8.12.0.1: Upgrade to version 8.12.0.2 or later
  6. After upgrade, verify the Soft AP daemon is running normally and the Access Point is operational
  7. Confirm the PAPI protocol service is accessible without unexpected interruptions
Caveat Review Aruba upgrade documentation for potential migration considerations between major version branches; ensure controller compatibility before upgrading

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 / QA2.0 h
20.0 hours of engineering $3,500
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,600.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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