Bug 1579544 (CVE-2018-11037) - CVE-2018-11037 exiv2: information leak via a crafted file
Summary: CVE-2018-11037 exiv2: information leak via a crafted file
Keywords:
Status: CLOSED ERRATA
Alias: CVE-2018-11037
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: 1579486 Engineering1579489 Engineering1582050
Blocks: Embargoed1579499
TreeView+ depends on / blocked
 
Reported: 2018-05-17 21:15 UTC by Laura Pardo
Modified: 2020-04-28 15:27 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2019-08-06 19:18:52 UTC

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHSA-2019:2101 0 None None None 2019-08-06 12:14:40 UTC
Red Hat Product Errata RHSA-2020:1577 0 None None None 2020-04-28 15:27:11 UTC

Description Laura Pardo 2018-05-17 21:15:06 UTC 
A flaw was found in Exiv2 0.26, the Exiv2::PngImage::printStructure function in pngimage.cpp allows remote attackers to cause an information leak via a crafted file.


References:
https://github.com/Exiv2/exiv2/issues/307
Comment 1 Laura Pardo 2018-05-17 21:16:06 UTC 
Created exiv2 tracking bugs for this issue:

Affects: fedora-all [bug 1579486]
Comment 6 errata-xmlrpc 2019-08-06 12:14:39 UTC 
This issue has been addressed in the following products:

  Red Hat Enterprise Linux 7

Via RHSA-2019:2101 https://access.redhat.com/errata/RHSA-2019:2101
Comment 7 Product Security DevOps Team 2019-08-06 19:18:52 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-11037
Comment 8 errata-xmlrpc 2020-04-28 15:27:10 UTC 
This issue has been addressed in the following products:

  Red Hat Enterprise Linux 8

Via RHSA-2020:1577 https://access.redhat.com/errata/RHSA-2020:1577
Note You need to log in before you can comment on or make changes to this bug.