CVE-2022-37888
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 · uneditedThere 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 confidenceBuffer overflow vulnerabilities in the PAPI (Aruba Networks AP management protocol) service listening on UDP port 8211 allow unauthenticated attackers to send specially crafted packets and achieve remote code execution as a privileged user on the underlying operating system.
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>= 10.3.0.0, < 10.3.1.1>= 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.2all versionsCVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Identify the installed productDetermine if the system is running ArubaOS, Aruba Instant, or Siemens Scalance W1750d. On the device CLI, run 'show version' or check the system information interface.Affected if The product is not ArubaOS, Aruba Instant, or Siemens Scalance W1750d - this CVE does not apply.
-
Verify the PAPI service is exposed on UDP 8211Check if UDP port 8211 is listening on the device. Run 'netstat -an | grep 8211' or 'show ip interface' to verify the PAPI service is bound to a reachable interface.Affected if UDP port 8211 is not open or not accessible - the vulnerability cannot be exploited in its current configuration.
-
Check the ArubaOS versionIf running ArubaOS, execute 'show version' or 'show system info' to obtain the exact firmware version number.Affected if Version is >= 10.3.0.0 and < 10.3.1.1 - the system is within the affected range.
-
Check the Aruba Instant versionIf running Aruba Instant, execute 'show version' or access the controller web UI to retrieve the InstantOS version.Affected if Version falls within any of these ranges: >= 6.4.0.0 and < 6.4.4.8-4.2.4.21; >= 6.5.0.0 and < 6.5.4.24; >= 8.6.0.0 and < 8.6.0.19; >= 8.7.0.0 and < 8.7.1.10; >= 8.10.0.0 and < 8.10.0.2.
-
Check the Siemens Scalance W1750d firmware versionIf running Siemens Scalance W1750d, check the firmware version through the device web interface or CLI.Affected if Any version of Scalance W1750d firmware is installed - all versions are affected.
The environment is affected if UDP port 8211 is open and the device runs a vulnerable ArubaOS version (10.3.0.0 to 10.3.1.0), a vulnerable Aruba Instant version in any of the five listed ranges, or any Siemens Scalance W1750d firmware version.
Generated from the published advisory. Verify against your own configuration.
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 · scoped6.4.4.8-4.2.4.216.5.4.248.6.0.19
Apply Aruba's released firmware upgrades for InstantOS and ArubaOS to address these critical RCE vulnerabilities; affected deployments should prioritize patching given the CVSS 9.8 severity and unauthenticated exploitation vector.
ArubaOS: 10.3.1.1+ | Instant: 6.4.4.8+, 6.5.4.24+, 8.6.0.19+, 8.7.1.10+ | Scalance W1750d: Contact vendor
- Identify the exact version of ArubaOS or InstantOS currently running on the affected device
- For ArubaOS 10.3.x devices: Upgrade to version 10.3.1.1 or later
- For InstantOS 6.4.x devices: Upgrade to version 6.4.4.8-4.2.4.21 or later (6.4.4.8 or higher)
- For InstantOS 6.5.x devices: Upgrade to version 6.5.4.24 or later
- For InstantOS 8.6.x devices: Upgrade to version 8.6.0.19 or later
- For InstantOS 8.7.x devices: Upgrade to version 8.7.1.10 or later
- For Scalance W1750d devices: Contact Siemens for a firmware update; no fixed version is currently documented
- After upgrade, verify that PAPI UDP port 8211 is properly secured via access controls if exposed to untrusted networks
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation6.0 h
- Implementation12.0 h
- Testing8.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $8,448.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-37888 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2022-37888 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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