tiff: CVE-2023-3618

Debian Bug report logs - #1040945
tiff: CVE-2023-3618

Reply or subscribe to this bug.

Toggle useless messages

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

From: Salvatore Bonaccorso <carnil@debian.org>

To: Debian Bug Tracking System <submit@bugs.debian.org>

Subject: tiff: CVE-2023-3618

Date: Wed, 12 Jul 2023 21:34:09 +0200

Source: tiff
Version: 4.5.1-1
Severity: important
Tags: security upstream
Forwarded: https://gitlab.com/libtiff/libtiff/-/issues/529
X-Debbugs-Cc: carnil@debian.org, Debian Security Team <team@security.debian.org>

Hi,

The following vulnerability was published for tiff.

CVE-2023-3618[0]:
| 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.


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

For further information see:

[0] https://security-tracker.debian.org/tracker/CVE-2023-3618
    https://www.cve.org/CVERecord?id=CVE-2023-3618
[1] https://gitlab.com/libtiff/libtiff/-/issues/529

Please adjust the affected versions in the BTS as needed.

Regards,
Salvatore

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

From: László Böszörményi (GCS) <gcs@debian.org>

To: Salvatore Bonaccorso <carnil@debian.org>, 1040945@bugs.debian.org

Subject: Re: Bug#1040945: tiff: CVE-2023-3618

Date: Wed, 12 Jul 2023 22:12:50 +0200

Hi Salvatore,

On Wed, Jul 12, 2023 at 9:39 PM Salvatore Bonaccorso <carnil@debian.org> wrote:
> Source: tiff
> Version: 4.5.1-1
> CVE-2023-3618[0]:
> | 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.
[...]
> Please adjust the affected versions in the BTS as needed.
 Done my quick testing. My experience is the following.
1) libtiff6 and libtiff-tools are both 4.5.1-1 (ie, Trixie): the tool
reports several warnings, exists with 1 (non-zero) but doesn't
segfault. Even tried with valgrind, still no segfault.
2) libtiff6 is 4.5.1-1 backported to Bookworm and libtiff-tools are
not, ie it's 4.5.0-6 : the tool reports the same warnings like above,
but this time it _does_ segfault.
3) If libtiff-tools also updated to 4.5.1-1 on Bookworm: it's like the
first case, several warnings, non-zero exit code without a segfault.

In short, it seems:
- it's a non-dsa as only a crash in a CLI tool (which has end of life now),
- doesn't affect the library,
- while 4.5.0-6 (and in fact, at least from 4.5.0-1) is vulnerable,
4.5.1-1 fixed this issue.

But you may find it otherwise, I do not alter this report in the BTS.

Regards,
Laszlo/GCS

Send a report that this bug log contains spam.