CVE-2019-13377: The implementations of SAE and EAP-pwd in hostapd and wpa_supplicant 2.x through 2.8 are vulnerable to side-channel attacks as a result of o
Noroxi assessment
Priority: Monitor (action score 24/100)
- The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
- Probability of exploitation in the next 30 days: 2.5% (FIRST EPSS); higher than 84.8% of all records.
- Anyone who can reach it over the internet can trigger it. No account or password is required. No user action is required. Special conditions such as timing or configuration are required.
- Fixed version: hostapd (Alpine:v3.10) 2.8-r1; wpa_supplicant (Alpine:v3.10) 2.8-r2; hostapd (Alpine:v3.9) 2.7-r4.
Low priority for now. Upgrade to hostapd (Alpine:v3.10) 2.8-r1; wpa_supplicant (Alpine:v3.10) 2.8-r2; hostapd (Alpine:v3.9) 2.7-r4 or later.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
Primary sources: NVD · CVE.org · FIRST EPSS
The implementations of SAE and EAP-pwd in hostapd and wpa_supplicant 2.x through 2.8 are vulnerable to side-channel attacks as a result of observable timing differences and cache access patterns when Brainpool curves are used. An attacker may be able to gain leaked information from a side-channel attack that can be used for full password recovery.
- Published
- Aug 15, 2019
- Updated
- Jun 16, 2026
- EPSS
- 2.5% · 84th percentile
- CWE
- CWE-203
Report tools
Action score
24
Monitor
Low priority for now.
- CVSS
- 23 / 40 · 5.9 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 1 / 30 · 2.5%
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- No public exploit code on record
- A fix has been released
If any of these changes, we'll tell you in the daily email digest.
Running WordPress? Scan your site free with WP Lens
Noroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
| Vendor | Product | CPE |
|---|---|---|
| w1.fi | hostapd | cpe:2.3:a:w1.fi:hostapd |
| fedoraproject | fedora | cpe:2.3:o:fedoraproject:fedora |
| canonical | ubuntu linux | cpe:2.3:o:canonical:ubuntu_linux |
| debian | debian linux | cpe:2.3:o:debian:debian_linux |
Affected versions
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- canonical ubuntu linux18.04
- canonical ubuntu linux19.04
- debian debian linux10.0
- fedoraproject fedora30
- w1.fi hostapd2.0 and later · up to 2.8 inclusive
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| Alpine:v3.10 | hostapd | from 2.0 · before 2.8-r1 | 2.8-r1 |
| Alpine:v3.10 | wpa_supplicant | before 2.8-r2 | 2.8-r2 |
| Alpine:v3.9 | hostapd | from 2.0 · before 2.7-r4 | 2.7-r4 |
| Alpine:v3.9 | wpa_supplicant | before 2.7-r4 | 2.7-r4 |
| Debian:10 | wpa | before 2:2.7+git20190128+0c1e29f-6+deb10u1 | 2:2.7+git20190128+0c1e29f-6+deb10u1 |
| Debian:12 | wpa | before 2:2.9-1 | 2:2.9-1 |
| openSUSE:Leap 15.1 | wpa_supplicant | before 2.9-lp151.5.10.1 | 2.9-lp151.5.10.1 |
| openSUSE:Leap 15.2 | wpa_supplicant | before 2.9-lp152.8.3.1 | 2.9-lp152.8.3.1 |
| openSUSE:Tumbleweed | wpa_supplicant | before 2.9-13.4 | 2.9-13.4 |
| SUSE:HPE Helion OpenStack 8 | wpa_supplicant | before 2.9-15.22.1 | 2.9-15.22.1 |
| SUSE:Linux Enterprise Module for Basesystem 15 SP1 | wpa_supplicant | before 2.9-4.20.1 | 2.9-4.20.1 |
| SUSE:Linux Enterprise Server 12 SP5 | wpa_supplicant | before 2.9-23.3.1 | 2.9-23.3.1 |
Same product
w1.fi: all recordsOther highest-scoring records for the same primary product.
- CVE-2022-23304The implementations of EAP-pwd in hostapd before 2.10 and wpa_supplicant before 2.10 are vulnerable to side-channel attacks as a result of c40Plan
- CVE-2022-23303The implementations of SAE in hostapd before 2.10 and wpa_supplicant before 2.10 are vulnerable to side channel attacks as a result of cache40Plan
- CVE-2019-9499The implementations of EAP-PWD in wpa_supplicant EAP Peer do not validate the scalar and element values in EAP-pwd-Commit33Monitor
Published before and after this one in the same product
- ← EarlierCVE-2019-9498Apr 17, 2019 · The implementations of EAP-PWD in hostapd EAP Server do not validate the scalar and element values in EAP-pwd-Commit33Monitor
- ← EarlierCVE-2019-11555Apr 26, 2019 · The EAP-pwd implementation in hostapd (EAP server) before 2.8 and wpa_supplicant (EAP peer) before 2.8 does not validate fragmentation reass24Monitor
- Later →CVE-2019-16275Sep 12, 2019 · hostapd before 2.10 and wpa_supplicant before 2.10 allow an incorrect indication of disconnection in certain situations because source addre26Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| alpine:hostapd | 2.8-r1 · Alpine:v3.10 | Package registry (OSV) |
| alpine:wpa_supplicant | 2.8-r2 · Alpine:v3.10 | Package registry (OSV) |
| debian:wpa | 2:2.9-1 · Debian:12 | Package registry (OSV) |
| opensuse:wpa_supplicant | 2.9-lp151.5.10.1 · openSUSE:Leap 15.1 | Package registry (OSV) |
| suse:wpa_supplicant | 2.9-4.20.1 · SUSE:Linux Enterprise Module for Basesystem 15 SP1 | Package registry (OSV) |
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
No dated events beyond publication.
FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).
Patch and commit links
Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.
Credits
All researchersFinders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.
No credits in the CNA record.
Variant candidates
Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.
No nightly-computed relations.
Chain candidates
An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.
—
Bug bounty scope
No known public program.
Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).
Technical details
Attack conditions
- Anyone who can reach it over the internet can trigger it.
- No account or password is required.
- No user action is required.
- Special conditions such as timing or configuration are required.
If successful
- Confidentiality
- high · data can be read
- Integrity
- none
- Availability
- none
- Attack vector
- Network
- Attack complexity
- High
- Privileges required
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality impact
- High
- Integrity impact
- None
- Availability impact
- None
Weakness class (CWE)
CWE-203 · Observable DiscrepancyCVSS vector
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:N/A:N
nvd-primary
Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
Attack patterns (CAPEC)
ATT&CK techniques
—
Change log
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (5 more)Show less
Vendor advisories and official records. Exploit/PoC links are deliberately left out.