Security Advisory

CVE-2019-9495: Dragonblood EAP-pwd Side Channel

Last updated:
  • CVE-2019-9495

CVE-2019-9495 is the Dragonblood cache side channel in the EAP-pwd code of hostapd and wpa_supplicant up to 2.7: an attacker who can run code on the same device can observe which path the password derivation takes and use it for an offline dictionary attack. Synology lists its RADIUS Server 3.0 package as affected.

Vulnerability summary

CVSS base score

3.7

Low severity

EPSS score (FIRST)

3.5%

Probability of exploitation in the wild in the next 30 days

CISA KEV catalog

No

Not listed

Published

Vulnerability ID: CVE-2019-9495 · Source: NVD

Affected components

ComponentCPEVersion range
hostapd and wpa_supplicant (w1.fi hostap project) with EAP-pwd supportcpe:2.3:a:w1.fi:hostapd:*:*:*:*:*:*:*:*up to and including 2.7 with CONFIG_EAP_PWD=y and EAP-pwd enabled at runtime; fixed in 2.8 (w1.fi 2019-2)
Synology RADIUS Server 3.0 packagecpe:2.3:a:synology:radius_server:3.0:*:*:*:*:*:*:*RADIUS Server 3.0; fixed with DSM 6.2.3-25426 or later (Synology-SA-19:16)

What does this mean for affected devices?

CVE-2019-9495 is the EAP-pwd member of the Dragonblood disclosure by Mathy Vanhoef and Eyal Ronen. NVD's record says the EAP-pwd implementations in hostapd and wpa_supplicant "are vulnerable to side-channel attacks as a result of cache access patterns", that "the ability to install and execute applications is necessary for a successful attack" and that "weak passwords may be cracked". NVD scores it 3.7 under CVSS v3.1, vector CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:N/A:N, with CWE-203 (observable discrepancy) as primary weakness; CERT/CC adds CWE-524 (NVD).

The w1.fi 2019-2 advisory, published 2019-04-10, explains why upstream treated the EAP-pwd code like the SAE code of CVE-2019-9494: EAP-pwd derives its password element with a similar loop, so the cache attack against SAE "would likely be applicable" here. The attacker must be "able to run unprivileged code on the victim machine", which "is not commonly the case on an authentication server (EAP server), so the most likely target for this would be a client device using EAP-pwd". The timing attack on MODP groups does not apply, because the hostap EAP-pwd code does not support MODP groups. The vulnerable configuration is any build with CONFIG_EAP_PWD=y and EAP-pwd enabled at runtime. The fix is a set of constant-time commits, listed under v2.8 in the hostapd ChangeLog; w1.fi later tightened the same code in its 2019-6 and 2022-1 advisories, the second of which is CVE-2022-23304.

The device angle comes from the coordinated disclosure. CERT/CC VU#871675 lists Synology as affected, and Synology's statement in that note gives a clear build-option example: DiskStation Manager and Synology Router Manager, including the RT1900ac, RT2600ac and MR2200ac routers, "ship OpenSSL version 1.0.2 and wpa_supplicant, but EAP-PWD (CONFIG_EAP_PWD) is not enabled and not compiled", while the RADIUS Server package "ships EAP-PWD module but the module is not enabled by default". Synology-SA-19:16 then lists RADIUS Server 3.0 as affected by CVE-2019-9495, CVE-2019-9497, CVE-2019-9498 and CVE-2019-9499 at low severity, fixed with DSM 6.2.3-25426 or later in its 2020-06-18 revision, and scores CVE-2019-9495 at 5.3 with an adjacent-network vector. FreeBSD-SA-19:03.wpa shipped the fix for the base system's hostapd and wpa_supplicant on 2019-05-14.

The CVE is not in the CISA KEV catalog as of 2026-11-17 (catalog version 2026.11.13), and FIRST EPSS gives it 0.03477, the 89.29th percentile, in the 2026-11-16 dataset (CISA KEV, FIRST EPSS). On an access point or RADIUS appliance that runs no third-party code, the attack is hard to mount; on an EAP-pwd client that runs apps, it matters more.

