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.

Published: 2025-02-11 Last update: 2025-11-03 Assigner: [email protected] Source: [email protected]
NVD Status：Modified，CVE State: published
View at NVD, CVE.org, EUVD

CVE-2022-37660 is rated Low Risk (39.7/100): CVSS Medium severity, with low exploitation likelihood (EPSS 0.18%). Monitor for updates and reassess as exploit intelligence or EPSS changes.

Risk is dynamic; we continuously reassess and refresh what is shown on this page as upstream context changes.

Exploit prediction scoring system (EPSS) score for CVE-2022-37660

EPSS lead: Daily EPSS estimates relative likelihood of exploitation; percentile ranks this CVE among scored vulnerabilities (higher = more severe relative rank).

# Date Old EPSS score New EPSS score Delta (New - Old)
1 2026-04-19 0.15% 0.18% +0.03%
2 2026-03-23 0.31% 0.15% -0.16%
3 2026-03-22 — 0.31% —

Full EPSS history (6 records total)

Common vulnerability scoring system (CVSS) metrics for CVE-2022-37660

CVSS metrics for this CVE.

Base score Version Severity Vector Exploitability Impact Score source
6.5 3.1 MEDIUM
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:N Click to expand
Attack vector (AV:N)
Could be attacked over the internet or any normal routed network—not just someone sitting at the machine.
Attack complexity (AC:L)
Once they can reach the bug, pulling it off is straightforward—no weird race conditions or rare setup.
Privileges required (PR:N)
No account or special rights needed—anonymous or random user is enough.
User interaction (UI:N)
Nobody has to click “OK” or open a trap file; it can work without a victim helping.
Scope (S:U)
Damage stays in the same “trust bubble” as the broken component—no big spill into unrelated systems.
Confidentiality (C:L)
Some sensitive info could get out, but not a total data dump.
Integrity (I:L)
Attackers could change some data, but it’s limited—not everything goes.
Availability (A:N)
Service keeps running; no real outage angle.
 3.9 2.5 134c704f-9b21-4f2e-91b3-4a467353bcc0

Weakness enumeration for CVE-2022-37660

OS Trackers for CVE-2022-37660

vendor priority summary link
alpine — CVE-2022-37660: 1 source package rows (hostapd); 2 state rows across 2 repos (3.19-main, 3.20-main); fixed 0, open 2. https://security.alpinelinux.org/vuln/CVE-2022-37660
debian not yet assigned CVE-2022-37660 not yet assigned priority: Debian including 1 source packages (wpa), 5 status rows across 5 suites (bookworm, bullseye, forky, sid, trixie): resolved 5. https://security-tracker.debian.org/tracker/CVE-2022-37660
redhat high — https://access.redhat.com/security/cve/CVE-2022-37660
ubuntu medium CVE-2022-37660 medium priority: Ubuntu including 1 source packages (wpa), 8 status rows across 8 suites (bionic, focal, jammy, noble, oracular, trusty, upstream, xenial): released 5, not-affected 3. https://ubuntu.com/security/CVE-2022-37660

Affected software / configurations for CVE-2022-37660

Vendor Product Version Raw CPE
w1.fi hostapd <= 2.10 cpe:2.3:a:w1.fi:hostapd:*:*:*:*:*:*:*:*

References for CVE-2022-37660

cvelogic Threat Intelligence