CVE-2018-14051 json
The function wav_read in libwav.c in libwav through 2017-04-20 has an infinite loop.
published 8y ago modified 4mo ago also EUVD-2018-5977
- cvss
- 7.5
- version 3.0, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 1.7%
- EPSS 1.7% chance of exploitation in 30 days, percentile 76%
- public exploits
- 0
- none known
Summary
The function wav_read in libwav.c in libwav through 2017-04-20 has an infinite loop.
Is CVE-2018-14051 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.
Check with FencerExploit prediction
1.66% chance of exploitation in the next 30 days, higher than 76% of all scored CVEs (FIRST EPSS, 2026-11-09).
Exploits and checks
- github.com https://github.com/marc-q/libwav/issues/21 referenced PoC, tagged "exploit" by a source, unverified
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 3.0 | 7.5 | CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H |
| NVD | 2.0 | 5.0 | AV:N/AC:L/Au:N/C:N/I:N/A:P |
Classification
- Weakness
-
- CWE-835 Loop with Unreachable Exit Condition
References
-
github.com
/marc-q/libwav/issues/21
exploit, third-party-advisory
-
github.com
/fouzhe/security/tree/master/libwav
third-party-advisory
Sources
- CVE List CVE-2018-14051
- NVD CVE-2018-14051
Fencer Intel 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.