CVE-2016-5418
published 2016-09-21CVE-2016-5418: 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…
PriorityP347high7.5CVSS 3.0
AVNACLPRNUINSUCNIHAN
EPSS
4.71%
90.8th percentile
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.
Affected
23 ranges
| Vendor | Product | Version range | Fixed in |
|---|---|---|---|
| debian | libarchive | < libarchive 3.2.1-4 (bookworm) | libarchive 3.2.1-4 (bookworm) |
| libarchive | libarchive | <= 3.2.0 | — |
| libarchive | libarchive | >= 0 < 3.2.1-4 | 3.2.1-4 |
| libarchive | libarchive | >= 0 < 3.2.1-4 | 3.2.1-4 |
| libarchive | libarchive | >= 0 < 3.2.1-4 | 3.2.1-4 |
| libarchive | libarchive | >= 0 < 3.2.1-4 | 3.2.1-4 |
| libarchive | libarchive | >= 0 < 3.1.2-7ubuntu2.4 | 3.1.2-7ubuntu2.4 |
| libarchive | libarchive | >= 0 < 3.1.2-11ubuntu0.16.04.3 | 3.1.2-11ubuntu0.16.04.3 |
| oracle | linux | — | — |
| oracle | linux | — | — |
| redhat | enterprise_linux_desktop | — | — |
| redhat | enterprise_linux_desktop | — | — |
| redhat | enterprise_linux_hpc_node | — | — |
| redhat | enterprise_linux_hpc_node | — | — |
| redhat | enterprise_linux_hpc_node_eus | — | — |
| redhat | enterprise_linux_server | — | — |
| redhat | enterprise_linux_server | — | — |
| redhat | enterprise_linux_server_aus | — | — |
| redhat | enterprise_linux_server_eus | — | — |
| redhat | enterprise_linux_workstation | — | — |
| redhat | enterprise_linux_workstation | — | — |
| redhat | openshift | — | — |
| redhat | openshift | — | — |
CVSS provenance
nvdv3.07.5HIGHCVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N
nvdv2.05.0MEDIUMAV:N/AC:L/Au:N/C:N/I:P/A:N
osv7.5HIGH
vendor_debian7.5HIGH
vendor_redhat7.5HIGH
vendor_ubuntu7.5HIGH
Stop checking back — get the weekly exploitation signal.
Every Monday: what got weaponized or added to CISA KEV in the last seven days — each CVE cross-linked to its PoC, Nuclei template, and detection rule. Free, one email a week, unsubscribe in one click.
GHSA
GHSA-88p3-99rj-qvrx: The sandboxing code in libarchive 3
ghsa_unreviewed·2022-05-13
CVE-2016-5418 [HIGH] CWE-20 GHSA-88p3-99rj-qvrx: The sandboxing code in libarchive 3
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.
OSV
libarchive vulnerabilities
osv·2017-03-09·CVSS 7.5
CVE-2016-5418 [HIGH] libarchive vulnerabilities
libarchive vulnerabilities
It was discovered that libarchive incorrectly handled hardlink entries when
extracting archives. A remote attacker could possibly use this issue to
overwrite arbitrary files. (CVE-2016-5418)
Christian Wressnegger, Alwin Maier, and Fabian Yamaguchi discovered that
libarchive incorrectly handled filename lengths when writing ISO9660
archives. A remote attacker could use this issue to cause libarchive to
crash, resulting in a denial of service, or possibly execute arbitrary
code. This issue only applied to Ubuntu 12.04 LTS, Ubuntu 14.04 LTS and
Ubuntu 16.04 LTS. (CVE-2016-6250)
Alexander Cherepanov discovered that libarchive incorrectly handled
recursive decompressions. A remote attacker could possibly use this issue
to cause libarchive to hang, resulting in a de
OSV
CVE-2016-5418: The sandboxing code in libarchive 3
osv·2016-09-21·CVSS 7.5
CVE-2016-5418 [HIGH] CVE-2016-5418: The sandboxing code in libarchive 3
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.
Ubuntu
libarchive vulnerabilities
vendor_ubuntu·2017-03-09·CVSS 7.5
CVE-2016-5418 [HIGH] libarchive vulnerabilities
Title: libarchive vulnerabilities
Summary: libarchive could be made to crash, overwrite files, or run programs as your
login if it opened a specially crafted file.
It was discovered that libarchive incorrectly handled hardlink entries when
extracting archives. A remote attacker could possibly use this issue to
overwrite arbitrary files. (CVE-2016-5418)
Christian Wressnegger, Alwin Maier, and Fabian Yamaguchi discovered that
libarchive incorrectly handled filename lengths when writing ISO9660
archives. A remote attacker could use this issue to cause libarchive to
crash, resulting in a denial of service, or possibly execute arbitrary
code. This issue only applied to Ubuntu 12.04 LTS, Ubuntu 14.04 LTS and
Ubuntu 16.04 LTS. (CVE-2016-6250)
Alexander Cherepanov discovered that libarchive in
Red Hat
libarchive: Archive Entry with type 1 (hardlink), but has a non-zero data size file overwrite
vendor_redhat·2016-09-12·CVSS 7.5
CVE-2016-5418 [HIGH] CWE-20 libarchive: Archive Entry with type 1 (hardlink), but has a non-zero data size file overwrite
libarchive: Archive Entry with type 1 (hardlink), but has a non-zero data size file overwrite
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.
A flaw was found in the way libarchive handled hardlink archive entries of non-zero size. Combined with flaws in libarchive's file system sandboxing, this issue could cause an application using libarchive to overwrite arbitrary files with arbitrary data from the archive.
Debian
CVE-2016-5418: libarchive - The sandboxing code in libarchive 3.2.0 and earlier mishandles hardlink archive ...
vendor_debian·2016·CVSS 7.5
CVE-2016-5418 [HIGH] CVE-2016-5418: libarchive - The sandboxing code in libarchive 3.2.0 and earlier mishandles hardlink archive ...
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.
Scope: local
bookworm: resolved (fixed in 3.2.1-4)
bullseye: resolved (fixed in 3.2.1-4)
forky: resolved (fixed in 3.2.1-4)
sid: resolved (fixed in 3.2.1-4)
trixie: resolved (fixed in 3.2.1-4)
No detection rules found.
No public exploits indexed.
Bugzilla
CVE-2016-5418 libarchive3: libarchive: Archive Entry with type 1 (hardlink), but has a non-zero data size file overwrite [epel-6]
bugzilla·2016-09-12·CVSS 7.5
CVE-2016-5418 [HIGH] CVE-2016-5418 libarchive3: libarchive: Archive Entry with type 1 (hardlink), but has a non-zero data size file overwrite [epel-6]
CVE-2016-5418 libarchive3: libarchive: Archive Entry with type 1 (hardlink), but has a non-zero data size file overwrite [epel-6]
This is an automatically created tracking bug! It was created to ensure
that one or more security vulnerabilities are fixed in affected versions
of Fedora EPEL.
For comments that are specific to the vulnerability please use bugs filed
against the "Security Response" product referenced in the "Blocks" field.
For more information see:
http://fedoraproject.org/wiki/Security/TrackingBugs
When submitting as an update, use the fedpkg template provided in the next
comment(s). This will include the bug IDs of this tracking bug as well as
the relevant top-level CVE bugs.
Please also mention the CVE IDs being fixed in the RPM changelog and the
fedpkg commit message.
Bugzilla
CVE-2016-5418 libarchive: Archive Entry with type 1 (hardlink), but has a non-zero data size file overwrite [epel-5]
bugzilla·2016-09-12·CVSS 7.5
CVE-2016-5418 [HIGH] CVE-2016-5418 libarchive: Archive Entry with type 1 (hardlink), but has a non-zero data size file overwrite [epel-5]
CVE-2016-5418 libarchive: Archive Entry with type 1 (hardlink), but has a non-zero data size file overwrite [epel-5]
This is an automatically created tracking bug! It was created to ensure
that one or more security vulnerabilities are fixed in affected versions
of Fedora EPEL.
For comments that are specific to the vulnerability please use bugs filed
against the "Security Response" product referenced in the "Blocks" field.
For more information see:
http://fedoraproject.org/wiki/Security/TrackingBugs
When submitting as an update, use the fedpkg template provided in the next
comment(s). This will include the bug IDs of this tracking bug as well as
the relevant top-level CVE bugs.
Please also mention the CVE IDs being fixed in the RPM changelog and the
fedpkg commit message.
[bug automat
Bugzilla
CVE-2016-5418 libarchive: Archive Entry with type 1 (hardlink), but has a non-zero data size file overwrite [fedora-all]
bugzilla·2016-09-12·CVSS 7.5
CVE-2016-5418 [HIGH] CVE-2016-5418 libarchive: Archive Entry with type 1 (hardlink), but has a non-zero data size file overwrite [fedora-all]
CVE-2016-5418 libarchive: Archive Entry with type 1 (hardlink), but has a non-zero data size file overwrite [fedora-all]
This is an automatically created tracking bug! It was created to ensure
that one or more security vulnerabilities are fixed in affected versions
of Fedora.
For comments that are specific to the vulnerability please use bugs filed
against the "Security Response" product referenced in the "Blocks" field.
For more information see:
http://fedoraproject.org/wiki/Security/TrackingBugs
When submitting as an update, use the fedpkg template provided in the next
comment(s). This will include the bug IDs of this tracking bug as well as
the relevant top-level CVE bugs.
Please also mention the CVE IDs being fixed in the RPM changelog and the
fedpkg commit message.
NOTE: this is
Bugzilla
CVE-2016-5418 libarchive: Archive Entry with type 1 (hardlink), but has a non-zero data size file overwrite
bugzilla·2016-08-02·CVSS 7.5
CVE-2016-5418 [HIGH] CVE-2016-5418 libarchive: Archive Entry with type 1 (hardlink), but has a non-zero data size file overwrite
CVE-2016-5418 libarchive: Archive Entry with type 1 (hardlink), but has a non-zero data size file overwrite
Insomnia Security (as part of a pre-arranged commercial engagement) reports:
A vulnerability in libarchive exists that allows an archive Entry with type 1 (hardlink), but has a non-zero data size to cause a file overwrite. This vulnerability can be leveraged in a way that has a significant security impact (this was not clear at first during initial research by upstream).
Discussion:
Upstream bugs:
https://github.com/libarchive/libarchive/issues/743 (umbrella report)
https://github.com/libarchive/libarchive/issues/744
https://github.com/libarchive/libarchive/issues/745
https://github.com/libarchive/libarchive/issues/746
External reference:
http://seclists.org/oss-sec/2016/q3/25
http://rhn.redhat.com/errata/RHSA-2016-1844.htmlhttp://rhn.redhat.com/errata/RHSA-2016-1850.htmlhttp://www.openwall.com/lists/oss-security/2016/08/09/2http://www.oracle.com/technetwork/topics/security/linuxbulletinjul2016-3090544.htmlhttp://www.securityfocus.com/bid/93165https://access.redhat.com/errata/RHSA-2016:1852https://access.redhat.com/errata/RHSA-2016:1853https://bugzilla.redhat.com/show_bug.cgi?id=1362601https://gist.github.com/anonymous/e48209b03f1dd9625a992717e7b89c4fhttps://github.com/libarchive/libarchive/commit/dfd6b54ce33960e420fb206d8872fb759b577ad9https://github.com/libarchive/libarchive/issues/746https://security.gentoo.org/glsa/201701-03http://rhn.redhat.com/errata/RHSA-2016-1844.htmlhttp://rhn.redhat.com/errata/RHSA-2016-1850.htmlhttp://www.openwall.com/lists/oss-security/2016/08/09/2http://www.oracle.com/technetwork/topics/security/linuxbulletinjul2016-3090544.htmlhttp://www.securityfocus.com/bid/93165https://access.redhat.com/errata/RHSA-2016:1852https://access.redhat.com/errata/RHSA-2016:1853https://bugzilla.redhat.com/show_bug.cgi?id=1362601https://gist.github.com/anonymous/e48209b03f1dd9625a992717e7b89c4fhttps://github.com/libarchive/libarchive/commit/dfd6b54ce33960e420fb206d8872fb759b577ad9https://github.com/libarchive/libarchive/issues/746https://security.gentoo.org/glsa/201701-03
2016-09-21
Published