Bug 1494449 – CVE-2017-14503 libarchive: Out-of-bounds read in lha_read_data_none

Bugzilla will be upgraded to version 5.0. The upgrade date is tentatively scheduled for 2 December 2018, pending final testing and feedback.

Bug 1494449 - (CVE-2017-14503) CVE-2017-14503 libarchive: Out-of-bounds read in lha_read_data_none

Summary:	CVE-2017-14503 libarchive: Out-of-bounds read in lha_read_data_none

Status:	NEW

Aliases:	CVE-2017-14503

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=20170916,reported=2...
Keywords:	Security

Depends On:	1449531
Blocks:
	Show dependency tree / graph

Reported:	2017-09-22 05:53 EDT by Andrej Nemec
Modified:	2018-09-06 01:40 EDT (History)
CC List:	4 users (show)

See Also:
Fixed In Version:	libarchive 3.3.3
Doc Type:	If docs needed, set a value
Doc Text:
Story Points:	---
Clone Of:
Environment:
Last Closed:
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 2017-09-22 05:53:08 EDT

libarchive 3.3.2 suffers from an out-of-bounds read within lha_read_data_none() in archive_read_support_format_lha.c when extracting a specially crafted lha archive, related to lha_crc16. An attacker could use this flaw to cause a denial of service.

Upstream issue:

https://github.com/libarchive/libarchive/issues/948

Comment 1 Andrej Nemec 2017-09-22 05:53:46 EDT

Created libarchive tracking bugs for this issue:

Affects: fedora-all [bug 1449531]

Comment 2 Pavel Raiskup 2018-09-06 01:40:06 EDT

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

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