Vulnerability Description
In hostapd 2.10 and earlier, the PKEX code remains active even after a successful PKEX association. An attacker that successfully bootstrapped public keys with another entity using PKEX in the past, will be able to subvert a future bootstrapping by passively observing public keys, re-using the encrypting element Qi and subtracting it from the captured message M (X = M - Qi). This will result in the public ephemeral key X; the only element required to subvert the PKEX association.
CVSS Score
MEDIUM
Affected Products
| Vendor | Product | Versions |
|---|---|---|
| W1.Fi | Hostapd | <= 2.10 |
Related Weaknesses (CWE)
References
- https://link.springer.com/article/10.1007/s10207-025-00988-3Third Party Advisory
- https://w1.fi/cgit/hostap/commit/?id=15af83cf1846870873a011ed4d714732f01cd2e4Patch
- https://lists.debian.org/debian-lts-announce/2025/04/msg00019.html
FAQ
What is CVE-2022-37660?
CVE-2022-37660 is a vulnerability with a CVSS score of 6.5 (MEDIUM). In hostapd 2.10 and earlier, the PKEX code remains active even after a successful PKEX association. An attacker that successfully bootstrapped public keys with another entity using PKEX in the past, w...
How severe is CVE-2022-37660?
CVE-2022-37660 has been rated MEDIUM with a CVSS base score of 6.5/10. Review the CVSS metrics above for detailed severity breakdown.
Is there a patch for CVE-2022-37660?
Check the references section above for vendor advisories and patch information. Affected products include: W1.Fi Hostapd.