CVE-2019-20016 json
libmysofa before 2019-11-24 does not properly restrict recursive function calls, as demonstrated by reports of stack consumption in readOHD…
published 2019-12-27 6 y ago modified 2026-06-17 4 mo ago also EUVD-2019-10572
- cvss
- 6.5
- 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 80%
- public exploits
- 0
- none known
Summary
libmysofa before 2019-11-24 does not properly restrict recursive function calls, as demonstrated by reports of stack consumption in readOHDRHeaderMessageDatatype in dataobject.c and directblockRead in fractalhead.c. NOTE: a download of v0.9 after 2019-12-06 should fully remediate this issue.
Patch / fix
- symonics libmysofa 0.9
- libmysofa Debian 14, Debian 13, Debian 12 0.9~dfsg0-1
debian advisories DEBIAN-CVE-2019-20016
- libmysofa Package Hub 15 SP2 0.9.1-bp152.4.3.1
- libmysofa openSUSE Leap 15.2 0.9.1-lp152.3.3.1
opensuse advisories openSUSE-SU-2021:0459-1openSUSE-SU-2021:0444-1
Exploit prediction
1.95% chance of exploitation in the next 30 days, higher than 80% of all scored CVEs (FIRST EPSS, 2026-11-08).
Exploits and checks
- github.com https://github.com/hoene/libmysofa/issues/83 referenced PoC, tagged "exploit" by a source, unverified
- github.com https://github.com/hoene/libmysofa/issues/84 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-787 Out-of-bounds Write
References
-
github.com
/hoene/libmysofa/commit/2e6fac6ab6156dae8e8c6f417741388084b70d6f
patch, third-party-advisory
-
github.com
/hoene/libmysofa/issues/83
exploit, third-party-advisory
-
github.com
/hoene/libmysofa/issues/84
exploit, third-party-advisory
Sources
- CVE List CVE-2019-20016
- NVD CVE-2019-20016
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.