CVE-2019-11578 json
auth.c in dhcpcd before 7.2.1 allowed attackers to infer secrets by performing latency attacks.
published 2019-04-28 7 y ago modified 2026-06-17 4 mo ago also EUVD-2019-3248
- cvss
- 5.9
- version 3.1, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 2.0%
- EPSS 2.0% chance of exploitation in 30 days, percentile 81%
- public exploits
- 0
- none known
Summary
auth.c in dhcpcd before 7.2.1 allowed attackers to infer secrets by performing latency attacks.
Patch / fix
Vendor advisories
What the vendors themselves say about their products: affected, fixed or not affected, and what to do.
red hat product security vex CVE-2019-11578 updated cvss 5.3
dhcpcd: information disclosure in auth.c
-
Red Hat All currently supported Red Hat productsnot affected: vulnerable code not present
Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf
Exploit prediction
2.04% chance of exploitation in the next 30 days, higher than 81% of all scored CVEs (FIRST EPSS, 2026-11-08).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 3.1 | 5.9 | CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:N/A:N |
| NVD | 2.0 | 4.3 | AV:N/AC:M/Au:N/C:P/I:N/A:N |
Classification
- Weakness
-
- CWE-203 Observable Discrepancy
References
-
roy.marples.name
/git/dhcpcd.git/commit/?id=7121040790b611ca3fbc400a1bbcd4364ef57233
patch, third-party-advisory
-
roy.marples.name
/git/dhcpcd.git/commit/?id=cfde89ab66cb4e5957b1c4b68ad6a9449e2784da
third-party-advisory
-
roy.marples.name
/git/dhcpcd.git/commit/?id=aee631aadeef4283c8a749c1caf77823304acf5e
patch, third-party-advisory
-
roy.marples.name
/archives/dhcpcd-discuss/0002415.html
third-party-advisory
-
securityfocus.com
/bid/108090
vdb-entry, third-party-advisory
Sources
- CVE List CVE-2019-11578
- NVD CVE-2019-11578
Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.