Bug 1730329 (CVE-2019-13311) - CVE-2019-13311 ImageMagick: memory leaks at AcquireMagickMemory because of a wand/mogrify.c error
Summary: CVE-2019-13311 ImageMagick: memory leaks at AcquireMagickMemory because of a ...
Alias: CVE-2019-13311
Product: Security Response
Classification: Other
Component: vulnerability
Version: unspecified
Hardware: All
OS: Linux
Target Milestone: ---
Assignee: Red Hat Product Security
QA Contact:
Depends On: 1730331 1730792
Blocks: 1730618
TreeView+ depends on / blocked
Reported: 2019-07-16 13:17 UTC by Marian Rehak
Modified: 2023-09-07 20:15 UTC (History)
7 users (show)

Fixed In Version: ImageMagick 6.9.10-52, ImageMagick 7.0.8-52
Doc Type: If docs needed, set a value
Doc Text:
A flaw was found in ImageMagick, containing memory leaks of AcquireMagickMemory due to a wand/mogrify.c error. It was discovered that ImageMagick does not properly release acquired memory when some error conditions occur in the function MogrifyImageList(). An attacker could abuse this flaw by providing a specially crafted image and cause a Denial of Service by using all available memory. Applications compiled against ImageMagick libraries that accept untrustworthy images may be exploited to use all available memory and make them crash.
Clone Of:
Last Closed: 2020-03-31 22:34:39 UTC

Attachments (Terms of Use)

System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHSA-2020:1180 0 None None None 2020-03-31 19:32:32 UTC

Description Marian Rehak 2019-07-16 13:17:19 UTC
ImageMagick 7.0.8-50 Q16 has memory leaks at AcquireMagickMemory because of a wand/mogrify.c error.

Upstream Issues:


Comment 1 Marian Rehak 2019-07-16 13:22:12 UTC
Created ImageMagick tracking bugs for this issue:

Affects: fedora-all [bug 1730331]

Comment 8 errata-xmlrpc 2020-03-31 19:32:29 UTC
This issue has been addressed in the following products:

  Red Hat Enterprise Linux 7

Via RHSA-2020:1180 https://access.redhat.com/errata/RHSA-2020:1180

Comment 9 Product Security DevOps Team 2020-03-31 22:34:39 UTC
This bug is now closed. Further updates for individual products will be reflected on the CVE page(s):


Note You need to log in before you can comment on or make changes to this bug.