Free and open · new CVEs checked every 20 minutesStatusRSSOpen dataContact

CVE-2020-36430: libass 0.15.x before 0.15.1 has a heap-based buffer overflow in decode_chars (called from decode_font and proc

44
This month
HIGH 7.8UPGRADEMITIGATE

CVE-2020-36430 is a high-severity flaw (CVSS 7.8) affecting libass, fedora. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.

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.

Why this priority

  • High severity

A fixed release or distro patch exists.

Risk facts

CVSS score7.8 (High)
Attack vectorLocal
Attack complexityLow
Privileges neededNone
User interactionRequired
EPSS exploit chance1.1% (top 35%)
CISA exploited listNo
WeaknessCWE-787
Published2021-07-20
Last modified2026-06-17
Publisher (CNA): MITRE · Vendor: fedoraproject · libass project

Share: LinkedIn · X · Reddit

Last updated 2026-06-17 · Sources: CVE Program, NVD, CISA KEV, EPSS and vendor advisories · How we score

Am I affected?

Timeline

libass project libass UPGRADE
Affected: >= 0.15.0 and < 0.15.1
Fixed in: 0.15.1
Safe to downgrade to: a release before 0.15.0
1. Check installed version
apt-cache policy libass || rpm -q libass || libass --version
2. UPGRADE to 0.15.1 (Debian / Ubuntu)
sudo apt update && sudo apt install --only-upgrade libass
2. UPGRADE (RHEL / Amazon Linux / Fedora)
sudo dnf upgrade libass
Note
Distros often backport fixes without changing the version number. Confirm with the distro advisory or changelog.
3. If no update is available yet, DOWNGRADE to a release before 0.15.0 (Debian / Ubuntu)
apt-cache madison libass sudo apt install libass=<VERSION_BEFORE_0.15.0> sudo apt-mark hold libass
3. If no update is available yet, DOWNGRADE (RHEL / Amazon Linux / Fedora)
dnf --showduplicates list libass sudo dnf downgrade libass-<VERSION_BEFORE_0.15.0> sudo dnf versionlock add libass
Downgrade risk
Downgrading can break dependent software and may reopen older bugs. Read the distro advisory first and test on a non-production host.
After downgrade
Restart the service, and keep the package held until a fixed release ships.
fedoraproject fedora MITIGATE
Affected: 34
Fixed in: no fixed release known
Safe to downgrade to: a release before 34
Check your OS release
cat /etc/os-release; uname -r
Debian / Ubuntu
sudo apt update && sudo apt full-upgrade
RHEL / Amazon Linux / Fedora
sudo dnf upgrade --refresh
Windows
Install the latest cumulative update from Windows Update
If no patch exists yet
OS downgrades are not safe. Apply the vendor mitigation from the advisory and restrict exposure.
Verify at the official source NVD · CVE Program · Report a problem with this page
Scores and fixes here are computed automatically from those and other public sources. Confirm with the vendor advisory before changing production systems.

Quick answers

How do I fix CVE-2020-36430?

libass: upgrade to 0.15.1; fedora: mitigate or apply the listed mitigation. Exact commands for each OS are on this page.

Is CVE-2020-36430 being exploited?

CVE-2020-36430 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

What does CVE-2020-36430 affect?

CVE-2020-36430 affects libass, fedora. Severity is high (CVSS 7.8). 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.

How urgent is CVE-2020-36430?

Priority 44/100. High severity

Related CVEs

References

← Back to latest CVEs

Get the weekly exploited-CVE digest by emailThe CVEs being attacked this week and how to fix them. No spam, unsubscribe any time.