Уязвимость функции extractImageSection() компонента tools/tiffcrop.c библиотеки LibTIFF, позволяющая нарушителю вызвать отказ в обслуживании

Уязвимость функции processCropSelections() (tools/tiffcrop.c) библиотеки LibTIFF, позволяющая нарушителю вызвать отказ в обслуживании

Уязвимость функции LZWDecode() (libtiff /tif_lzw.c) библиотеки LibTIFF, позволяющая нарушителю вызвать отказ в обслуживании

Уязвимость функции extractContigSamples32bits() (tiffcrop.c) библиотеки LibTIFF, позволяющая нарушителю вызвать отказ в обслуживании

Уязвимость библиотеки LibTIFF, связанная с выходом операции за границы буфера в памяти при обработке параметров TIFFTAG_INKNAMES и TIFFTAG_NUMBEROFINKS, позволяющая нарушителю вызвать отказ в обслуживании

Уязвимость функции loadImage() (tools/tiffcrop.c) библиотеки LibTIF, позволяющая нарушителю вызвать отказ в обслуживании

Уязвимость компонента tif_dir.c библиотеки LibTIFF связанная с разыменованием нулевого указателя, позволяющая нарушителю вызвать отказ в обслуживании

Уязвимость функции fax3encode библиотеки LibTIFF, позволяющая нарушителю вызвать отказ в обслуживании

Уязвимость функции extractimagesection библиотеки libtiff, позволяющая нарушителю раскрыть защищаемую информацию или вызвать отказ в обслуживании

Уязвимость утилиты tiffcrop (tools/tiffcrop.c:3488) библиотеки libtiff, позволяющая нарушителю вызвать отказ в обслуживании

Уязвимость утилиты tiffcrop (tools/tiffcp.c:948) библиотеки libtiff, позволяющая нарушителю вызвать отказ в обслуживании

Уязвимость утилиты tiffcrop (tools/tiffcrop.c:3701) библиотеки libtiff, позволяющая нарушителю вызвать отказ в обслуживании

Уязвимость утилиты tiffcrop (tools/tiffcrop.c:3502) библиотеки libtiff, позволяющая нарушителю вызвать отказ в обслуживании

Уязвимость утилиты tiffcrop (libtiff/tif_unix.c:368, tools/tiffcrop.c:2903, tools/tiffcrop.c:6778) библиотеки libtiff, позволяющая нарушителю вызвать отказ в обслуживании

Уязвимость утилиты tiffcrop (tools/tiffcrop.c:3724) библиотеки libtiff , позволяющая нарушителю вызвать отказ в обслуживании

Уязвимость утилиты tiffcrop (tools/tiffcrop.c:3516) библиотеки libtiff, позволяющая нарушителю вызвать отказ в обслуживании

Уязвимость утилиты tiffcrop (tools/tiffcrop.c:3609) библиотеки libtiff, позволяющая нарушителю вызвать отказ в обслуживании

Уязвимость утилиты tiffcrop библиотеки libtiff , позволяющая нарушителю вызвать отказ в обслуживании

Уязвимость утилиты tiffcrop библиотеки LibTIFF, позволяющая нарушителю вызвать отказ в обслуживании

Уязвимость утилиты tiffcrop (tools/tiffcrop.c:3592) библиотеки LibTIFF, позволяющая нарушителю вызвать отказ в обслуживании

Уязвимость функции _TIFFmemcpy() (libtiff/tif_unix.c) библиотеки LibTIFF, позволяющая нарушителю вызвать отказ в обслуживании

Уязвимость функции extractContigSamplesShifted8bits() (tools/tiffcrop.c) библиотеки LibTIFF, позволяющая нарушителю вызвать отказ в обслуживании

Уязвимость функции readSeparateTilesIntoBuffer() библиотеки LibTIFF, позволяющая нарушителю вызвать отказ в обслуживании

Уязвимость функции TIFFClose() библиотеки LibTIFF, позволяющая нарушителю вызвать отказ в обслуживании

Уязвимость компонента raw2tiff.c библиотеки LibTIFF, позволяющая нарушителю вызвать отказ в обслуживании

Уязвимость функции tiffrasterscanlinesize64() библиотеки LibTIFF, позволяющая нарушителю вызвать отказ в обслуживании

Уязвимость функции ExtractImageSection() библиотеки LibTIFF, позволяющая нарушителю вызвать отказ в обслуживании

Уязвимость библиотеки LibTIFF, связанная с разыменованием указателя NULL, позволяющая нарушителю вызвать отказ в обслуживании

LibTIFF 4.4.0 has an out-of-bounds read in extractImageSection in tools/tiffcrop.c:6905, 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 48d6ece8.

Multiple heap buffer overflows in tiffcrop.c utility in libtiff library Version 4.4.0 allows attacker to trigger unsafe or out of bounds memory access via crafted TIFF image file which could result into application crash, potential information disclosure or any other context-dependent impact

