Skip to content
Fencer Intel
medium 6.5

CVE-2019-19698 json

marc-q libwav through 2017-04-20 has a NULL pointer dereference in wav_content_read() at libwav.c.

published 6y ago modified 4mo ago also EUVD-2019-9307

cvss
6.5
version 3.1, NVD
cisa kev
Not listed
not in CISA's catalog
epss
1.2%
EPSS 1.2% chance of exploitation in 30 days, percentile 67%
public exploits
0
none known

Summary

marc-q libwav through 2017-04-20 has a NULL pointer dereference in wav_content_read() at libwav.c.

Is CVE-2019-19698 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 Fencer

Exploit prediction

1.17% chance of exploitation in the next 30 days, higher than 67% of all scored CVEs (FIRST EPSS, 2026-11-09).

Exploits and checks

  • github.com https://github.com/marc-q/libwav/issues/25 referenced PoC, tagged "exploit" by a source, unverified
  • github.com https://github.com/xiaoxiongwang/security/tree/master/libwav referenced PoC, tagged "exploit" by a source, unverified

CVSS scores

assigned by version score vector
NVD 3.1 6.5 CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:N/A:H
NVD 2.0 4.3 AV:N/AC:M/Au:N/C:N/I:N/A:P

Classification

Weakness

References

Sources

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.