Bug 1609942 (CVE-2018-14437) - CVE-2018-14437 ImageMagick: memory leak in parse8BIM in coders/meta.c
Summary: CVE-2018-14437 ImageMagick: memory leak in parse8BIM in coders/meta.c
Keywords:
Status: CLOSED ERRATA
Alias: CVE-2018-14437
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: 1609943 1609944 1613369
Blocks: 1609945
TreeView+ depends on / blocked
 
Reported: 2018-07-30 21:26 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:05 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:31:54 UTC

Description Laura Pardo 2018-07-30 21:26:10 UTC 
A flaw was found in ImageMagick 7.0.8-4. A memory leak in parse8BIM in coders/meta.c.


References:
https://github.com/ImageMagick/ImageMagick/issues/1190

Upstream Patch:
https://github.com/ImageMagick/ImageMagick6/commit/0812674565df667b1b3e4122ad259096de311c6c
https://github.com/ImageMagick/ImageMagick/commit/082223fb992448dbb574747deac9a30f986c116e
Comment 1 Laura Pardo 2018-07-30 21:26:41 UTC 
Created ImageMagick tracking bugs for this issue:

Affects: fedora-all [bug 1609943]
Comment 3 Riccardo Schirone 2018-08-07 12:33:59 UTC 
Memory is allocated in the parse8BIM function in coders/meta.c and pointed by the `line` variable. However there are multiple paths that return from the function without releasing the acquired memory.
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:05 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-14437
Note You need to log in before you can comment on or make changes to this bug.