First published: Fri Oct 21 2022(Updated: )
LibTIFF 4.4.0 has an out-of-bounds write in _TIFFmemcpy in libtiff/tif_unix.c:346 when called from extractImageSection, tools/tiffcrop.c:6860, allowing attackers to cause a denial-of-service via a crafted tiff file. For users that compile libtiff from sources, the fix is available with commit 236b7191.
Credit: cve@gitlab.com
Affected Software | Affected Version | How to fix |
---|---|---|
debian/tiff | <=4.1.0+git191117-2~deb10u4 | 4.1.0+git191117-2~deb10u8 4.2.0-1+deb11u4 4.2.0-1+deb11u5 4.5.0-6+deb12u1 4.5.1+git230720-3 |
Libtiff Libtiff | <=4.4.0 | |
Netapp Active Iq Unified Manager Vmware Vsphere | ||
Debian Debian Linux | =10.0 | |
Debian Debian Linux | =11.0 |
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
CVE-2022-3627 is a vulnerability in LibTIFF 4.4.0 that allows attackers to cause a denial-of-service via a crafted tiff file.
The CVE-2022-3627 vulnerability can be exploited by sending a specially crafted tiff file to the target, which triggers an out-of-bounds write in the _TIFFmemcpy function.
Versions 4.1.0+git191117-2~deb10u4, 4.2.0-1+deb11u4, 4.5.0-6, and 4.5.1+git230720-1 are affected by CVE-2022-3627.
If you compile libtiff from sources, you can apply the fix with commit 236b7191f04c60d09ee836ae13b50f812c841047.
You can find more information about CVE-2022-3627 on the Debian security tracker and the libtiff GitLab repository.