dbcve.org
ArubaosOperating system · Arubanetworks

CVE-2024-33518

MEDIUM · 5.3 CVSS v3.1 Published 2024-05-01
Fix available
A fix is available. Upgrade to 8.10.0.10 / 8.11.2.1 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
An unauthenticated Denial-of-Service (DoS) vulnerability exists in the Radio Frequency Manager service accessed via the PAPI protocol. Successful exploitation of this vulnerability results in the ability to interrupt the normal operation of the affected service.

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 specially crafted requests via the PAPI protocol to the Radio Frequency Manager service, causing a denial-of-service condition that interrupts normal operation.

MitigationImplement network segmentation to restrict access to the RF Manager service, apply rate limiting on PAPI protocol endpoints, and investigate vendor patches.

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:>= 8.10.0.0, < 8.10.0.10>= 8.11.0.0, < 8.11.2.1>= 10.4.0.0, < 10.4.1.0>= 10.5.0.0, < 10.5.1.0

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 ArubaOS version
    Run 'show version' or access the controller CLI/webUI to retrieve the current OS version
    Affected if The version falls within any of these ranges: 8.10.0.0 to 8.10.0.9, 8.11.0.0 to 8.11.2.0, 10.4.0.0 to 10.4.0.9, or 10.5.0.0 to 10.5.1.0
  2. Verify if RF Manager service is enabled
    Check the controller configuration for RF Manager (RF Manager service or RFM) status via CLI 'show rf-manager' or through the web interface
    Affected if RF Manager is currently enabled and running on the device
  3. Confirm PAPI protocol accessibility
    Determine if the PAPI protocol port (default UDP 8211) is reachable from untrusted network segments by reviewing firewall rules or performing a port scan from external interfaces
    Affected if PAPI port is open to untrusted or management networks without proper access controls
  4. Review network exposure of management interfaces
    Audit which management interfaces (HTTP/HTTPS/SSH) have external access and whether they permit PAPI traffic propagation
    Affected if The controller management interface or PAPI service is accessible from non-trusted network segments

You are affected if your ArubaOS version is within the affected ranges AND the RF Manager service is enabled AND the PAPI protocol is accessible from an untrusted network.

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.10 / 8.11.2.1 / 10.4.1.0 or later
Fixed in 8.10.0.108.11.2.110.4.1.0
Interim mitigation

Implement network segmentation to restrict access to the RF Manager service, apply rate limiting on PAPI protocol endpoints, and investigate vendor patches.

Recommended fix High confidence

8.10.0.10 (for 8.10.x users) | 8.11.2.1 (for 8.11.x users) | 10.4.1.0 (for 10.4.x users) | 10.5.1.0 (for 10.5.x users)

  1. Identify the current ArubaOS version by running 'show version' on the controller CLI
  2. For ArubaOS 8.10.x branch: upgrade to version 8.10.0.10 or later
  3. For ArubaOS 8.11.x branch: upgrade to version 8.11.2.1 or later
  4. For ArubaOS 10.4.x branch: upgrade to version 10.4.1.0 or later
  5. For ArubaOS 10.5.x branch: upgrade to version 10.5.1.0 or later
  6. Follow Aruba standard upgrade procedure: backup current configuration, upload new firmware, reboot controller
  7. After upgrade completes, verify the Radio Frequency Manager service is running normally using 'show rf manager status'
Caveat Review Aruba upgrade guide for version-specific notes; major branch upgrades may have configuration or feature changes

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

Fix this in Arubaos Scoped from the published advisory
  • Consultation6.0 h
  • Implementation12.0 h
  • Testing6.0 h
  • Review / QA3.0 h
27.0 hours of engineering $4,800
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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