CVE-2020-36430
Published: 20 July 2021
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.
Notes
Author | Note |
---|---|
ccdm94 |
introduced by commit 910211f. |
Priority
Status
Package | Release | Status |
---|---|---|
libass
Launchpad, Ubuntu, Debian |
bionic |
Not vulnerable
(code not present)
|
focal |
Not vulnerable
(code not present)
|
|
groovy |
Ignored
(end of life)
|
|
hirsute |
Ignored
(end of life)
|
|
impish |
Not vulnerable
(1:0.15.0-2)
|
|
jammy |
Not vulnerable
(1:0.15.2-1)
|
|
trusty |
Not vulnerable
(code not present)
|
|
upstream |
Released
(0.15.1, 1:0.15.0-2)
|
|
xenial |
Not vulnerable
(code not present)
|
|
Patches:
upstream: https://github.com/libass/libass/commit/017137471d0043e0321e377ed8da48e45a3ec632 |
Severity score breakdown
Parameter | Value |
---|---|
Base score | 7.8 |
Attack vector | Local |
Attack complexity | Low |
Privileges required | None |
User interaction | Required |
Scope | Unchanged |
Confidentiality | High |
Integrity impact | High |
Availability impact | High |
Vector | CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H |