CVE-2010-4666: Buffer Overflow
A number of flaws have been corrected in upstream libarchive that have not yet been included in a public release of libarchive (latest version is 2.8.4).
A buffer overflow at reading bit lengths of huffman code of LZX when reading a broken CAB file (CVE-2010-4666) [1].
Buffer overflows in various functions related to reading archives (in archivereadsupportformatiso9660.c) (CVE-2011-1777) [2].
Buffer overflow in reading tar archives (CVE-2011-1778) [3].
Use-after-free bugs (CVE-2011-1779) [4].
[1] http://code.google.com/p/libarchive/source/detail?r=2842 [2] http://code.google.com/p/libarchive/source/detail?r=3158 [3] http://code.google.com/p/libarchive/source/detail?r=3160 [4] http://code.google.com/p/libarchive/source/detail?r=3038
Other sources
Buffer overflow in libarchive 3.0 pre-release code allows remote attackers to cause a denial of service (application crash) or possibly have unspecified other impact via a crafted CAB file, which is not properly handled during the reading of Huffman code data within LZX compressed data.
Affected Software
Event History
Frequently Asked Questions
What is the severity of CVE-2010-4666?
CVE-2010-4666 has been assigned a moderate severity level due to its potential to cause a buffer overflow.
How do I fix CVE-2010-4666?
To mitigate CVE-2010-4666, upgrade to the latest version of libarchive that includes the patches for the identified vulnerabilities.
What types of systems are affected by CVE-2010-4666?
CVE-2010-4666 affects systems using libarchive version 3.0 on FreeBSD and other compatible platforms.
Is CVE-2010-4666 exploitable remotely?
CVE-2010-4666 could potentially be exploited remotely if a user is tricked into processing a malicious CAB file.
What kind of impact can CVE-2010-4666 have on my system?
CVE-2010-4666 can lead to a crash or arbitrary code execution due to the buffer overflow vulnerability.