First published: Thu Apr 12 2018(Updated: )
A flaw was found in Exiv2 0.26, an out-of-bounds read in IptcData::printStructure in iptc.c could result in a crash or information leak, related to the "!= 0x1c" case. References: <a href="https://github.com/Exiv2/exiv2/issues/263">https://github.com/Exiv2/exiv2/issues/263</a> <a href="https://github.com/xiaoqx/pocs/blob/master/exiv2/readme.md">https://github.com/xiaoqx/pocs/blob/master/exiv2/readme.md</a>
Affected Software | Affected Version | How to fix |
---|---|---|
CentOS Dos2unix |
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
REDHAT-BUG-1566737 is classified as a medium severity vulnerability.
To fix REDHAT-BUG-1566737, update Exiv2 to the latest version that addresses the out-of-bounds read issue.
REDHAT-BUG-1566737 affects Exiv2 version 0.26 and possibly earlier versions.
The issue in REDHAT-BUG-1566737 is an out-of-bounds read that could lead to a crash or an information leak.
As of now, there are no publicly available exploits specifically targeting REDHAT-BUG-1566737.