Bug 1728486 (CVE-2019-13110)

Summary: CVE-2019-13110 exiv2: integer-overflow and out-of-bounds read in CiffDirectory::readDirectory leads to denail of service
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: jgrulich, michel, rdieter, rschiron
Target Milestone: ---Keywords: Security
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: exiv 0.27.2 Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2021-10-27 10:46:04 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: 1728487, 1730404    
Bug Blocks: 1728496, 1988983    

Description Dhananjay Arunesh 2019-07-10 05:09:02 UTC
A CiffDirectory::readDirectory integer overflow and out-of-bounds read in Exiv2 through 0.27.1 allows an attacker to cause a denial of service (SIGSEGV) via a crafted CRW image file.

Reference:
https://github.com/Exiv2/exiv2/issues/843
https://github.com/Exiv2/exiv2/pull/844

Comment 1 Dhananjay Arunesh 2019-07-10 05:10:20 UTC
Created exiv2 tracking bugs for this issue:

Affects: fedora-all [bug 1728487]

Comment 5 Riccardo Schirone 2019-07-16 15:42:39 UTC
Statement:

This issue did not affect the versions of exiv2 as shipped with Red Hat Enterprise Linux 8 as they did not include the vulnerable code.

Comment 6 Riccardo Schirone 2019-07-16 15:47:36 UTC
Function CiffDirectory::readDirectory() in crwimage.cpp checks whether the value `o` read from the image is valid, however the check is performed as `if (o + 2 > size)`, which could be bypassed when `o + 2` wraps around. This leads to an out-of-bound read when reading the `count` value.

Comment 8 Todd Cullum 2021-08-03 00:45:00 UTC
*** Bug 1988977 has been marked as a duplicate of this bug. ***