# CVE-2023-37822: Weak cryptography in n/a

> Weak WPA2-PSK generation allows attackers to brute force the password and gain unauthorized access to the user's primary network.

- **Severity:** High 8.2 (`CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:C/C:H/I:L/A:N`)
- **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:** 3 Oct 2024
- **Updated:** 5 Jul 2026
- **Also known as:** GHSA-cr9c-949p-jxvr

## What is CVE-2023-37822?

CVE-2023-37822 is a high-severity vulnerability in n/a, published on 3 Oct 2024. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

The Eufy Homebase 2 before firmware version 3.3.4.1h creates a dedicated wireless network for its ecosystem, which serves as a proxy to the end user's primary network. The WPA2-PSK generation of this dedicated network is flawed and solely based on the serial number. Due to the flawed generation process, the WPA2-PSK can be brute forced offline within seconds. This vulnerability allows an attacker in proximity to the dedicated wireless network to gain unauthorized access to the end user's primary network. The only requirement of the attack is proximity to the dedicated wireless network.

Weakness: CWE-331 (Insufficient Entropy)

## Which versions are affected by CVE-2023-37822?

It affects 1 product.


Products: Eufy Homebase 2 Firmware.

## How do I fix CVE-2023-37822?

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

## Is CVE-2023-37822 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2023-37822 and fix it if it is affected.

What it is: CVE-2023-37822 is a high-severity vulnerability in n/a, published on 3 Oct 2024. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2023-37822 in the wild and no public exploit code.

Affected product: n/a. 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-2023-37822/ (Markdown: https://insights.sbomify.com/CVE-2023-37822/index.md)
```

## Sources

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

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