CVE-2020-26682
published 2020-10-16CVE-2020-26682: In libass 0.14.0, the `ass_outline_construct`'s call to `outline_stroke` causes a signed integer overflow.
PriorityP341high8.8CVSS 3.1
AVNACLPRNUIRSUCHIHAH
EPSS
1.80%
78.4th percentile
In libass 0.14.0, the `ass_outline_construct`'s call to `outline_stroke` causes a signed integer overflow.
Affected
7 ranges
| Vendor | Product | Version range | Fixed in |
|---|---|---|---|
| debian | libass | < libass 1:0.15.0-1 (bookworm) | libass 1:0.15.0-1 (bookworm) |
| libass_project | libass | — | — |
| libass_project | libass | >= 0 < 1:0.15.0-1 | 1:0.15.0-1 |
| libass_project | libass | >= 0 < 1:0.15.0-1 | 1:0.15.0-1 |
| libass_project | libass | >= 0 < 1:0.15.0-1 | 1:0.15.0-1 |
| libass_project | libass | >= 0 < 1:0.15.0-1 | 1:0.15.0-1 |
| ubuntu | libass | — | — |
CVSS provenance
nvdv3.18.8HIGHCVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H
nvdv2.06.8MEDIUMAV:N/AC:M/Au:N/C:P/I:P/A:P
osv8.8HIGH
vendor_debian8.8HIGH
vendor_ubuntu8.8HIGH
Stop checking back — get the weekly exploitation signal.
Every Monday: what got weaponized or added to CISA KEV in the last seven days — each CVE cross-linked to its PoC, Nuclei template, and detection rule. Free, one email a week, unsubscribe in one click.
Ubuntu
libass vulnerabilities
vendor_ubuntu·2026-09-24·CVSS 8.8
CVE-2020-26682 [HIGH] libass vulnerabilities
Title: libass vulnerabilities
Summary: Several security issues were fixed in libass.
It was discovered that libass incorrectly handled parsing operations for
specific nested character strings. An attacker could use this issue to
cause libass to crash, resulting in a denial of service, or possibly
execute arbitrary code. This issue only affected Ubuntu 14.04 LTS,
Ubuntu 16.04 LTS, Ubuntu 18.04 LTS and Ubuntu 20.04 LTS.
(CVE-2020-24994)
It was discovered that libass incorrectly handled certain outline
processing operations. An attacker could use this issue to cause libass
to crash, resulting in a denial of service. This issue only affected
Ubuntu 18.04 LTS and Ubuntu 20.04 LTS. (CVE-2020-26682)
It was discovered that libass incorrectly handled certain ASS subtitle
files when measuring wr
Debian
CVE-2020-26682: libass - In libass 0.14.0, the `ass_outline_construct`'s call to `outline_stroke` causes ...
vendor_debian·2020·CVSS 8.8
CVE-2020-26682 [HIGH] CVE-2020-26682: libass - In libass 0.14.0, the `ass_outline_construct`'s call to `outline_stroke` causes ...
In libass 0.14.0, the `ass_outline_construct`'s call to `outline_stroke` causes a signed integer overflow.
Scope: local
bookworm: resolved (fixed in 1:0.15.0-1)
bullseye: resolved (fixed in 1:0.15.0-1)
forky: resolved (fixed in 1:0.15.0-1)
sid: resolved (fixed in 1:0.15.0-1)
trixie: resolved (fixed in 1:0.15.0-1)
GHSA
GHSA-87rf-m79q-qqqf: In libass 0
ghsa_unreviewed·2022-05-24
CVE-2020-26682 [HIGH] CWE-190 GHSA-87rf-m79q-qqqf: In libass 0
In libass 0.14.0, the `ass_outline_construct`'s call to `outline_stroke` causes a signed integer overflow.
OSV
CVE-2020-26682: In libass 0
osv·2020-10-16·CVSS 8.8
CVE-2020-26682 [HIGH] CVE-2020-26682: In libass 0
In libass 0.14.0, the `ass_outline_construct`'s call to `outline_stroke` causes a signed integer overflow.
No detection rules found.
No public exploits indexed.
Bugzilla
CVE-2020-26682 libass: in`ass_outline_construct`'s call to `outline_stroke` a signed integer overflow could result in undefined behaviour
bugzilla·2020-10-01·CVSS 8.8
CVE-2020-26682 [HIGH] CVE-2020-26682 libass: in`ass_outline_construct`'s call to `outline_stroke` a signed integer overflow could result in undefined behaviour
CVE-2020-26682 libass: in`ass_outline_construct`'s call to `outline_stroke` a signed integer overflow could result in undefined behaviour
In `ass_outline_construct`'s call to `outline_stroke` a signed integer
overflow happens leading to undefined behaviour.
Discussion:
External References:
https://github.com/libass/libass/issues/431
https://github.com/libass/libass/pull/432
---
Created libass tracking bugs for this issue:
Affects: epel-all [bug 1884109]
Affects: fedora-all [bug 1884108]
---
This CVE Bugzilla entry is for community support informational purposes only as it does not affect a package in a commercially supported Red Hat product. Refer to the dependent bugs for status of those individual community products.
Bugzilla
CVE-2020-26682 libass: in`ass_outline_construct`'s call to `outline_stroke` a signed integer overflow could result in undefined behaviour [epel-all]
bugzilla·2020-10-01·CVSS 8.8
CVE-2020-26682 [HIGH] CVE-2020-26682 libass: in`ass_outline_construct`'s call to `outline_stroke` a signed integer overflow could result in undefined behaviour [epel-all]
CVE-2020-26682 libass: in`ass_outline_construct`'s call to `outline_stroke` a signed integer overflow could result in undefined behaviour [epel-all]
This is an automatically created tracking bug! It was created to ensure
that one or more security vulnerabilities are fixed in affected versions
of epel-all.
For comments that are specific to the vulnerability please use bugs filed
against the "Security Response" product referenced in the "Blocks" field.
For more information see:
http://fedoraproject.org/wiki/Security/TrackingBugs
When submitting as an update, use the fedpkg template provided in the next
comment(s). This will include the bug IDs of this tracking bug as well as
the relevant top-level CVE bugs.
Please also mention the CVE IDs being fixed in the RPM changelog and the
fedpkg
Bugzilla
CVE-2020-26682 libass: in`ass_outline_construct`'s call to `outline_stroke` a signed integer overflow could result in undefined behaviour [fedora-all]
bugzilla·2020-10-01·CVSS 8.8
CVE-2020-26682 [HIGH] CVE-2020-26682 libass: in`ass_outline_construct`'s call to `outline_stroke` a signed integer overflow could result in undefined behaviour [fedora-all]
CVE-2020-26682 libass: in`ass_outline_construct`'s call to `outline_stroke` a signed integer overflow could result in undefined behaviour [fedora-all]
This is an automatically created tracking bug! It was created to ensure
that one or more security vulnerabilities are fixed in affected versions
of fedora-all.
For comments that are specific to the vulnerability please use bugs filed
against the "Security Response" product referenced in the "Blocks" field.
For more information see:
http://fedoraproject.org/wiki/Security/TrackingBugs
When submitting as an update, use the fedpkg template provided in the next
comment(s). This will include the bug IDs of this tracking bug as well as
the relevant top-level CVE bugs.
Please also mention the CVE IDs being fixed in the RPM changelog and the
fed
http://www.openwall.com/lists/oss-security/2020/11/19/7https://github.com/libass/libass/issues/431https://github.com/libass/libass/pull/432https://security.gentoo.org/glsa/202012-12http://www.openwall.com/lists/oss-security/2020/11/19/7https://github.com/libass/libass/issues/431https://github.com/libass/libass/pull/432https://security.gentoo.org/glsa/202012-12
2020-10-16
Published