dbcve.org
ArubaosOperating system · Arubanetworks

CVE-2020-24633

CRITICAL · 9.8 CVSS v3.1 Published 2020-12-11
Fix available
A fix is available. Upgrade to 2.1.0.2 / 2.2.0.1 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 are multiple buffer overflow vulnerabilities that could lead to unauthenticated remote code execution by sending especially crafted packets destined to the PAPI (Aruba Networks AP management protocol) UDP port (8211) of access-points or controllers in Aruba 9000 Gateway; Aruba 7000 Series Mobility Controllers; Aruba 7200 Series Mobility Controllers version(s): 2.1.0.1, 2.2.0.0 and below; 6.4.4.23, 6.5.4.17, 8.2.2.9, 8.3.0.13, 8.5.0.10, 8.6.0.5, 8.7.0.0 and below; 6.4.4.23, 6.5.4.17, 8.2.2.9, 8.3.0.13, 8.5.0.10, 8.6.0.5, 8.7.0.0 and below.

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

Multiple buffer overflow vulnerabilities exist in the PAPI (Aruba Networks AP management protocol) UDP port (8211) of Aruba mobility controllers and gateways. Specially crafted packets sent to this port can trigger the buffer overflow, enabling unauthenticated remote code execution on affected devices.

MitigationApply vendor-provided patches for the specific affected version lines (6.4.x, 6.5.x, 8.2.x, 8.3.x, 8.5.x, 8.6.x, 8.7.x) or upgrade to a fixed release. If patching is not immediately possible, consider network segmentation to restrict access to UDP port 8211.

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:< 6.4.4.24>= 6.5.0.0, < 6.5.4.18>= 8.0.0.0, < 8.2.2.10>= 8.3.0.0, < 8.3.0.14>= 8.4.0.0, < 8.5.0.11>= 8.6.0.0, < 8.6.0.6>= 8.7.0.0, < 8.7.1.0
Sd WanApplication
Affected:< 2.1.0.2>= 2.2.0.0, < 2.2.0.1

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. Verify UDP port 8211 is listening
    From the management interface or via network scan, confirm UDP port 8211 (PAPI) is open on the device. On the device CLI, run: `show listening ports` or check firewall rules.
    Affected if UDP port 8211 is exposed and responds to queries
  2. Determine ArubaOS version
    On the controller/gateway CLI, run: `show version` or `show controller-ip` to retrieve the installed ArubaOS firmware version.
    Affected if The version falls within any of these ranges: < 6.4.4.24; >= 6.5.0.0 and < 6.5.4.18; >= 8.0.0.0 and < 8.2.2.10; >= 8.3.0.0 and < 8.3.0.14; >= 8.4.0.0 and < 8.5.0.11; >= 8.6.0.0 and < 8.6.0.6; >= 8.7.0.0 and < 8.7.1.0
  3. Determine SD-WAN version
    If the device is an SD-WAN gateway, run: `show version` or check the SD-WAN controller management interface for the installed software version.
    Affected if The version falls within: < 2.1.0.2; or >= 2.2.0.0 and < 2.2.0.1
  4. Confirm PAPI protocol is enabled
    Check if the PAPI service is explicitly enabled in the controller configuration. Run: `show api analytics` or review the controller's service settings for PAPI/UDP 8211.
    Affected if PAPI protocol is enabled and the version is within the affected ranges listed above

You are affected if UDP port 8211 is exposed on your Aruba device and the installed ArubaOS or SD-WAN version matches any of the vulnerable version ranges.

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 2.1.0.2 / 2.2.0.1 / 6.4.4.24 or later
Fixed in 2.1.0.22.2.0.16.4.4.24
Interim mitigation

Apply vendor-provided patches for the specific affected version lines (6.4.x, 6.5.x, 8.2.x, 8.3.x, 8.5.x, 8.6.x, 8.7.x) or upgrade to a fixed release. If patching is not immediately possible, consider network segmentation to restrict access to UDP port 8211.

Recommended fix High confidence

ArubaOS: upgrade to 6.4.4.24, 6.5.4.18, 8.2.2.10, or 8.3.0.14 (or later) | SD-WAN: upgrade to 2.1.0.2 or 2.2.0.1 (or later)

  1. 1. Identify the currently installed ArubaOS or SD-WAN version on affected devices
  2. 2. Determine the appropriate upgrade path based on current version (6.4.x, 6.5.x, 8.0.x-8.2.x, 8.3.x, or SD-WAN)
  3. 3. Download the corresponding fixed version from Aruba/HPE support portal: https://asp.arubanetworks.com/
  4. 4. Review Aruba upgrade instructions for your specific controller or gateway model
  5. 5. Schedule a maintenance window as upgrades may require downtime
  6. 6. Backup current configuration before proceeding with upgrade
  7. 7. Upload the firmware to the controller/gateway
  8. 8. Execute the upgrade following Aruba's documented procedure
Caveat Review Aruba upgrade guide for controller-specific considerations; some version jumps may require intermediate upgrades; ensure compatibility with managed APs

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-2020-24633 — 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-2020-24633 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