Bug 1801673 (CVE-2019-16711) - CVE-2019-16711 ImageMagick: memory leak in Huffman2DEncodeImage in coders/ps2.c
Summary: CVE-2019-16711 ImageMagick: memory leak in Huffman2DEncodeImage in coders/ps2.c
Keywords:
Status: CLOSED ERRATA
Alias: CVE-2019-16711
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: 1801676 1801678 1812617
Blocks: 1801685
TreeView+ depends on / blocked
 
Reported: 2020-02-11 13:16 UTC by Dhananjay Arunesh
Modified: 2020-03-31 22:36 UTC (History)
4 users (show)

Fixed In Version: ImageMagick 7.0.8-40, ImageMagick 6.9.10-40
Doc Type: If docs needed, set a value
Doc Text:
A memory leak was discovered in ImageMagick in function Huffman2DEncodeImage in ps2.c. An application that uses ImageMagick to parse PS2 images may be vulnerable to this flaw and crash due to some memory that is never freed.
Clone Of:
Environment:
Last Closed: 2020-03-31 22:36:09 UTC
Embargoed:


Attachments (Terms of Use)


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

Description Dhananjay Arunesh 2020-02-11 13:16:38 UTC
A vulnerability was found in ImageMagick 7.0.8-40 has a memory leak in Huffman2DEncodeImage in coders/ps2.c.

Reference:
https://github.com/ImageMagick/ImageMagick/issues/1542

Comment 1 Dhananjay Arunesh 2020-02-11 13:19:20 UTC
Created ImageMagick tracking bugs for this issue:

Affects: epel-8 [bug 1801678]
Affects: fedora-all [bug 1801676]

Comment 4 errata-xmlrpc 2020-03-31 19:33:14 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:36:09 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-2019-16711


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