dbcve.org
ArubaosOperating system · Arubanetworks

CVE-2022-37885

CRITICAL · 9.8 CVSS v3.1 Published 2022-10-07
Fix available
A fix is available. Upgrade to 6.4.4.8-4.2.4.21 / 6.5.4.24 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 buffer overflow vulnerabilities in multiple underlying services that could lead to unauthenticated remote code execution by sending specially crafted packets destined to the PAPI (Aruba Networks AP management protocol) UDP port (8211). Successful exploitation of these vulnerabilities results in the ability to execute arbitrary code as a privileged user on the underlying operating system of Aruba InstantOS 6.4.x: 6.4.4.8-4.2.4.20 and below; Aruba InstantOS 6.5.x: 6.5.4.23 and below; Aruba InstantOS 8.6.x: 8.6.0.18 and below; Aruba InstantOS 8.7.x: 8.7.1.9 and below; Aruba InstantOS 8.10.x: 8.10.0.1 and below; ArubaOS 10.3.x: 10.3.1.0 and below; Aruba has released upgrades for Aruba InnstantOS that address these security vulnerabilities.

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

Buffer overflow vulnerabilities in the PAPI (Aruba Networks AP management protocol) service on UDP port 8211 allow unauthenticated remote attackers to execute arbitrary code as a privileged user on affected Aruba InstantOS and ArubaOS devices.

MitigationUpgrade to the patched versions of Aruba InstantOS or ArubaOS as specified in Aruba's security advisory; restrict access to UDP port 8211 at network perimeter as an interim control.

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.3.0.0, < 10.3.1.1
InstantOperating system
Affected:>= 6.4.0.0, < 6.4.4.8-4.2.4.21>= 6.5.0.0, < 6.5.4.24>= 8.6.0.0, < 8.6.0.19>= 8.7.0.0, < 8.7.1.10>= 8.10.0.0, < 8.10.0.2
Scalance W1750d FirmwareOperating system
Affected:all versions

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 PAPI service is exposed on UDP port 8211
    Scan the device or network for open UDP port 8211 using a port scanner such as 'nmap -sU -p 8211 <target>' or check local listening ports with 'netstat -ulnp | grep 8211' or 'ss -ulnp | grep 8211'
    Affected if UDP port 8211 is open and listening, indicating the PAPI service is active
  2. Identify the device OS and version
    On the Aruba device, check the OS version via command line with 'show version' or check the web UI dashboard for the firmware version display
    Affected if Device runs ArubaOS version 10.3.0.0 through 10.3.1.0, or Aruba Instant version 6.4.0.0-6.4.4.8-4.2.4.20, 6.5.0.0-6.5.4.23, 8.6.0.0-8.6.0.18, 8.7.0.0-8.7.1.9, or 8.10.0.0-8.10.0.1
  3. For Siemens devices, confirm device model
    Identify the device as a Siemens Scalance W1750d by checking the model label, web interface, or SNMP inventory data
    Affected if Device is a Siemens Scalance W1750d (all firmware versions are affected)
  4. Confirm PAPI protocol is enabled
    Verify that the PAPI service is not disabled via controller configuration with 'show papi status' or check that AP management is active in the wireless controller settings
    Affected if PAPI service is enabled and the AP management interface is active on UDP 8211

The environment is affected if UDP port 8211 is open with the PAPI service active on an ArubaOS or Aruba Instant device within the vulnerable version ranges, or on any Siemens Scalance W1750d device.

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 6.4.4.8-4.2.4.21 / 6.5.4.24 / 8.6.0.19 or later
Fixed in 6.4.4.8-4.2.4.216.5.4.248.6.0.19
Interim mitigation

Upgrade to the patched versions of Aruba InstantOS or ArubaOS as specified in Aruba's security advisory; restrict access to UDP port 8211 at network perimeter as an interim control.

Recommended fix High confidence

ArubaOS 10.3.1.1+; Aruba InstantOS 6.4.4.8+, 6.5.4.24+, 8.6.0.19+, 8.7.1.10+, 8.10.0.2+; Scalance W1750d has no fix available

  1. 1. Identify the exact Aruba InstantOS or ArubaOS version currently running on affected devices
  2. 2. For Aruba InstantOS 6.4.x: Upgrade to version 6.4.4.8 or later
  3. 3. For Aruba InstantOS 6.5.x: Upgrade to version 6.5.4.24 or later
  4. 4. For Aruba InstantOS 8.6.x: Upgrade to version 8.6.0.19 or later
  5. 5. For Aruba InstantOS 8.7.x: Upgrade to version 8.7.1.10 or later
  6. 6. For Aruba InstantOS 8.10.x: Upgrade to version 8.10.0.2 or later
  7. 7. For ArubaOS 10.3.x: Upgrade to version 10.3.1.1 or later
  8. 8. For Scalance W1750d: Implement network segmentation to isolate the device; block UDP port 8211 at network perimeter; monitor for suspicious PAPI traffic
Caveat Major version upgrades may introduce configuration changes; test thoroughly before production deployment

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

Fix this in Arubaos Scoped from the published advisory
  • Consultation8.0 h
  • Implementation16.0 h
  • Testing8.0 h
  • Review / QA4.0 h
36.0 hours of engineering $6,400
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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