Bug 1649101 (CVE-2018-19108) - CVE-2018-19108 exiv2: infinite loop in Exiv2::PsdImage::readMetadata in psdimage.cpp
Summary: CVE-2018-19108 exiv2: infinite loop in Exiv2::PsdImage::readMetadata in psdim...
Alias: CVE-2018-19108
Product: Security Response
Classification: Other
Component: vulnerability
Version: unspecified
Hardware: All
OS: Linux
Target Milestone: ---
Assignee: Red Hat Product Security
QA Contact:
Depends On: 1649103 1649102 1649828
Blocks: 1649106
TreeView+ depends on / blocked
Reported: 2018-11-12 22:47 UTC by Laura Pardo
Modified: 2019-09-29 15:02 UTC (History)
3 users (show)

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

Attachments (Terms of Use)

System ID Priority Status Summary Last Updated
Red Hat Product Errata RHSA-2019:2101 None None None 2019-08-06 12:14:50 UTC

Description Laura Pardo 2018-11-12 22:47:51 UTC
A flaw was found in Exiv2 0.26. An infinite loop in Exiv2::PsdImage::readMetadata in psdimage.cpp in the PSD image reader. This could lead to a denial of service caused by an integer overflow via a crafted PSD image file. 


Upstream Patch:

Comment 1 Laura Pardo 2018-11-12 22:48:37 UTC
Created exiv2 tracking bugs for this issue:

Affects: fedora-all [bug 1649102]

Comment 4 Adam Mariš 2018-11-14 13:45:39 UTC

This issue affects the versions of exiv2 as shipped with Red Hat Enterprise Linux 6. Red Hat Enterprise Linux 6 is now in Maintenance Support 2 Phase of the support and maintenance life cycle. This has been rated as having a security impact of Low, and is not currently planned to be addressed in future updates. For additional information, refer to the Red Hat Enterprise Linux Life Cycle: https://access.redhat.com/support/policy/updates/errata/.

Comment 7 errata-xmlrpc 2019-08-06 12:14:49 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 8 Product Security DevOps Team 2019-08-06 19:20:05 UTC
This bug is now closed. Further updates for individual products will be reflected on the CVE page(s):


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