tiff: CVE-2022-3627 CVE-2022-3626 CVE-2022-3599 CVE-2022-3598 CVE-2022-3597 CVE-2022-3570

Debian Bug report logs - #1022555
tiff: CVE-2022-3627 CVE-2022-3626 CVE-2022-3599 CVE-2022-3598 CVE-2022-3597 CVE-2022-3570

Reply or subscribe to this bug.

Toggle useless messages

Message #5 received at submit@bugs.debian.org (full text, mbox, reply):

From: Moritz Mühlenhoff <jmm@inutil.org>

To: submit@bugs.debian.org

Subject: tiff: CVE-2022-3627 CVE-2022-3626 CVE-2022-3599 CVE-2022-3598 CVE-2022-3597 CVE-2022-3570

Date: Sun, 23 Oct 2022 21:51:06 +0200

Source: tiff
X-Debbugs-CC: team@security.debian.org
Severity: grave
Tags: security

Hi,

The following vulnerabilities were published for tiff.

CVE-2022-3627[0]:
| 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.

https://gitlab.com/libtiff/libtiff/-/commit/236b7191f04c60d09ee836ae13b50f812c841047
https://gitlab.com/libtiff/libtiff/-/issues/411

CVE-2022-3626[1]:
| LibTIFF 4.4.0 has an out-of-bounds write in _TIFFmemset in
| libtiff/tif_unix.c:340 when called from processCropSelections,
| tools/tiffcrop.c:7619, 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.

https://gitlab.com/libtiff/libtiff/-/commit/236b7191f04c60d09ee836ae13b50f812c841047
https://gitlab.com/libtiff/libtiff/-/issues/426

CVE-2022-3599[2]:
| LibTIFF 4.4.0 has an out-of-bounds read in writeSingleSection in
| tools/tiffcrop.c:7345, 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.

https://gitlab.com/libtiff/libtiff/-/commit/e813112545942107551433d61afd16ac094ff246
https://gitlab.com/libtiff/libtiff/-/issues/398

CVE-2022-3598[3]:
| LibTIFF 4.4.0 has an out-of-bounds write in
| extractContigSamplesShifted24bits in tools/tiffcrop.c:3604, 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 cfbb883b.

https://gitlab.com/libtiff/libtiff/-/commit/cfbb883bf6ea7bedcb04177cc4e52d304522fdff
https://gitlab.com/libtiff/libtiff/-/issues/435

CVE-2022-3597[4]:
| 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:6826, 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.

https://gitlab.com/libtiff/libtiff/-/commit/236b7191f04c60d09ee836ae13b50f812c841047
https://gitlab.com/libtiff/libtiff/-/issues/413

CVE-2022-3570[5]:
| 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

https://gitlab.com/libtiff/libtiff/-/commit/bd94a9b383d8755a27b5a1bc27660b8ad10b094c
https://gitlab.com/libtiff/libtiff/-/issues/381
https://gitlab.com/libtiff/libtiff/-/issues/386

If you fix the vulnerabilities please also make sure to include the
CVE (Common Vulnerabilities & Exposures) ids in your changelog entry.

For further information see:

[0] https://security-tracker.debian.org/tracker/CVE-2022-3627
    https://www.cve.org/CVERecord?id=CVE-2022-3627
[1] https://security-tracker.debian.org/tracker/CVE-2022-3626
    https://www.cve.org/CVERecord?id=CVE-2022-3626
[2] https://security-tracker.debian.org/tracker/CVE-2022-3599
    https://www.cve.org/CVERecord?id=CVE-2022-3599
[3] https://security-tracker.debian.org/tracker/CVE-2022-3598
    https://www.cve.org/CVERecord?id=CVE-2022-3598
[4] https://security-tracker.debian.org/tracker/CVE-2022-3597
    https://www.cve.org/CVERecord?id=CVE-2022-3597
[5] https://security-tracker.debian.org/tracker/CVE-2022-3570
    https://www.cve.org/CVERecord?id=CVE-2022-3570

Please adjust the affected versions in the BTS as needed.

Send a report that this bug log contains spam.