CVE-2020-36430: Libass Project vulnerability
Libass Project · Libass
Fixed in 0.15.1 · Affected: Libass Project before 0.15.1 · Exploitation: possible (1 to 10%)
Not in CyberSIXT coverage yet: no article names this CVE. This page shows the public record.
Higher than 65% of scored CVEs
Not scored yet. The CVE record carries no CVSS score.
DescriptionCVE.org
libass 0.15.x before 0.15.1 has a heap-based buffer overflow in decode_chars (called from decode_font and process_text) because the wrong integer data type is used for subtraction.
On the Atlas
Every published CVE is on the CyberSIXT Atlas, grouped by weakness, vendor and month.
- Exploitation
- Possible (1 to 10%). EPSS between 1% and 10%.
- CISA KEV
- Not listed
- Public check
- No public nuclei template
- Vendor
- Libass Project
- Published
- July 2021
CoverageNo articles yet
No CyberSIXT article names CVE-2020-36430 yet, so there is no coverage timeline, action brief or change log for it. Everything on this page comes from the public CVE record, CISA KEV, EPSS and the nuclei template index. Search the archive or see the CVEs in the news.
References
- NVD entrynvd.nist.gov
- CVE recordcve.org
- Weakness CWE-787cwe.mitre.org
- Vendor advisorylists.fedoraproject.org
- Vendor advisorysecurity.gentoo.org
- github.com/google/oss-fuzz-vulns/blob/main/vulns/libass/OSV-2020github.com
- bugs.chromium.org/p/oss-fuzz/issues/detail?id=26674bugs.chromium.org
- github.com/libass/libass/commit/017137471d0043e0321e377ed8da48e4github.com