CVE-2020-36430
Libass Project Libass vulnerability
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.
Affected products
Libass, Fedora. The exact versions are in the references.
What to do now
- Check your exposureFind out whether Libass Project Libass runs anywhere in your environment, including systems of suppliers.
- UpdateInstall the version in which the vendor fixed the vulnerability. The references lead to the advisory.
- Set the orderSystems that can be reached from the internet come first, then the rest.
References
- bugs.chromium.org/p/oss-fuzz/issues/detail?id=26674 · Patch
- github.com/libass/libass/commit/017137471d0043e0321e377ed8da48e45a3ec632 · Patch
- github.com/google/oss-fuzz-vulns/blob/main/vulns/libass/OSV-2020-2099.yaml · Third Party Advisory
- security.gentoo.org/glsa/202208-13 · Third Party Advisory
- lists.fedoraproject.org/archives/list/package-announce%40lists.fedoraproject.org/message/6
- nvd.nist.gov/vuln/detail/CVE-2020-36430
- cve.org/CVERecord?id=CVE-2020-36430
Data: CVE list and the NVD. This product uses data from the NVD API but is not endorsed or certified by the NVD.