dbcve.org
ArubaosOperating system · Arubanetworks

CVE-2024-33513

MEDIUM · 5.9 CVSS v3.1 Published 2024-05-01
Fix available
A fix is available. Upgrade to after 10.5.1.0 or later.
See remediation →
68/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
Unauthenticated Denial-of-Service (DoS) vulnerabilities exist in the AP Management service accessed via the PAPI protocol. Successful exploitation of these vulnerabilities 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

Unauthenticated Denial-of-Service vulnerabilities in the AP Management service accessed via the PAPI protocol allow remote attackers to interrupt normal service operation without any authentication credentials.

MitigationImplement network segmentation and access controls to limit PAPI protocol exposure; apply vendor patches when available; consider rate limiting on affected interfaces.

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
High
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
None
Availability
High

CVSS:3.1/AV:N/AC:H/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 ArubaOS version
    Run 'show version' or access the controller CLI to retrieve the current OS version number
    Affected if The installed version falls within 8.10.0.0-8.10.0.10, 8.11.0.0-8.11.2.1, 10.4.0.0-10.4.1.0, or 10.5.0.0-10.5.1.0
  2. Confirm PAPI protocol is enabled
    Check the AP Management service configuration to verify PAPI protocol is active on the controller
    Affected if PAPI protocol is enabled and the version falls within the affected ranges
  3. Determine PAPI network exposure
    Review firewall rules, ACLs, or interface bindings to assess whether the PAPI service is accessible from outside the trusted management network
    Affected if PAPI is exposed to untrusted or external networks and the version is affected
  4. Check for unauthorized DoS impact indicators
    Monitor AP availability, controller responsiveness, and PAPI service logs for disruptions or unexpected resets
    Affected if Service interruptions are occurring and the version is within the affected ranges

You are affected if your ArubaOS version matches one of the four affected ranges AND the PAPI protocol is enabled and accessible on your 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 a release after 10.5.1.0
Interim mitigation

Implement network segmentation and access controls to limit PAPI protocol exposure; apply vendor patches when available; consider rate limiting on affected interfaces.

Recommended fix Moderate confidence

ArubaOS version greater than the currently installed vulnerable version (e.g., 8.10.0.11+, 8.11.3.0+, 10.4.2.0+, or 10.5.2.0+)

  1. 1. Identify the currently running ArubaOS version using 'show version' command
  2. 2. Determine which version branch (8.10.x, 8.11.x, 10.4.x, or 10.5.x) is in use
  3. 3. Download the appropriate fixed ArubaOS version from the Aruba support portal at https://asp.arubanetworks.com
  4. 4. Upload the new firmware to the controller or managed device
  5. 5. Validate the firmware image integrity using the provided checksum
  6. 6. Schedule a maintenance window as the upgrade will cause brief service interruption
  7. 7. Execute the firmware upgrade using 'upgrade-software' command
  8. 8. After reboot, verify the new version is running with 'show version'
Caveat Standard ArubaOS upgrade considerations apply: verify controller hardware compatibility, review release notes for known issues, and ensure backup of configuration before proceeding

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