Bug 1348441 – CVE-2016-4301 libarchive: Stack buffer overflow in the mtree parse_device

Bugzilla will be upgraded to version 5.0 on a still to be determined date in the near future. The original upgrade date has been delayed.

Bug 1348441 - (CVE-2016-4301) CVE-2016-4301 libarchive: Stack buffer overflow in the mtree parse_device

Summary:	CVE-2016-4301 libarchive: Stack buffer overflow in the mtree parse_device

Status:	CLOSED NOTABUG

Aliases:	CVE-2016-4301

Product:	Security Response
Classification:	Other
Component:	vulnerability (Show other bugs)
Sub Component:
Version:	unspecified
Hardware:	All Linux

Priority	low Severity low
Target Milestone:	---
Target Release:	---
Assigned To:	Red Hat Product Security
QA Contact:
Docs Contact:

URL:
Whiteboard:	impact=low,public=20160619,reported=2...
Keywords:	Security

Depends On:
Blocks:	1334215
	Show dependency tree / graph

Reported:	2016-06-21 03:55 EDT by Andrej Nemec
Modified:	2016-06-29 10:07 EDT (History)
CC List:	5 users (show)

See Also:
Fixed In Version:	libarchive 3.2.1
Doc Type:	Bug Fix
Doc Text:	An exploitable stack based buffer overflow vulnerability exists in the mtree parse_device functionality of libarchive. A specially crafted mtree file can cause a buffer overflow resulting in memory corruption and potential code execution in the context of the application.
Story Points:	---
Clone Of:
Environment:
Last Closed:	2016-06-22 23:06:00 EDT
Type:	---
Regression:	---
Mount Type:	---
Documentation:	---
CRM:
Verified Versions:
Category:	---
oVirt Team:	---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---

Attachments	(Terms of Use)
Add an attachment (proposed patch, testcase, etc.)

Groups: None (edit)

Description Andrej Nemec 2016-06-21 03:55:14 EDT

An exploitable stack based buffer overflow vulnerability exists in the mtree parse_device functionality of libarchive. A specially crafted mtree file can cause a buffer overflow resulting in memory corruption/code execution. An attacker can send a malformed file to trigger this vulnerability.

External references:

http://www.talosintel.com/reports/TALOS-2016-0153/

Upstream fix:

https://github.com/libarchive/libarchive/commit/a550daeecf6bc689ade371349892ea17b5b97c77

Comment 1 Doran Moppert 2016-06-22 02:16:38 EDT

Contrary to the Talos advisory, the affected code was only introduced after
the release of v3.1.2.  Thus no Red Hat packages are affected.

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