Skip to content
Fencer Vulns
medium 6.5

CVE-2019-14372 json

In Libav 12.3, there is an infinite loop in the function wv_read_block_header() in the file wvdec.c.

published 2019-07-28 7 y ago modified 2026-06-17 4 mo ago also EUVD-2019-5585

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

Summary

In Libav 12.3, there is an infinite loop in the function wv_read_block_header() in the file wvdec.c.

Exploit prediction

1.13% chance of exploitation in the next 30 days, higher than 66% of all scored CVEs (FIRST EPSS, 2026-11-08).

Exploits and checks

  • bugzilla.libav.org https://bugzilla.libav.org/show_bug.cgi?id=1165 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
  • CWE-835 Loop with Unreachable Exit Condition

References

Sources

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.