CVE-2016-5418 Path traversal in n/a

High 7.5 Published 21 Sep 2016 Updated 6 Aug 2024

Remote attackers can write to arbitrary files via crafted archive entries due to improper handling of hardlinks in libarchive.

Exploited in the wild: Not known
Login needed: Not needed
Attackable: Over the internet
Victim action needed: Not needed
Fix: Available

What is CVE-2016-5418?

CVE-2016-5418 is a high-severity path traversal vulnerability in Libarchive Libarchive, published on 21 Sep 2016. An attacker can exploit it over the internet without logging in, with no action from the victim.

Official description

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.

Weakness: CWE-20, CWE-19

Which versions are affected by CVE-2016-5418?

It affects 10 products.

Linux distribution packages (29)

`atomic-openshift` Red Hat:openshift:3.1::el7	All versions	`0:3.1.1.7-1.git.0.65f396b.el7aos`
`atomic-openshift-clients` Red Hat:openshift:3.1::el7	All versions	`0:3.1.1.7-1.git.0.65f396b.el7aos`
`atomic-openshift-clients-redistributable` Red Hat:openshift:3.1::el7	All versions	`0:3.1.1.7-1.git.0.65f396b.el7aos`
`atomic-openshift-dockerregistry` Red Hat:openshift:3.1::el7	All versions	`0:3.1.1.7-1.git.0.65f396b.el7aos`
`atomic-openshift-master` Red Hat:openshift:3.1::el7	All versions	`0:3.1.1.7-1.git.0.65f396b.el7aos`
`atomic-openshift-node` Red Hat:openshift:3.1::el7	All versions	`0:3.1.1.7-1.git.0.65f396b.el7aos`
`atomic-openshift-pod` Red Hat:openshift:3.1::el7	All versions	`0:3.1.1.7-1.git.0.65f396b.el7aos`
`atomic-openshift-recycle` Red Hat:openshift:3.1::el7	All versions	`0:3.1.1.7-1.git.0.65f396b.el7aos`
`atomic-openshift-sdn-ovs` Red Hat:openshift:3.1::el7	All versions	`0:3.1.1.7-1.git.0.65f396b.el7aos`
`tuned-profiles-atomic-openshift-node` Red Hat:openshift:3.1::el7	All versions	`0:3.1.1.7-1.git.0.65f396b.el7aos`
`atomic-openshift` Red Hat:openshift:3.2::el7	All versions	`0:3.2.1.15-1.git.0.d84be7f.el7`
`atomic-openshift-clients` Red Hat:openshift:3.2::el7	All versions	`0:3.2.1.15-1.git.0.d84be7f.el7`
`atomic-openshift-clients-redistributable` Red Hat:openshift:3.2::el7	All versions	`0:3.2.1.15-1.git.0.d84be7f.el7`
`atomic-openshift-dockerregistry` Red Hat:openshift:3.2::el7	All versions	`0:3.2.1.15-1.git.0.d84be7f.el7`
`atomic-openshift-master` Red Hat:openshift:3.2::el7	All versions	`0:3.2.1.15-1.git.0.d84be7f.el7`
`atomic-openshift-node` Red Hat:openshift:3.2::el7	All versions	`0:3.2.1.15-1.git.0.d84be7f.el7`
`atomic-openshift-pod` Red Hat:openshift:3.2::el7	All versions	`0:3.2.1.15-1.git.0.d84be7f.el7`
`atomic-openshift-recycle` Red Hat:openshift:3.2::el7	All versions	`0:3.2.1.15-1.git.0.d84be7f.el7`
`atomic-openshift-sdn-ovs` Red Hat:openshift:3.2::el7	All versions	`0:3.2.1.15-1.git.0.d84be7f.el7`
`atomic-openshift-tests` Red Hat:openshift:3.2::el7	All versions	`0:3.2.1.15-1.git.0.d84be7f.el7`
`atomic-openshift-utils` Red Hat:openshift:3.2::el7	All versions	`0:3.2.28-1.git.0.5a85fc5.el7`
`heapster` Red Hat:openshift:3.2::el7	All versions	`0:1.1.0-1.beta2.el7.1`
`openshift-ansible` Red Hat:openshift:3.2::el7	All versions	`0:3.2.28-1.git.0.5a85fc5.el7`
`openshift-ansible-docs` Red Hat:openshift:3.2::el7	All versions	`0:3.2.28-1.git.0.5a85fc5.el7`
`openshift-ansible-filter-plugins` Red Hat:openshift:3.2::el7	All versions	`0:3.2.28-1.git.0.5a85fc5.el7`
`openshift-ansible-lookup-plugins` Red Hat:openshift:3.2::el7	All versions	`0:3.2.28-1.git.0.5a85fc5.el7`
`openshift-ansible-playbooks` Red Hat:openshift:3.2::el7	All versions	`0:3.2.28-1.git.0.5a85fc5.el7`
`openshift-ansible-roles` Red Hat:openshift:3.2::el7	All versions	`0:3.2.28-1.git.0.5a85fc5.el7`
`tuned-profiles-atomic-openshift-node` Red Hat:openshift:3.2::el7	All versions	`0:3.2.1.15-1.git.0.d84be7f.el7`

Products include Libarchive Libarchive, Oracle Linux, Redhat Enterprise Linux Desktop, Redhat Enterprise Linux Hpc Node, Redhat Enterprise Linux Hpc Node Eus, Redhat Enterprise Linux Server and 4 more.

How do I fix CVE-2016-5418?

Upgrade to a fixed version.

Upgrade, and resolve every user-supplied path against an allowed base folder before opening it. More about Path traversal.

Is CVE-2016-5418 being exploited?

There is no known exploitation of CVE-2016-5418 in the wild and no public exploit code.

All Libarchive Libarchive vulnerabilities

Sources

Also known as DEBIAN-CVE-2016-5418, DLA-657-1, GHSA-88p3-99rj-qvrx, MGASA-2016-0318, RHSA-2016:1852, RHSA-2016:1853 and 1 more.