Vulnerability in Eufy Homebase 2 before firmware (CVE-2023-37822)
Summary
Vulnerability in Eufy Homebase 2 before firmware (CVE-2023-37822). Confidential information can be exposed externally.
Original description
The description as published by the source.
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.
Source: NIST National Vulnerability Database NVD
Auto-generated summary
Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.
A vulnerability tracked as CVE-2023-37822 has been found in Eufy Homebase 2 before firmware.
Confidential information can be exposed externally. CVSS score: 8.2/10.
What to do: apply the vendor's official patched release.
If unsure, ask your IT team or search "Eufy Homebase 2 before firmware CVE-2023-37822" on the vendor's site.
CVE-2023-37822 (Eufy Homebase 2 before firmware) — CWE-331 / CVSS v3 8.2
Attack vector: adjacent-network / unauthenticated / no user interaction
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.
A vulnerability (CWE-331) exists in Eufy Homebase 2 before firmware.
Check the vendor advisory for the affected versions of Eufy Homebase 2 before firmware.
Severity: High (CVSS 8.2/10). Confidential information can be exposed externally.
Update to the patched release per vendor advisory.
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Audit SBOM/dependencies to find affected services.
Response actions
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
Audit SBOM/dependencies for affected components.資産台帳・SBOM・依存マニフェストで Eufy Homebase 2 before firmware を使っているサービスとバージョンを洗い出す。
-
2Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
References
- web cve@mitre.org
- web cve@mitre.org
- web cve@mitre.org