# CVE-2022-37888: Memory corruption in Aruba Access Points: 100 Series; 103 Series; 110 Series; 120 Series; 130 Series; 200 Series; 207 Series; 210 Series; 220 Series; 260 Series; 300 Series; 303 Series; 310 Series; 318 Series Hardened Access Points; 320 Series; 330 Series; 340 Series; 370 Series; 500 Series; 510 Series; 530 Series; 550 Series; 630 Series; 650 Series;

> Unauthenticated remote attackers can execute arbitrary code with privileged access on Aruba Access Points via buffer overflows in the PAPI protocol.

- **Severity:** Critical 9.8 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 6 Oct 2022
- **Updated:** 3 Aug 2024
- **Also known as:** GHSA-j45x-9cfm-vhqh

## What is CVE-2022-37888?

CVE-2022-37888 is a critical memory corruption vulnerability in Arubanetworks Arubaos, published on 6 Oct 2022. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

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.

Weakness: CWE-120 (Buffer Copy without Checking Size of Input)

## Which versions are affected by CVE-2022-37888?

It affects 3 products.


Products: Arubanetworks Arubaos, Arubanetworks Instant, Siemens Scalance W1750d Firmware.

## How do I fix CVE-2022-37888?

No fix has been published for CVE-2022-37888 yet. Limit exposure of the affected software until one is available.

## Is CVE-2022-37888 being exploited?

There is no known exploitation of CVE-2022-37888 in the wild and no public exploit code.

## Other vulnerabilities in Arubanetworks Arubaos

- [CVE-2024-42393](https://insights.sbomify.com/CVE-2024-42393/): Memory corruption in Hpe Aruba Networking InstantOS and Aruba Access Points running ArubaOS 10 (critical 9.8)
- [CVE-2024-42394](https://insights.sbomify.com/CVE-2024-42394/): Memory corruption in HPE Aruba Networking InstantOS and Aruba Access Points running ArubaOS 10 (critical 9.8)
- [CVE-2024-42395](https://insights.sbomify.com/CVE-2024-42395/): Memory corruption in HPE Aruba Networking InstantOS and Aruba Access Points running ArubaOS 10 (critical 9.8)
- [CVE-2024-31466](https://insights.sbomify.com/CVE-2024-31466/): Unauthenticated Buffer Overflow Vulnerabilities in CLI Service Accessed by the PAPI Protocol (critical 9.8)
- [CVE-2024-31467](https://insights.sbomify.com/CVE-2024-31467/): Unauthenticated Buffer Overflow Vulnerabilities in CLI Service Accessed by the PAPI Protocol (critical 9.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2022-37888 and fix it if it is affected.

What it is: CVE-2022-37888 is a critical memory corruption vulnerability in Arubanetworks Arubaos, published on 6 Oct 2022. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2022-37888 in the wild and no public exploit code.

Affected product: Arubanetworks Arubaos. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2022-37888/ (Markdown: https://insights.sbomify.com/CVE-2022-37888/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2022-37888
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2022-37888
- OSV: https://osv.dev/vulnerability/CVE-2022-37888

---
From sbomify Insights: https://insights.sbomify.com/CVE-2022-37888/
Summaries are generated and may contain mistakes; the official description above is the record.