Null Pointer Dereference in libtiff: CVE-2022-0908
Summary
CVE-2022-0908: Null source pointer passed as an argument to memcpy() function within TIFFFetchNormalTag () in tif_dirread.c in libtiff versions up to 4.3.0 could lead to Denial of Service via crafted TIFF file. Affects tiff across 2 version ranges.
< 4.3.0-r0
< a95b799f65064e4ba2e2dfc206808f86faf93e85
Fixed in 4.3.0-r0. How to fix ↓
Check if this vulnerability affects your application
Upload a manifest or SBOM and we'll show whether you're affected, plus every other risky package in the same scan.
No signup required · Results in about 60 seconds
Background
libtiff is an open-source library used for reading and writing TIFF image files. It provides various functions and utilities for handling TIFF files. However, versions up to 4.3.0 of libtiff are vulnerable to a null pointer dereference issue in the TIFFFetchNormalTag() function within the tif_dirread.c file. This vulnerability can be exploited by an attacker through a crafted TIFF file, leading to a Denial of Service (DoS) attack.
Vulnerability Detail
The vulnerability (CVE-2022-0908) arises from a null source pointer being passed as an argument to the memcpy() function within the TIFFFetchNormalTag() function. This can result in a crash or termination of the application using libtiff when processing a malicious TIFF file. An attacker can exploit this vulnerability by providing a specially crafted TIFF file, causing the application to crash or become unresponsive. The impact of this vulnerability is limited to a DoS attack, as it does not allow for arbitrary code execution or privilege escalation.
How To Fix
Minimum fixed version
4.3.0-r0
This is the first release that contains the fix.
sudo apk add --upgrade tiffTip — Not sure which version your app runs? Vulert can match this fix to it. Scan free →
Workaround
There is no known workaround for this vulnerability. It is essential to update libtiff to the fixed version to mitigate the risk of exploitation.
Conclusion
The null pointer dereference vulnerability in libtiff (CVE-2022-0908) can be mitigated by updating to version 4.3.0 or later. It is recommended to promptly update libtiff to ensure the security and stability of applications using this library. For further support and assistance in vulnerability remediation, please contact DevNack.com.
See every vulnerability recorded for tiff →
FAQ
libtiff is an open-source library used for reading and writing TIFF image files. It provides various functions and utilities for handling TIFF files.
The vulnerability (CVE-2022-0908) can lead to a Denial of Service (DoS) attack by causing the application using libtiff to crash or become unresponsive. However, it does not allow for arbitrary code execution or privilege escalation.
An attacker can exploit this vulnerability by providing a specially crafted TIFF file, which triggers the null pointer dereference issue in the TIFFFetchNormalTag() function. This can lead to a crash or termination of the application.
No, there is no known workaround for this vulnerability. It is crucial to update libtiff to the fixed version (4.3.0 or later) to mitigate the risk of exploitation.
Users can update libtiff to the fixed version (4.3.0 or later) by obtaining the updated package from the official repository or package manager for their operating system.
Related vulnerabilities
Recent vulnerabilities recorded for tiff.
