Bug 1726084 (CVE-2019-13137) - CVE-2019-13137 ImageMagick: a memory leak vulnerability in the function ReadPSImage in coders/ps.c
Summary: CVE-2019-13137 ImageMagick: a memory leak vulnerability in the function ReadP...
Keywords:
Status: CLOSED NOTABUG
Alias: CVE-2019-13137
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: 1726085
Blocks: 1726127
TreeView+ depends on / blocked
 
Reported: 2019-07-02 07:50 UTC by Marian Rehak
Modified: 2021-02-16 21:47 UTC (History)
5 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2019-07-12 13:08:09 UTC
Embargoed:

Attachments (Terms of Use)

Description Marian Rehak 2019-07-02 07:50:16 UTC 
ImageMagick before 7.0.8-50 has a memory leak vulnerability in the function ReadPSImage in coders/ps.c.

Upstream Issue:

https://github.com/ImageMagick/ImageMagick/issues/1601
Comment 1 Marian Rehak 2019-07-02 07:50:28 UTC 
Created ImageMagick tracking bugs for this issue:

Affects: fedora-all [bug 1726085]
Comment 2 Riccardo Schirone 2019-07-05 15:25:56 UTC 
Upstream patch:
https://github.com/ImageMagick/ImageMagick/commit/35ccb468ee2dcbe8ce9cf1e2f1957acc27f54c34
Comment 3 Riccardo Schirone 2019-07-05 15:30:29 UTC 
Vulnerable code introduced in https://github.com/ImageMagick/ImageMagick/commit/a5eeacb1bd5536f4f53f36e4ad6fa50b4b1261ca which, according to the commit message "Added eps:fit-page to Phostscript reader."
Comment 4 Riccardo Schirone 2019-07-05 15:31:16 UTC 
Statement:

This issue did not affect the versions of ImageMagick as shipped with Red Hat Enterprise Linux 5, 6, and 7 as they did not include the vulnerable code.
Comment 5 Product Security DevOps Team 2019-07-12 13:08: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-13137
Note You need to log in before you can comment on or make changes to this bug.