First published: Wed Jun 13 2018(Updated: )
A flaw was found in Exiv2 0.26. An integer overflow in LoaderTiff::getData() in preview.cpp, leading to an out-of-bounds read in Exiv2::ValueType::setDataArea in value.hpp. References: <a href="https://github.com/Exiv2/exiv2/issues/366">https://github.com/Exiv2/exiv2/issues/366</a> <a href="https://github.com/TeamSeri0us/pocs/blob/master/exiv2/2-out-of-read-Poc">https://github.com/TeamSeri0us/pocs/blob/master/exiv2/2-out-of-read-Poc</a> Patch: <a href="https://github.com/Exiv2/exiv2/commit/341de4500ab993103c215bfb07d43d4a08654ac4">https://github.com/Exiv2/exiv2/commit/341de4500ab993103c215bfb07d43d4a08654ac4</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.
The severity of REDHAT-BUG-1590993 is considered high due to the potential for out-of-bounds reads.
To fix REDHAT-BUG-1590993, update Exiv2 to the latest version where the vulnerability has been patched.
REDHAT-BUG-1590993 is caused by an integer overflow in the LoaderTiff::getData() function, which leads to out-of-bounds reads.
Exiv2 version 0.26 is specifically affected by the vulnerability identified in REDHAT-BUG-1590993.
The potential impacts of REDHAT-BUG-1590993 include crashes or unauthorized access to memory, which could lead to data leaks.