To fix it, ship hostapd and wpa_supplicant 2.8 or later, or backport the 2019-2 commits, build without CONFIG_EAP_PWD where EAP-pwd is not needed, and require strong passwords. Our hostapd and wpa_supplicant vulnerabilities guide shows how to find CONFIG_EAP_PWD and the version in an image, and our weak cryptography fix guide covers constant-time code in firmware. The EAP-pwd commit validation flaws of the same disclosure are CVE-2019-9497 and CVE-2019-9499.

How to fix this class of issueNo dedicated SoftWSP guide covers this weakness class; the fix is usually the vendor patch or firmware update referenced above. Our related guide explains how to plan and verify it: NIST SP 800-40 Rev. 4: enterprise patch management planning, explained.

Evidence

  • EAP-pwd in hostapd and wpa_supplicant leaks via cache access patterns; needs the ability to run applications; NVD CVSS v3.1 3.7 (AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:N/A:N), CWE-203 (NVD), CWE-524 (CERT/CC). — NVD
  • Needs unprivileged code on the victim, most likely an EAP-pwd client; MODP timing attack not applicable; CONFIG_EAP_PWD=y plus runtime EAP-pwd; fixed in v2.8. — w1.fi security advisory 2019-2
  • Synology statement: DSM and SRM (RT1900ac, RT2600ac, MR2200ac) ship wpa_supplicant without CONFIG_EAP_PWD; RADIUS Server package ships the EAP-pwd module, off by default. — CERT/CC VU#871675
  • Synology-SA-19:16: RADIUS Server 3.0 affected (low), fixed with DSM 6.2.3-25426 (revision 6, 2020-06-18); Synology CVSS 5.3. — Synology-SA-19:16
  • Not in the CISA KEV catalog as of 2026-11-17 (catalog version 2026.11.13). — CISA KEV
  • EPSS 0.03477 (89.29th percentile), dataset 2026-11-16, read 2026-11-17. — FIRST EPSS

Related advisories

Sources

  1. NVD
  2. w1.fi security advisory 2019-2: EAP-pwd side-channel attack
  3. CERT/CC VU#871675: WPA3 design issues and implementation vulnerabilities in hostapd and wpa_supplicant
  4. Synology-SA-19:16: Dragonblood
  5. FreeBSD-SA-19:03.wpa
  6. hostapd ChangeLog
  7. CISA KEV
  8. FIRST EPSS

Frequently asked questions

Does CVE-2019-9495 affect a router that only offers WPA2-Personal or WPA3-Personal?

Only if EAP-pwd is compiled in and enabled. The w1.fi 2019-2 advisory lists the vulnerable configuration as CONFIG_EAP_PWD=y in the build plus EAP-pwd enabled at runtime. Synology, for example, told CERT/CC that its routers ship wpa_supplicant without CONFIG_EAP_PWD, so only its RADIUS Server package was listed.

Who can exploit CVE-2019-9495?

An attacker who can run unprivileged code on the device that performs EAP-pwd and observe the shared CPU cache. Upstream says this is not common on an authentication server, so the most likely target is a client device that uses EAP-pwd. A strong password still defeats the offline dictionary step.

Which version fixes CVE-2019-9495?

hostapd and wpa_supplicant 2.8, released 2019-04-21, include the constant-time EAP-pwd commits; w1.fi also published the commits for older releases. Synology fixed RADIUS Server 3.0 with DSM 6.2.3-25426 (per Synology-SA-19:16).

Is CVE-2019-9495 in the CISA KEV catalog?

No, not as of 2026-11-17 (catalog version 2026.11.13). FIRST EPSS gives it 0.03477, the 89.29th percentile, in the 2026-11-16 dataset (per CISA KEV and FIRST EPSS).