LibTIFF 4.4.0 has an out-of-bounds read in tiffcp in tools/tiffcp.c:948, 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 e8131125.

processCropSelections in tools/tiffcrop.c in LibTIFF through 4.5.0 has a heap-based buffer overflow (e.g., "WRITE of size 307203") via a crafted TIFF image.

LibTIFF 4.4.0 has an out-of-bounds read in tiffcrop in tools/tiffcrop.c:3488, 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 afaabc3e.

LibTIFF 4.4.0 has an out-of-bounds read in tiffcrop in tools/tiffcrop.c:3592, 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 afaabc3e.

LibTIFF 4.4.0 has an out-of-bounds read in tiffcrop in libtiff/tif_unix.c:368, invoked by tools/tiffcrop.c:2903 and tools/tiffcrop.c:6921, 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 afaabc3e.

LibTIFF 4.4.0 has an out-of-bounds read in tiffcrop in tools/tiffcrop.c:3400, 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 afaabc3e.

LibTIFF 4.4.0 has an out-of-bounds read in tiffcrop in tools/tiffcrop.c:3701, 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 afaabc3e.

LibTIFF 4.4.0 has an out-of-bounds write in tiffcrop in tools/tiffcrop.c:3502, 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 33aee127.

LibTIFF 4.4.0 has an out-of-bounds write in tiffcrop in libtiff/tif_unix.c:368, invoked by tools/tiffcrop.c:2903 and tools/tiffcrop.c:6778, 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 33aee127.

LibTIFF 4.4.0 has an out-of-bounds write in tiffcrop in tools/tiffcrop.c:3724, 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 33aee127.

LibTIFF 4.4.0 has an out-of-bounds write in tiffcrop in tools/tiffcrop.c:3516, 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 33aee127.

LibTIFF 4.4.0 has an out-of-bounds write in tiffcrop in tools/tiffcrop.c:3609, 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 33aee127.

A flaw was found in tiffcrop, a program distributed by the libtiff package. A specially crafted tiff file can lead to an out-of-bounds read in the extractImageSection function in tools/tiffcrop.c, resulting in a denial of service and limited information disclosure. This issue affects libtiff versions 4.x.

loadImage() in tools/tiffcrop.c in LibTIFF through 4.5.0 has a heap-based use after free via a crafted TIFF image.

A NULL pointer dereference flaw was found in Libtiff's LZWDecode() function in the libtiff/tif_lzw.c file. This flaw allows a local attacker to craft specific input data that can cause the program to dereference a NULL pointer when decompressing a TIFF format file, resulting in a program crash or denial of service.

A null pointer dereference issue was found in Libtiff's tif_dir.c file. This issue may allow an attacker to pass a crafted TIFF image file to the tiffcp utility which triggers a runtime error that causes undefined behavior. This will result in an application crash, eventually leading to a denial of service.

A vulnerability was found in the libtiff library. This flaw causes a heap buffer overflow issue via the TIFFTAG_INKNAMES and TIFFTAG_NUMBEROFINKS values.

A vulnerability was found in the libtiff library. This security flaw causes a heap buffer overflow in extractContigSamples32bits, tiffcrop.c.

A heap-buffer-overflow vulnerability was found in LibTIFF, in extractImageSection() at tools/tiffcrop.c:7916 and tools/tiffcrop.c:7801. This flaw allows attackers to cause a denial of service via a crafted tiff file.

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 memory leak flaw was found in Libtiff's tiffcrop utility. This issue occurs when tiffcrop operates on a TIFF image file, allowing an attacker to pass a crafted TIFF image file to tiffcrop utility, which causes this memory leak issue, resulting an application crash, eventually leading to a denial of service.

A flaw was found in libtiff. A specially crafted tiff file can lead to a segmentation fault due to a buffer overflow in the Fax3Encode function in libtiff/tif_fax3.c, resulting in a denial of service.

LibTIFF is vulnerable to an integer overflow. This flaw allows remote attackers to cause a denial of service (application crash) or possibly execute an arbitrary code via a crafted tiff image, which triggers a heap-based buffer overflow.

A vulnerability was found in libtiff due to multiple potential integer overflows in raw2tiff.c. This flaw allows remote attackers to cause a denial of service or possibly execute an arbitrary code via a crafted tiff image, which triggers a heap-based buffer overflow.

An out-of-memory flaw was found in libtiff that could be triggered by passing a crafted tiff file to the TIFFRasterScanlineSize64() API. This flaw allows a remote attacker to cause a denial of service via a crafted input with a size smaller than 379 KB.

A null pointer dereference flaw was found in Libtiff via `tif_dirinfo.c`. This issue may allow an attacker to trigger memory allocation failures through certain means, such as restricting the heap space size or injecting faults, causing a segmentation fault. This can cause an application crash, eventually leading to a denial of service.