Bug 1730580 (CVE-2019-13300) - CVE-2019-13300 ImageMagick: heap-based buffer overflow at MagickCore/statistic.c in EvaluateImages because of mishandling columns
Summary: CVE-2019-13300 ImageMagick: heap-based buffer overflow at MagickCore/statisti...
Alias: CVE-2019-13300
Product: Security Response
Classification: Other
Component: vulnerability
Version: unspecified
Hardware: All
OS: Linux
Target Milestone: ---
Assignee: Red Hat Product Security
QA Contact:
Depends On: 1730581 1732747
Blocks: 1730618
TreeView+ depends on / blocked
Reported: 2019-07-17 07:35 UTC by Marian Rehak
Modified: 2023-09-07 20:16 UTC (History)
5 users (show)

Fixed In Version: ImageMagick 6.9.10-50, ImageMagick 7.0.8-50
Doc Type: If docs needed, set a value
Doc Text:
A heap-based buffer overflow was discovered in ImageMagick in the way it applies a value with arithmetic, relational, or logical operators to an image due to mishandling columns. Applications compiled against ImageMagick libraries that accept untrustworthy images and use the evaluate-sequence option or function EvaluateImages may be vulnerable to this flaw. An attacker could abuse this flaw by providing a specially crafted image to make the application crash or potentially execute code.
Clone Of:
Last Closed: 2020-03-31 22:34:55 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:44 UTC

Description Marian Rehak 2019-07-17 07:35:44 UTC
ImageMagick 7.0.8-50 Q16 has a heap-based buffer overflow at MagickCore/statistic.c in EvaluateImages because of mishandling columns.

Upstream Issue:


Comment 1 Marian Rehak 2019-07-17 07:36:06 UTC
Created ImageMagick tracking bugs for this issue:

Affects: fedora-all [bug 1730581]

Comment 4 errata-xmlrpc 2020-03-31 19:32:43 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 5 Product Security DevOps Team 2020-03-31 22:34:55 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.