CVE-2020-36428 json
matio (aka MAT File I/O Library) 1.5.18 through 1.5.21 has a heap-based buffer overflow in ReadInt32DataDouble (called from ReadInt32Data a…
published 2021-07-20 5 y ago modified 2026-06-17 4 mo ago also EUVD-2020-23956
- cvss
- 8.8
- version 3.1, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 1.4%
- EPSS 1.4% chance of exploitation in 30 days, percentile 72%
- public exploits
- 0
- none known
Summary
matio (aka MAT File I/O Library) 1.5.18 through 1.5.21 has a heap-based buffer overflow in ReadInt32DataDouble (called from ReadInt32Data and Mat_VarRead4).
Patch / fix
- libmatio Debian 14, Debian 13, Debian 12 1.5.22-1
debian advisories DEBIAN-CVE-2020-36428
- matio openSUSE Tumbleweed 1.5.23-1.1
- matio Package Hub 15 SP4, openSUSE Leap 15.4 1.5.23-bp154.2.3.1
opensuse advisories openSUSE-SU-2024:12079-1openSUSE-SU-2022:10235-1
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-2020-36428 updated cvss 5.3
matio: heap-based buffer overflow in ReadInt32DataDouble
-
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
1.39% chance of exploitation in the next 30 days, higher than 72% of all scored CVEs (FIRST EPSS, 2026-11-08).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 3.1 | 8.8 | CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H |
| NVD | 2.0 | 6.8 | AV:N/AC:M/Au:N/C:P/I:P/A:P |
Classification
- Weakness
-
- CWE-787 Out-of-bounds Write
References
-
bugs.chromium.org
/p/oss-fuzz/issues/detail?id=21421
third-party-advisory
-
github.com
/google/oss-fuzz-vulns/blob/main/vulns/matio/OSV-2020-799.yaml
third-party-advisory
Sources
- CVE List CVE-2020-36428
- NVD CVE-2020-36428
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.