dbcve.org
ArubaosOperating system · Arubanetworks

CVE-2020-24634

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
An attacker is able to remotely inject arbitrary commands by sending especially crafted packets destined to the PAPI (Aruba Networks AP Management protocol) UDP port (8211) of access-pointsor 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

Remote command injection vulnerability in the PAPI (Aruba AP Management protocol) on UDP port 8211 of Aruba mobility controllers and gateways. Attackers can send specially crafted packets to inject and execute arbitrary operating system commands without authentication, achieving full system compromise.

MitigationApply vendor-supplied patches for affected versions (6.4.x, 6.5.x, 8.2.x, 8.3.x, 8.5.x, 8.6.x, 8.7.x). As an interim measure, restrict network access to UDP port 8211 to trusted management networks only and implement network segmentation for management 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.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. Check if UDP port 8211 is listening and exposed
    Run 'show ip interface' or 'show interface | include 8211' on the Aruba CLI to verify if UDP port 8211 is bound to any interface. Use a network scanner (e.g., nmap -sU -p 8211 <target>) from an external host to confirm the port is accessible.
    Affected if UDP port 8211 is open and accessible from untrusted networks or the internet
  2. Identify the ArubaOS version
    Execute 'show version' on the Aruba mobility controller or gateway CLI. Note the exact version number displayed in the output.
    Affected if The installed version falls within any of these ranges: < 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, or >= 8.7.0.0 and < 8.7.1.0
  3. Identify the Aruba SD-WAN version
    Execute 'show version' or 'show sd-wan version' on the SD-WAN gateway CLI. Note the exact version number displayed.
    Affected if The installed SD-WAN version is < 2.1.0.2, or >= 2.2.0.0 and < 2.2.0.1
  4. Verify management interface network exposure
    Review the device ACLs and firewall policies to confirm whether UDP port 8211 traffic from untrusted networks is permitted. Check 'show ip access-list' and 'show firewall-policy' for rules allowing traffic on UDP 8211 from external sources.
    Affected if There are firewall or ACL rules that permit unsolicited UDP port 8211 traffic from management networks that are not explicitly trusted

The environment is affected if the device runs a vulnerable ArubaOS or SD-WAN version AND UDP port 8211 is accessible from untrusted networks.

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 / 8.2.2.10 or later
Fixed in 2.1.0.22.2.0.18.2.2.10
Interim mitigation

Apply vendor-supplied patches for affected versions (6.4.x, 6.5.x, 8.2.x, 8.3.x, 8.5.x, 8.6.x, 8.7.x). As an interim measure, restrict network access to UDP port 8211 to trusted management networks only and implement network segmentation for management interfaces.

Recommended fix High confidence

ArubaOS: 8.2.2.10, 8.3.0.14, 8.5.0.11, or 8.6.0.6 (or later); SD-WAN: 2.1.0.2 or 2.2.0.1 (or later)

  1. 1. Identify the exact ArubaOS or SD-WAN version currently installed on the affected device
  2. 2. For ArubaOS: Determine which version branch you are on (8.2.x, 8.3.x, 8.4.x, 8.5.x, or 8.6.x)
  3. 3. Download the appropriate fixed ArubaOS version from HPE Aruba support portal: 8.2.2.10 or higher, 8.3.0.14 or higher, 8.5.0.11 or higher, or 8.6.0.6 or higher
  4. 4. For SD-WAN: Download fixed version 2.1.0.2 or higher, or 2.2.0.1 or higher from HPE Aruba support portal
  5. 5. Before upgrading, backup the current configuration following Aruba backup procedures
  6. 6. Upgrade the device during a maintenance window following Aruba's official upgrade instructions
  7. 7. After upgrade, verify the device is functioning correctly and the version has been updated
  8. 8. Confirm the PAPI UDP port 8211 is still accessible only from trusted management networks
Caveat Review HPE Aruba release notes for your specific version upgrade for any known compatibility issues or migration requirements

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