First published: Thu Jun 16 2016(Updated: )
A cpio archive with a ridiculously large symlink can cause memory allocation to fail, resulting in any attempt to view or extract the archive crashing. The failed allocation appears to be handled correctly within libarchive and not lead to further issues. External references: <a href="https://github.com/libarchive/libarchive/issues/705">https://github.com/libarchive/libarchive/issues/705</a> Upstream fix: <a href="https://github.com/libarchive/libarchive/commit/fd7e0c02">https://github.com/libarchive/libarchive/commit/fd7e0c02</a>
Credit: cve@mitre.org
Affected Software | Affected Version | How to fix |
---|---|---|
redhat/libarchive | <3.2.1 | 3.2.1 |
Redhat Enterprise Linux Desktop | =6.0 | |
Redhat Enterprise Linux Hpc Node | =6.0 | |
Red Hat Enterprise Linux Server | =6.0 | |
Redhat Enterprise Linux Workstation | =6.0 | |
Redhat Enterprise Linux Desktop | =7.0 | |
Redhat Enterprise Linux Hpc Node | =7.0 | |
Redhat Enterprise Linux Hpc Node Eus | =7.2 | |
Red Hat Enterprise Linux Server | =7.0 | |
Red Hat Enterprise Linux Server | =7.2 | |
Red Hat Enterprise Linux Server | =7.2 | |
Redhat Enterprise Linux Workstation | =7.0 | |
Oracle Linux | =6 | |
Oracle Linux | =7 | |
Libarchive Libarchive | <=3.2.0 |
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.