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.
Product
libass project libass vulnerabilities
6 published CVES affecting libass project libass, from public sources (CVE.org, NVD, CISA KEV, FIRST EPSS, OSV).
- Total
- 6
- Critical
- 0
- High
- 6
- Medium
- 0
- Low
- 0
- Unscored
- 0
- CISA KEV
- 0
Latest libass project libass CVEs
Newest publication first
-
HighCVSS 7.8 EPSS 1.1%
-
HighCVSS 8.8 EPSS 2.7%
Stack overflow in the parse_tag function in libass/ass_parse.c in libass before 0.15.0 allows remote attackers to cause a denial of service or remote code execution via a crafted file.
-
HighCVSS 8.8 EPSS 1.8%
In libass 0.14.0, the ass_outline_construct's call to outline_stroke causes a signed integer overflow.
-
HighCVSS 7.5 EPSS 5.2%
The check_allocations function in libass/ass_shaper.c in libass before 0.13.4 allows remote attackers to cause a denial of service (memory allocation failure) via unspecified vectors.
-
HighCVSS 7.5 EPSS 4.7%
Buffer overflow in the calc_coeff function in libass/ass_blur.c in libass before 0.13.4 allows remote attackers to cause a denial of service via unspecified vectors.
-
HighCVSS 7.5 EPSS 4.3%
The wrap_lines_smart function in ass_render.c in libass before 0.13.4 allows remote attackers to cause a denial of service (out-of-bounds read) via unspecified vectors, related to "0/3 line wrapping equalization."
Sources: CVE.org, NVD, CISA KEV, FIRST EPSS, OSV and public exploit-reference metadata. Product matching comes from the published CVE records. A proof-of-concept means public code exists; it is not evidence of exploitation.