Bug 1992202 (CVE-2021-34334) - CVE-2021-34334 exiv2: DoS due to integer overflow in loop counter
Summary: CVE-2021-34334 exiv2: DoS due to integer overflow in loop counter
Keywords:
Status: NEW
Alias: CVE-2021-34334
Product: Security Response
Classification: Other
Component: vulnerability
Version: unspecified
Hardware: All
OS: Linux
low
low
Target Milestone: ---
Assignee: Red Hat Product Security
QA Contact:
URL:
Whiteboard:
Depends On: 1992203 1992204 Red Hat1996166 Red Hat1996167 Red Hat1996168
Blocks: Embargoed1992216
TreeView+ depends on / blocked
 
Reported: 2021-08-10 18:01 UTC by Guilherme de Almeida Suckevicz
Modified: 2021-08-20 18:15 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed:

Attachments (Terms of Use)

Description Guilherme de Almeida Suckevicz 2021-08-10 18:01:27 UTC 
Exiv2 is a command-line utility and C++ library for reading, writing, deleting, and modifying the metadata of image files. An infinite loop is triggered when Exiv2 is used to read the metadata of a crafted image file. An attacker could potentially exploit the vulnerability to cause a denial of service, if they can trick the victim into running Exiv2 on a crafted image file. The bug is fixed in version v0.27.5.

Reference:
https://github.com/Exiv2/exiv2/security/advisories/GHSA-hqjh-hpv8-8r9p

Upstream patch:
https://github.com/Exiv2/exiv2/pull/1766
Comment 1 Guilherme de Almeida Suckevicz 2021-08-10 18:01:47 UTC 
Created exiv2 tracking bugs for this issue:

Affects: fedora-all [bug 1992204]


Created mingw-exiv2 tracking bugs for this issue:

Affects: fedora-all [bug 1992203]
Comment 2 Garrett Tucker 2021-08-20 12:55:56 UTC 
The attack vector for this CVE is local, not network based. Exiv2 would require manual execution with specific flags, and requires user interaction on a crafted file to be able to exploit this flaw and is not bound to the network. This CVE is a very similar CVE to CVE-2021-37616 which is correctly labeled as AV:L not AV:N.
Note You need to log in before you can comment on or make changes to this bug.