First published: Tue Jun 20 2023(Updated: )
A NULL pointer dereference in TIFFClose() is caused by a failure to open an output file (non-existent path or a path that requires permissions like /dev/null) while specifying zones. <a href="https://research.jfrog.com/vulnerabilities/libtiff-nullderef-dos-xray-522144/">https://research.jfrog.com/vulnerabilities/libtiff-nullderef-dos-xray-522144/</a> <a href="https://gitlab.com/libtiff/libtiff/-/issues/515">https://gitlab.com/libtiff/libtiff/-/issues/515</a>
Affected Software | Affected Version | How to fix |
---|---|---|
libtiff |
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
The severity of REDHAT-BUG-2216080 is classified as a critical NULL pointer dereference vulnerability.
To fix REDHAT-BUG-2216080, ensure that the output path is valid and has the appropriate permissions before using TIFFClose().
REDHAT-BUG-2216080 affects all versions of the LibTIFF library.
Exploiting REDHAT-BUG-2216080 may lead to a denial of service due to application crashes.
A known workaround for REDHAT-BUG-2216080 is to avoid specifying zones or ensure that the output file is accessible.