Bug 1609936 (CVE-2018-14435) - CVE-2018-14435 ImageMagick: memory leak in DecodeImage in coders/pcd.c
Summary: CVE-2018-14435 ImageMagick: memory leak in DecodeImage in coders/pcd.c
Keywords:
Status: CLOSED ERRATA
Alias: CVE-2018-14435
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: 1609937 1609938 1696381
Blocks: 1696293
TreeView+ depends on / blocked
 
Reported: 2018-07-30 21:15 UTC by Laura Pardo
Modified: 2020-03-31 22:33 UTC (History)
3 users (show)

Fixed In Version: ImageMagick 6.9.10-5, ImageMagick 7.0.8-5
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2020-03-31 22:33:01 UTC


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:31:53 UTC

Comment 1 Laura Pardo 2018-07-30 21:16:11 UTC
Created ImageMagick tracking bugs for this issue:

Affects: fedora-all [bug 1609937]

Comment 3 Scott Gayou 2019-04-04 17:01:04 UTC
Flaw is a failure to free memory before an exception is thrown. It looks like the exception macro just returns false and logs, thus, memory leak. (I don't believe the ImageMagick exception terminates immediately, but I did not test it.)

```
           default:
           {
             ThrowBinaryException(CorruptImageError,"CorruptImage",
               image->filename);
           }
```

All Red Hat Enterprise Linux versions look impacted by this minor memory leak.

Comment 5 errata-xmlrpc 2020-03-31 19:31:51 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 6 Product Security DevOps Team 2020-03-31 22:33:01 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-2018-14435


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