Critical severity · published Jan 27, 2020
CVE-2019-20433
libaspell.a in GNU Aspell before 0.60.8 has a buffer over-read for a string ending with a single '\0' byte, if the encoding is set to ucs-2 or ucs-4 outside of the application, as…
9.1
CVSS
1.7%
EPSS
No
On KEV
Description
libaspell.a in GNU Aspell before 0.60.8 has a buffer over-read for a string ending with a single '\0' byte, if the encoding is set to ucs-2 or ucs-4 outside of the application, as demonstrated by the ASPELL_CONF environment variable.
CVSS vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:H
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
None
Confidentiality
High
Integrity
None
Availability
High
Scope
Unchanged
Exploitation
Is it being used?
Exploit prediction (EPSS)1.7% · higher than 78% of CVEs
Exploited in the wildNo evidence yet
CISA KEVNot listed
Ransomware campaign useNot known
Affected products
Which versions
AS
Aspell · Gnu
before 0.60.8 · source: NVD
References
NVD
https://nvd.nist.gov/vuln/detail/CVE-2019-20433
CVE.org
https://www.cve.org/CVERecord?id=CVE-2019-20433
Vendor Advisory
http://aspell.net/buffer-overread-ucs.txt
More from Aspell
9.1
CVE-2019-17544
libaspell.a in GNU Aspell before 0.60.8 has a stack-based buffer over-read in acommon::unescape in common/getdata.cpp via an isolated \ character
7.8
CVE-2019-25051
objstack in GNU Aspell 0.60.8 has a heap-based buffer overflow in acommon::ObjStack::dup_top (called from acommon::StringMap::add and acommon::Config::lookup_list)
5.9
CVE-2026-103658
GNU Aspell 0.60.8.2 (first vulnerable version is not known) contains a heap-based buffer overflow write (CWE-122) in its read-only dictionary loader
1.8
CVE-2026-75820
Integer Truncation Leading to Heap Corruption in GNU Aspell
1.8
CVE-2026-75819
Out-of-bounds Read in GNU Aspell