First published: Tue Aug 02 2016(Updated: )
The sandboxing code in libarchive 3.2.0 and earlier mishandles hardlink archive entries of non-zero data size, which might allow remote attackers to write to arbitrary files via a crafted archive file.
Credit: secalert@redhat.com
Affected Software | Affected Version | How to fix |
---|---|---|
redhat/libarchive | <3.2.2 | 3.2.2 |
Red Hat Enterprise Linux Desktop | =6.0 | |
Red Hat Enterprise Linux HPC Node | =6.0 | |
Red Hat Enterprise Linux Server | =6.0 | |
Red Hat Enterprise Linux Workstation | =6.0 | |
Oracle Linux | =6 | |
Oracle Linux | =7 | |
Red Hat OpenShift | =3.1 | |
Red Hat OpenShift | =3.2 | |
Oracle Libarchive | <=3.2.0 | |
Red Hat Enterprise Linux Desktop | =7.0 | |
Red Hat Enterprise Linux HPC Node | =7.0 | |
Red Hat Enterprise Linux HPC Node | =7.2 | |
Red Hat Enterprise Linux Server | =7.0 | |
Red Hat Enterprise Linux Server | =7.2 | |
Red Hat Enterprise Linux Server | =7.2 | |
Red Hat Enterprise Linux Workstation | =7.0 |
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
CVE-2016-5418 is classified as a moderate severity vulnerability.
To fix CVE-2016-5418, upgrade libarchive to version 3.2.2 or later.
CVE-2016-5418 could allow remote attackers to write to arbitrary files on the system.
CVE-2016-5418 affects libarchive versions 3.2.0 and earlier.
Yes, CVE-2016-5418 specifically affects several Red Hat Enterprise Linux versions including 6.0 and 7.0.