Bugzilla – Bug 1166330
VUL-1: CVE-2019-20509: libarchive: insufficient validation of UTF-16 input by the LHA decoder can lead to a heap-based buffer over-read and application crash
Last modified: 2024-07-04 07:23:15 UTC
CVE-2019-20509 archive_read_support_format_lha.c in libarchive before 3.4.1 does not ensure valid sizes for UTF-16 input, which allows remote attackers to cause a denial of service (heap-based buffer over-read and application crash) via a crafted LHA archive. References: http://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2019-20509 http://people.canonical.com/~ubuntu-security/cve/2019/CVE-2019-20509.html https://github.com/libarchive/libarchive/issues/1284 https://github.com/libarchive/libarchive/compare/v3.4.0...v3.4.1 https://github.com/libarchive/libarchive/commit/91cf9372e89f7af4582964b15ceb7fc6d1b37471 http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-20509
SUSE:SLE-12:Update libarchive Affected SUSE:SLE-15:Update libarchive Affected Factory and SLE-15-SP2 are already fixed.
Created attachment 832516 [details] HeadOverflow1 (PoC LHA archive)
Created attachment 832517 [details] HeadOverflow2 (PoC LHA archive)
QA REPRODUCER: valgrind --tool=memcheck bsdtar -tf HeadOverflow1 Unfixed: Conditional jump or move depends on uninitialised value(s) at 0x4C34EE0: bcmp (in /usr/lib64/valgrind/vgpreload_memcheck-amd64-linux.so) by 0x560B08A: ??? (in /usr/lib64/libcrypto.so.1.1) by 0x560A235: FIPS_selftest (in /usr/lib64/libcrypto.so.1.1) by 0x560509C: ??? (in /usr/lib64/libcrypto.so.1.1) by 0x5618FE0: FIPS_mode_set (in /usr/lib64/libcrypto.so.1.1) by 0x551E16A: ??? (in /usr/lib64/libcrypto.so.1.1) by 0x400FBF9: call_init.part.0 (dl-init.c:72) by 0x400FD05: call_init (dl-init.c:119) by 0x400FD05: _dl_init (dl-init.c:120) by 0x4000ED9: ??? (in /lib64/ld-2.26.so) by 0x2: ??? by 0x1FFF0005A2: ??? by 0x1FFF0005A9: ??? [...] Fixed: ERROR SUMMARY: 0 errors from 0 contexts (suppressed: 0 from 0)
sle 12 is not affected, since libarchive 3.x had no UTF-16 support. Do you still need an update for SLE 15 SP0 or is SP2 enough?
This bug had been lost in the ether. (In reply to Adrian Schröter from comment #5) > sle 12 is not affected, since libarchive 3.x had no UTF-16 support. Thank you for checking. > Do you still need an update for SLE 15 SP0 or is SP2 enough? All good, thanks. SLE-12/libarchive: Not affected SLE-15/libarchive: EOL SLE-15-SP2/libarchive: Already fixed