Bug 1868354 (CVE-2012-1610) - CVE-2012-1610 ImageMagick: integer overflow in the GetEXIFProperty function in magick/property.c could lead to DoS
Summary: CVE-2012-1610 ImageMagick: integer overflow in the GetEXIFProperty function i...
Keywords:
Status: CLOSED WONTFIX
Alias: CVE-2012-1610
Product: Security Response
Classification: Other
Component: vulnerability
Version: unspecified
Hardware: All
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Red Hat Product Security
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks: 1868355
TreeView+ depends on / blocked
 
Reported: 2020-08-12 11:29 UTC by Marian Rehak
Modified: 2021-02-16 19:30 UTC (History)
5 users (show)

Fixed In Version: ImageMagick 6.7.6-4
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2020-08-12 21:15:19 UTC
Embargoed:

Attachments (Terms of Use)

Description Marian Rehak 2020-08-12 11:29:20 UTC 
Integer overflow in the GetEXIFProperty function in magick/property.c allows remote attackers to cause a DoS via a large component count for certain EXIF tags in a JPEG image.

Upstream Reference:

http://www.imagemagick.org/discourse-server/viewtopic.php?f=4&t=20629
Comment 1 Todd Cullum 2020-08-12 19:05:01 UTC 
This flaw is out of support scope for the following products:

* Red Hat Enterprise Linux 5
* Red Hat Enterprise Linux 6

See [1] for more detailed information on support scopes.

ImageMagick as shipped with Red Hat Enterprise Linux 7 and 8 is not affected by this flaw, as the versions shipped have already been patched.

1. https://access.redhat.com/support/policy/updates/errata/
Comment 2 Todd Cullum 2020-08-12 19:05:42 UTC 
Statement:

ImageMagick as shipped with Red Hat Enterprise Linux 7 and 8 is not affected by this flaw, as the versions shipped have already been patched.
Comment 3 Product Security DevOps Team 2020-08-12 21:15:19 UTC 
This bug is now closed. Further updates for individual products will be reflected on the CVE page(s):

https://access.redhat.com/security/cve/cve-2012-1610
Note You need to log in before you can comment on or make changes to this bug.