# CVE-2022-37932: Auth bypass in Hewlett Packard Enterprise OfficeConnect 1820, 1850, and 1920S Network switches

> Remote attackers can bypass authentication on HPE OfficeConnect network switches, requiring firmware upgrades to mitigate.

- **Severity:** High 8.8 (`CVSS:3.1/AV:A/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:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 30 Nov 2022
- **Updated:** 24 Apr 2025
- **Also known as:** GHSA-gp8j-jhwq-pp4q

## What is CVE-2022-37932?

CVE-2022-37932 is a high-severity authentication bypass vulnerability in Hewlett Packard Enterprise OfficeConnect 1820, 1850, and 1920S Network switches, published on 30 Nov 2022. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

A potential security vulnerability has been identified in Hewlett Packard Enterprise OfficeConnect 1820, 1850, and 1920S Network switches. The vulnerability could be remotely exploited to allow authentication bypass. HPE has made the following software updates to resolve the vulnerability in Hewlett Packard Enterprise OfficeConnect 1820, 1850 and 1920S Network switches versions: Prior to PT.02.14; Prior to PC.01.22; Prior to PO.01.21; Prior to PD.02.22;

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

It affects 19 products.


Products: Hpe Officeconnect 1820 J9979a Firmware, Hpe Officeconnect 1820 J9980a Firmware, Hpe Officeconnect 1820 J9981a Firmware, Hpe Officeconnect 1820 J9982a Firmware, Hpe Officeconnect 1820 J9983a Firmware, Hpe Officeconnect 1820 J9984a Firmware, Hpe Officeconnect 1850 24g 2xgt Firmware, Hpe Officeconnect 1850 24g 2xgt Poe\+ Firmware, Hpe Officeconnect 1850 2xgt\/Spf\+ Firmware, Hpe Officeconnect 1850 48g 4xgt Firmware, Hpe Officeconnect 1850 48g 4xgt Poe\+ Firmware, Hpe Officeconnect 1850 6xgt Firmware, Hpe Officeconnect 1920s 24g 2sfp Firmware, Hpe Officeconnect 1920s 24g 2sfp Poe\+ Firmware, Hpe Officeconnect 1920s 24g 2sfp Ppoe\+ Firmware, Hpe Officeconnect 1920s 48g 4sfp Firmware, Hpe Officeconnect 1920s 48g 4sfp Ppoe\+ Firmware, Hpe Officeconnect 1920s 8g Firmware, Hpe Officeconnect 1920s 8g Ppoe\+ Firmware.

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

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

## Is CVE-2022-37932 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2022-37932 exists.

Public exploit code:

- https://github.com/Tim-Hoekstra/CVE-2022-37932 (github_poc): https://github.com/Tim-Hoekstra/CVE-2022-37932
- HP Switch - Authentication Bypass (nuclei): http/cves/2022/CVE-2022-37932.yaml

## Fix prompt for AI coding agents

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

What it is: CVE-2022-37932 is a high-severity authentication bypass vulnerability in Hewlett Packard Enterprise OfficeConnect 1820, 1850, and 1920S Network switches, published on 30 Nov 2022. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2022-37932 exists.

Affected product: Hewlett Packard Enterprise OfficeConnect 1820, 1850, and 1920S Network switches. 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-37932/ (Markdown: https://insights.sbomify.com/CVE-2022-37932/index.md)
```

## Sources

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

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