# CVE-2016-5418: Path traversal in n/a > Remote attackers can write to arbitrary files via crafted archive entries due to improper handling of hardlinks in libarchive. - **Severity:** High 7.5 (`CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N`) - **Exploited in the wild:** Not known - **Login needed:** Not needed - **Attackable:** Over the internet - **Victim action needed:** Not needed - **Fix available:** Yes - **Published:** 21 Sep 2016 - **Updated:** 6 Aug 2024 - **Also known as:** DEBIAN-CVE-2016-5418, DLA-657-1, GHSA-88p3-99rj-qvrx, MGASA-2016-0318, RHSA-2016:1852, RHSA-2016:1853, UBUNTU-CVE-2016-5418 ## 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 (Improper Input Validation), CWE-19 ## Which versions are affected by CVE-2016-5418? It affects 10 products. | Package | Ecosystem | Affected | Fixed in | | --- | --- | --- | --- | | `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: Libarchive Libarchive, Oracle Linux, Redhat Enterprise Linux Desktop, Redhat Enterprise Linux Hpc Node, Redhat Enterprise Linux Hpc Node Eus, Redhat Enterprise Linux Server, Redhat Enterprise Linux Server Aus, Redhat Enterprise Linux Server Eus, Redhat Enterprise Linux Workstation, Redhat Openshift. ## How do I fix CVE-2016-5418? Upgrade to a fixed version. ## Is CVE-2016-5418 being exploited? There is no known exploitation of CVE-2016-5418 in the wild and no public exploit code. ## Other vulnerabilities in Libarchive Libarchive - [CVE-2024-37407](https://insights.sbomify.com/CVE-2024-37407/): Memory corruption in n/a (critical 9.1) - [CVE-2016-1541](https://insights.sbomify.com/CVE-2016-1541/): Memory corruption in n/a (high 8.8) - [CVE-2016-6250](https://insights.sbomify.com/CVE-2016-6250/): Integer overflow in n/a (high 8.6) - [CVE-2025-5914](https://insights.sbomify.com/CVE-2025-5914/): Libarchive: double free at archive_read_format_rar_seek_data() in archive_read_support_format_rar.c (high 7.8) - [CVE-2024-48957](https://insights.sbomify.com/CVE-2024-48957/): Memory corruption in n/a (high 7.8) ## Fix prompt for AI coding agents ```text Check this codebase for CVE-2016-5418 and fix it if it is affected. What it is: 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. Exploitation: There is no known exploitation of CVE-2016-5418 in the wild and no public exploit code. Affected product: Libarchive Libarchive. No package-level version data is available, so check the vendor advisory linked from the reference page. Task: 1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies. 2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it. 3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead. 4. Run the tests and summarise what changed and why. 5. If nothing in the project is affected, say so and change nothing. Reference: https://insights.sbomify.com/CVE-2016-5418/ (Markdown: https://insights.sbomify.com/CVE-2016-5418/index.md) ``` ## Sources - CVE record: https://www.cve.org/CVERecord?id=CVE-2016-5418 - NVD: https://nvd.nist.gov/vuln/detail/CVE-2016-5418 - OSV: https://osv.dev/vulnerability/CVE-2016-5418 --- From sbomify Insights: https://insights.sbomify.com/CVE-2016-5418/ Summaries are generated and may contain mistakes; the official description above is the record.