First published: Fri Feb 07 2020(Updated: )
In Jp2Image::readMetadata() in jp2image.cpp in Exiv2 0.27.2, an input file can result in an infinite loop and hang, with high CPU consumption. Remote attackers could leverage this vulnerability to cause a denial of service via a crafted file. Upstream Issue: <a href="https://github.com/Exiv2/exiv2/issues/1011">https://github.com/Exiv2/exiv2/issues/1011</a> Upstream Fix: <a href="https://github.com/Exiv2/exiv2/commit/a82098f4f90cd86297131b5663c3dec6a34470e8">https://github.com/Exiv2/exiv2/commit/a82098f4f90cd86297131b5663c3dec6a34470e8</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-1800472 is categorized as a denial of service vulnerability due to potential high CPU consumption from an infinite loop.
To fix REDHAT-BUG-1800472, you should update to the latest version of Exiv2, which addresses the infinite loop issue.
REDHAT-BUG-1800472 can lead to system unavailability due to high CPU usage from an infinite loop when processing crafted files.
Users of Exiv2 version 0.27.2 are affected by REDHAT-BUG-1800472, particularly those processing specific input files.
Yes, REDHAT-BUG-1800472 can be exploited remotely by attackers through specially crafted files to trigger the denial of service.