Hunspell 1.7.0 has an invalid read operation in SuggestMgr::leftcommonsubstring in suggestmgr.cxx. Reference: https://github.com/butterflyhack/hunspell-crash
Created hunspell tracking bugs for this issue: Affects: fedora-all [bug 1771027] Created mingw-hunspell tracking bugs for this issue: Affects: epel-7 [bug 1771029] Affects: fedora-all [bug 1771028]
Can't reproduce this yet, but I feel this can only happen with an empty .dic or near-empty .dic
See https://github.com/hunspell/hunspell/issues/624 for how to reproduce
https://github.com/hunspell/hunspell/commit/ac938e2ecb48ab4dd21298126c7921689d60571b
RHEL8 is compiled with -D_GLIBCXX_ASSERTIONS. The assertions always catch this case before we reach the out-of-bounds read and abort() the application.
Statement: This is unlikely to be an issue in a real world scenario, as it requires specially crafted Hunspell dictionaries, which are not shipped with Red Hat Enterprise Linux. Additionally, applications using Hunspell will likely filter out invalid input before passing it on, which further limits the impact.
This issue has been addressed in the following products: Red Hat Enterprise Linux 7 Via RHSA-2020:3971 https://access.redhat.com/errata/RHSA-2020:3971
This bug is now closed. Further updates for individual products will be reflected on the CVE page(s): https://access.redhat.com/security/cve/cve-2019-16707