CVE-2022-37889
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 with root privileges on affected Aruba InstantOS and ArubaOS devices.
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 device model and OS typeAccess the device CLI or management interface and run 'show version' or check the system information page to determine if the device is an Aruba Instant or ArubaOS deviceAffected if The device is not an Aruba product or is a model outside the affected product families (ArubaOS, Aruba Instant, or Siemens Scalance W1750d)
-
Check the installed ArubaOS versionRun 'show version' in the device CLI or check the web management interface system settings. Compare the displayed version number against the affected range: 10.3.0.0 through 10.3.1.0Affected if The installed version is >= 10.3.0.0 and < 10.3.1.1
-
Check the installed Aruba Instant versionRun 'show version' in the Instant AP CLI or check the Aruba Central /Instant Web UI. Compare against all affected ranges: 6.4.0.0-6.4.4.8, 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.2Affected if The installed version falls within any of these ranges: 6.4.x before 6.4.4.8-4.2.4.21, 6.5.x before 6.5.4.24, 8.6.x before 8.6.0.19, 8.7.x before 8.7.1.10, or 8.10.x before 8.10.0.2
-
Verify if this is a Siemens Scalance W1750d deviceCheck the device model identification via 'show version' or physical labeling. This model has no version exclusion - all versions are affectedAffected if The device is a Siemens Scalance W1750d (all versions)
-
Confirm PAPI service exposure on UDP port 8211From an external host or adjacent network segment, perform a UDP port scan targeting port 8211 (e.g., nmap -sU -p 8211 <device_ip>) or check device firewall rules with 'show firewall'Affected if UDP port 8211 is open and reachable from untrusted networks
A device is affected if it is an Aruba Instant, ArubaOS, or Siemens Scalance W1750d device running a version within the specified ranges AND the PAPI service on UDP port 8211 is accessible from the network.
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 vendor-supplied firmware updates from Aruba Networks for all affected versions; until patches are deployed, restrict network access to UDP port 8211 from untrusted sources via firewall rules or network segmentation.
ArubaOS: upgrade to >= 10.3.1.1; Aruba Instant 6.4.x: upgrade to >= 6.4.4.8-4.2.4.21; Aruba Instant 6.5.x: upgrade to >= 6.5.4.24; Aruba Instant 8.6.x: upgrade to >= 8.6.0.19; Aruba Instant 8.7.x: upgrade to >= 8.7.1.10; Aruba Instant 8.10.x: upgrade to >= 8.10.0.2
- 1. Identify the exact Aruba product line (ArubaOS, Aruba Instant, or Scalance W1750d) and current firmware version using 'show version' or system console.
- 2. For Aruba Instant access points: Access the Instant controller or AirWave management interface, navigate to Maintenance > Firmware, and upgrade to the minimum fixed version for your release branch.
- 3. For ArubaOS controllers: Access the controller CLI or WebUI, navigate to Maintenance > Firmware Upgrade, and upload the 10.3.1.1 or later firmware image.
- 4. Schedule upgrade during maintenance window as the PAPI service (UDP 8211) will be restarted.
- 5. After upgrade, verify the running version matches the fixed release and confirm the PAPI service is operational.
- 6. For Scalance W1750d: Contact Siemens support for alternative mitigations as no firmware fix is available.
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.0 h
- Review / QA2.0 h
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 locallyCheck whether your project pulls in CVE-2022-37889 — 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-37889 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