First published: Tue Feb 11 2025(Updated: )
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.
Credit: cve@mitre.org
Affected Software | Affected Version | How to fix |
---|---|---|
w1.fi hostapd | <=2.10 |
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
CVE-2022-37660 has a medium severity level as it allows attackers to potentially subvert secure bootstrapping processes.
To fix CVE-2022-37660, upgrade hostapd to version 2.11 or later which addresses this vulnerability.
CVE-2022-37660 allows an attacker to reuse previously bootstrapped public keys, compromising security in communications.
No, CVE-2022-37660 is not a concern for users who upgrade to hostapd version 2.11 or newer.
CVE-2022-37660 can facilitate man-in-the-middle attacks by enabling attackers to subvert secure PKEX associations.