Bug 1691764 (CVE-2019-9923)

Summary: CVE-2019-9923 tar: null-pointer dereference in pax_decode_header in sparse.c
Product: [Other] Security Response Reporter: Dhananjay Arunesh <darunesh>
Component: vulnerabilityAssignee: Red Hat Product Security <security-response-team>
Status: CLOSED ERRATA QA Contact:
Severity: low Docs Contact:
Priority: low    
Version: unspecifiedCC: apmukher, databases-maint, kdudka, odubaj, ovasik, panovotn, pkubat, praiskup, tomm.momi
Target Milestone: ---Keywords: Security
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2021-10-27 03:26:54 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On: 1691765, 1692713, 1692714    
Bug Blocks: 1691767    

Description Dhananjay Arunesh 2019-03-22 13:06:58 UTC
pax_decode_header in sparse.c in GNU Tar before 1.32 had a NULL pointer dereference when parsing certain archives that have malformed extended headers.

Reference:
https://bugs.launchpad.net/ubuntu/+source/tar/+bug/1810241

Upstream commit:
http://git.savannah.gnu.org/cgit/tar.git/commit/?id=cb07844454d8cc9fb21f53ace75975f91185a120

Comment 1 Dhananjay Arunesh 2019-03-22 13:07:13 UTC
Created tar tracking bugs for this issue:

Affects: fedora-all [bug 1691765]

Comment 3 Riccardo Schirone 2019-03-26 09:51:12 UTC
Function pax_decode_header() in sparse.c does not check if there is a next block before using it, thus some malformed tar files could cause an application crash.