CVE-2022-37660

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.

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.

En hostapd 2.10 y versiones anteriores, el código PKEX permanece activo incluso después de una asociación PKEX exitosa. Un atacante que haya iniciado con éxito claves públicas con otra entidad que usa PKEX en el pasado, podrá subvertir una futura iniciación observando pasivamente las claves públicas, reutilizando el elemento de cifrado Qi y restándolo del mensaje capturado M (X = M - Qi). Esto dará como resultado la clave pública efímera X; el único elemento necesario para subvertir la asociación PKEX.