First published: Sun Dec 31 2017(Updated: )
Exiv2 0.26 has a Null Pointer Dereference in the Exiv2::DataValue::toLong function in value.cpp, related to crafted metadata in a malformed TIFF file. The vulnerability causes a segmentation fault. [UPSTREAM BUG] <a href="https://github.com/Exiv2/exiv2/issues/168">https://github.com/Exiv2/exiv2/issues/168</a> [UPSTREAM PATCH] <a href="https://github.com/Exiv2/exiv2/pull/199">https://github.com/Exiv2/exiv2/pull/199</a>
Credit: cve@mitre.org
Affected Software | Affected Version | How to fix |
---|---|---|
CentOS Dos2unix | =0.26 | |
Debian | =10.0 |
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
CVE-2017-18005 has been classified as a moderate severity vulnerability due to potential denial-of-service risks.
To fix CVE-2017-18005, upgrade Exiv2 to the latest version that addresses this vulnerability.
The CVE-2017-18005 vulnerability is caused by a null pointer dereference in the Exiv2::DataValue::toLong function when processing malformed TIFF file metadata.
CVE-2017-18005 affects Exiv2 version 0.26 and Debian GNU/Linux version 10.0.
Yes, CVE-2017-18005 can lead to segmentation faults and potential system crashes due to the null pointer dereference.