CVE-2016-8688

Description

The mtree bidder in libarchive 3.2.1 does not keep track of line sizes when extending the read-ahead, which allows remote attackers to cause a denial of service (crash) via a crafted file, which triggers an invalid read in the (1) detect_form or (2) bid_entry function in libarchive/archive_read_support_format_mtree.c.

Category

5.5
CVSS
Severity: Medium
CVSS 3.0 •
CVSS 2.0 •
EPSS 0.23%
Vendor Advisory gentoo.org Vendor Advisory opensuse.org
Affected: n/a n/a
Published at:
Updated at:

References

Link Tags
http://www.openwall.com/lists/oss-security/2016/10/16/11 mailing list third party advisory patch
https://lists.debian.org/debian-lts-announce/2018/11/msg00037.html mailing list
https://blogs.gentoo.org/ago/2016/09/11/libarchive-bsdtar-use-after-free-in-detect_form-archive_read_support_format_mtree-c/ vdb entry third party advisory patch
https://bugzilla.redhat.com/show_bug.cgi?id=1377923 issue tracking patch
https://security.gentoo.org/glsa/201701-03 vdb entry third party advisory patch vendor advisory
https://github.com/libarchive/libarchive/commit/eec077f52bfa2d3f7103b4b74d52572ba8a15aca issue tracking third party advisory patch
https://blogs.gentoo.org/ago/2016/09/11/libarchive-bsdtar-heap-based-buffer-overflow-in-bid_entry-archive_read_support_format_mtree-c/ vdb entry third party advisory patch
http://www.securityfocus.com/bid/93781 vdb entry third party advisory
https://blogs.gentoo.org/ago/2016/09/11/libarchive-bsdtar-memory-corruptionunknown-crash-in-bid_entry-archive_read_support_format_mtree-c/ vdb entry third party advisory patch
https://blogs.gentoo.org/ago/2016/09/11/libarchive-bsdtar-heap-based-buffer-overflow-in-detect_form-archive_read_support_format_mtree-c/ vdb entry third party advisory patch
http://lists.opensuse.org/opensuse-updates/2016-12/msg00027.html third party advisory vendor advisory
https://blogs.gentoo.org/ago/2016/09/11/libarchive-bsdtar-use-after-free-in-bid_entry-archive_read_support_format_mtree-c/ vdb entry third party advisory patch

Frequently Asked Questions

What is the severity of CVE-2016-8688?
CVE-2016-8688 has been scored as a medium severity vulnerability.
How to fix CVE-2016-8688?
To fix CVE-2016-8688, make sure you are using an up-to-date version of the affected component(s) by checking the vendor release notes. As for now, there are no other specific guidelines available.
Is CVE-2016-8688 being actively exploited in the wild?
As for now, there are no information to confirm that CVE-2016-8688 is being actively exploited. According to its EPSS score, there is a ~0% probability that this vulnerability will be exploited by malicious actors in the next 30 days.
This platform uses data from the NIST NVD, MITRE CVE, MITRE CWE, First.org and CISA KEV but is not endorsed or certified by these entities. CVE is a registred trademark of the MITRE Corporation and the authoritative source of CVE content is MITRE's CVE web site. CWE is a registred trademark of the MITRE Corporation and the authoritative source of CWE content is MITRE's CWE web site.
© 2025 Under My Watch. All Rights Reserved.