A PngChunk::parseChunkContent uncontrolled memory allocation in Exiv2 through 0.27.1 allows an attacker to cause a denial of service (crash due to an std::bad_alloc exception) via a crafted PNG image file. Reference: https://github.com/Exiv2/exiv2/issues/845 https://github.com/Exiv2/exiv2/pull/846
Created exiv2 tracking bugs for this issue: Affects: fedora-all [bug 1728491]
Upstream patch: https://github.com/Exiv2/exiv2/commit/8cdb330743b7b7f1a8e34514effde34d67c77577 [master branch] https://github.com/Exiv2/exiv2/commit/43f154f44b838e6b232193ccbd48e5a2e94bdd35 [0.27-maintenance branch]
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
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-13112