Security Advisory

CVE-2019-9499: EAP-pwd Peer Authentication Bypass

Last updated:
  • CVE-2019-9499

CVE-2019-9499 is a Dragonblood flaw in the wpa_supplicant EAP-pwd client up to 2.7: it accepts invalid commit values, so with a crypto library that skips elliptic-curve point checks, such as OpenSSL 1.0.2, LibreSSL or wolfSSL, a rogue access point can authenticate the device, learn its session key and control its traffic.

Vulnerability summary

CVSS base score

8.1

High severity

EPSS score (FIRST)

2.2%

Probability of exploitation in the wild in the next 30 days

CISA KEV catalog

No

Not listed

Published

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

Affected components

ComponentCPEVersion range
wpa_supplicant (w1.fi hostap project) EAP peer with EAP-pwd supportcpe:2.3:a:w1.fi:wpa_supplicant:*:*:*:*:*:*:*:*up to and including 2.7 with CONFIG_EAP_PWD=y, EAP-pwd enabled and a crypto library without EC point validation (OpenSSL 1.0.2 or older, LibreSSL, wolfSSL); fixed in 2.8 (w1.fi 2019-4)
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-9499 is the client-side EAP-pwd commit validation flaw of the Dragonblood disclosure. NVD's record says the EAP-pwd implementation in the wpa_supplicant EAP peer, "when built against a crypto library missing explicit validation on imported elements", does not validate the scalar and element values in EAP-pwd-Commit, so "an attacker may complete authentication, session key and control of the data connection with a client". NVD scores it 8.1 under CVSS v3.1, vector CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H, with CWE-287 as primary weakness; CERT/CC adds CWE-346 (NVD).

The w1.fi 2019-4 advisory, published 2019-04-10, explains that crafted commit values can force the derived key into "a very small set of possible values". Upstream calls the attack against the peer "slightly more complex" but still practical, and its result is "the attacker being able to operate a rogue AP". Whether a build is vulnerable depends on the crypto library: "OpenSSL v1.0.2 or older: vulnerable", "OpenSSL v1.1.0 or newer: not vulnerable", BoringSSL without commit 38feb990a183 vulnerable, and "LibreSSL: vulnerable" and "wolfssl: vulnerable". The fix is two commits, "EAP-pwd client: Verify received scalar and element" and "EAP-pwd: Check element x,y coordinates explicitly", listed under v2.8 (2019-04-21) in the wpa_supplicant ChangeLog. The server-side counterparts are CVE-2019-9497 (reflection) and CVE-2019-9498.

The device angle is embedded clients, where OpenSSL 1.0.2 and wolfSSL stayed common long after 2019. Synology's statement in CERT/CC VU#871675 is a worked example of the build-option check: its DSM and SRM firmware, 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", so the vulnerable library is present and the vulnerable code is not. Synology-SA-19:16 lists only its RADIUS Server 3.0 package as affected by CVE-2019-9499 and the related EAP-pwd CVEs, at low severity, fixed with DSM 6.2.3-25426 or later, and scores CVE-2019-9499 at 5.3. In the same CERT/CC note, OpenSSL said it was backporting a commit to 1.0.2 to protect applications that do not validate elliptic-curve points themselves. FreeBSD-SA-19:03.wpa fixed the base system's 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.02215, the 82.92nd percentile, in the 2026-11-16 dataset (CISA KEV, FIRST EPSS). Treat it as high on an EAP-pwd client on wpa_supplicant 2.7 or older linked against OpenSSL 1.0.2, LibreSSL or wolfSSL, and as not applicable where EAP-pwd is not compiled in.

To fix it, ship wpa_supplicant 2.8 or later, or backport the 2019-4 commits, and update the crypto library. Upstream's wpa_supplicant defconfig enables CONFIG_EAP_PWD, so check the build configuration rather than assuming it is off. Our hostapd and wpa_supplicant vulnerabilities guide shows how to read the build options and version in an image, our Mbed TLS and wolfSSL guide and OpenSSL guide cover finding the library version, and the EAP-pwd side channel of the same disclosure is CVE-2019-9495.

How to fix this class of issueThis advisory's weakness class is Authentication bypass. Our practical guide covers how to detect, fix, verify and disclose it: How to fix authentication bypass in embedded firmware.

Evidence

  • wpa_supplicant EAP peer, with a crypto library missing element validation, does not validate EAP-pwd-Commit values; NVD CVSS v3.1 8.1 (AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H), CWE-287 (NVD), CWE-346 (CERT/CC). — NVD
  • Attack against the peer practical; rogue AP; library list (OpenSSL 1.0.2 or older, LibreSSL, wolfSSL vulnerable; OpenSSL 1.1.0 or newer not); fix commits; v2.8. — w1.fi security advisory 2019-4
  • wpa_supplicant ChangeLog v2.8: EAP-pwd verify server scalar/element (CVE-2019-9499). — wpa_supplicant ChangeLog
  • Synology statement: DSM and SRM ship OpenSSL 1.0.2 and wpa_supplicant without CONFIG_EAP_PWD; OpenSSL backporting commit 1e2012b to 1.0.2 for EC point validation. — CERT/CC VU#871675
  • Synology-SA-19:16: RADIUS Server 3.0 affected (low), fixed with DSM 6.2.3-25426; 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.02215 (82.92nd percentile), dataset 2026-11-16, read 2026-11-17. — FIRST EPSS

Related advisories

Sources

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

Frequently asked questions

Which crypto libraries make CVE-2019-9499 exploitable?

The w1.fi 2019-4 advisory lists OpenSSL 1.0.2 or older, LibreSSL, wolfSSL and BoringSSL without commit 38feb990a183 as vulnerable, and OpenSSL 1.1.0 or newer as not vulnerable, because the newer library rejects invalid elliptic-curve points on import.

What can an attacker do with CVE-2019-9499?

Operate a rogue access point. With crafted EAP-pwd-Commit values the attacker completes authentication with the client and learns the session key, which, in NVD's words, gives control of the data connection with the client.

Is a device with OpenSSL 1.0.2 and wpa_supplicant automatically affected?

No. EAP-pwd must be compiled in and enabled. Synology told CERT/CC that its DSM and SRM firmware ship OpenSSL 1.0.2 and wpa_supplicant but do not compile CONFIG_EAP_PWD, so those devices were not affected (per CERT/CC VU#871675).

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

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