Bug 1377923 (CVE-2016-8688) - CVE-2016-8688 libarchive: heap based buffer overflow in detect_form (archive_read_support_format_mtree.c)
Summary: CVE-2016-8688 libarchive: heap based buffer overflow in detect_form (archive_...
Alias: CVE-2016-8688
Product: Security Response
Classification: Other
Component: vulnerability
Version: unspecified
Hardware: All
OS: Linux
Target Milestone: ---
Assignee: Red Hat Product Security
QA Contact:
: 1385664 (view as bug list)
Depends On: 1378669 1385674 1385675 1385676
Blocks: 1376684 1385672
TreeView+ depends on / blocked
Reported: 2016-09-21 03:30 UTC by Doran Moppert
Modified: 2021-02-17 03:18 UTC (History)
7 users (show)

Fixed In Version: libarchive 3.2.2
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Last Closed: 2016-09-23 03:21:20 UTC

Attachments (Terms of Use)

Description Doran Moppert 2016-09-21 03:30:03 UTC
Bookkeeping errors when extending the read-ahead buffer when trying 
to identify an mtree archive could lead libarchive to significantly
overcalculate the size of the line being read, resulting in heap
out-of-bounds reads or a crash.

Disclosed on oss-security:


Upstream issue:


Upstream fix:


All the mtree-related crashes in the oss-sec post came from the same 
underlying issue and were resolved in this commit.

Comment 1 Doran Moppert 2016-09-22 03:57:11 UTC
This could conceivably be exploited for controlled read of the heap, but code execution is not possible.

Comment 2 Doran Moppert 2016-09-23 03:17:06 UTC
Created libarchive tracking bugs for this issue:

Affects: fedora-all [bug 1378669]

Comment 3 Doran Moppert 2016-09-23 03:19:30 UTC

Red Hat Product Security has rated this issue as having Low security impact. This issue is not currently planned to be addressed in future updates. For additional information, refer to the Issue Severity Classification: https://access.redhat.com/security/updates/classification/.

Comment 4 Doran Moppert 2016-10-18 04:31:04 UTC
*** Bug 1385664 has been marked as a duplicate of this bug. ***

Note You need to log in before you can comment on or make changes to this bug.