Note: This is a public test instance of Red Hat Bugzilla. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback at bugzilla.redhat.com.

Bug 1178908 (CVE-2014-9449)

Summary: CVE-2014-9449 exiv2: buffer overflow in RiffVideo::infoTagsHandler
Product: [Other] Security Response Reporter: Martin Prpič <mprpic>
Component: vulnerabilityAssignee: Red Hat Product Security <security-response-team>
Status: CLOSED WONTFIX QA Contact:
Severity: medium Docs Contact:
Priority: medium    
Version: unspecifiedCC: jgrulich, michel, rdieter
Target Milestone: ---Keywords: Security
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: exiv2 0.25 Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2019-06-08 02:37:23 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: 1178909    
Bug Blocks:    

Description Martin Prpič 2015-01-05 15:57:31 UTC
A buffer overflow flaw was found in the RiffVideo::infoTagsHandler function in riffvideo.cpp in Exiv2 version 0.24. This flaw could allow remote attackers to cause a denial of service (application crash)  via a long IKEY INFO tag value in an AVI file.

Note that only version 0.24 is affected by this flaw. The patch for this issue is available at [2]. A reproduces is also available in comment #1 in [1].

[1] http://dev.exiv2.org/issues/960
[2] http://dev.exiv2.org/projects/exiv2/repository/diff?rev=3264&rev_to=3263

Comment 1 Martin Prpič 2015-01-05 15:57:58 UTC
Created exiv2 tracking bugs for this issue:

Affects: fedora-21 [bug 1178909]

Comment 3 Fedora Update System 2015-01-21 23:00:01 UTC
exiv2-0.24-4.fc21 has been pushed to the Fedora 21 stable repository.  If problems still persist, please make note of it in this bug report.