From: Peter Korsgaard <peter@korsgaard.com>
To: Baruch Siach <baruch@tkos.co.il>
Cc: buildroot@buildroot.org
Subject: Re: [Buildroot] [PATCH] package/tiff: security bump to version 4.5.1
Date: Mon, 26 Jun 2023 09:04:19 +0200 [thread overview]
Message-ID: <87a5wmogb0.fsf@48ers.dk> (raw)
In-Reply-To: <87ilbaojqn.fsf@48ers.dk> (Peter Korsgaard's message of "Mon, 26 Jun 2023 07:50:08 +0200")
>>>>> "Peter" == Peter Korsgaard <peter@korsgaard.com> writes:
>>>>> "Baruch" == Baruch Siach <baruch@tkos.co.il> writes:
>> Hi Peter,
>> On Sun, Jun 25 2023, Peter Korsgaard wrote:
>>> Fixes the following security issues:
>>>
>>> - CVE-2023-1916: 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.
>>>
>>> - CVE-2023-25434: libtiff 4.5.0 is vulnerable to Buffer Overflow via
>>> extractContigSamplesBytes() at /libtiff/tools/tiffcrop.c:3215.
>>>
>>> - CVE-2023-26965: loadImage() in tools/tiffcrop.c in LibTIFF through 4.5.0
>>> has a heap-based use after free via a crafted TIFF image
>>>
>>> Drop the now upstream
>>> 0001-tiffcrop-Correct-simple-copy-paste-error-Fix-488.patch.
>> Should be removed from .checkpackageignore as well.
> Ahh yes, thanks for reminding me.
Committed with that fixed, thanks.
--
Bye, Peter Korsgaard
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
next prev parent reply other threads:[~2023-06-26 7:04 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-25 20:37 [Buildroot] [PATCH] package/tiff: security bump to version 4.5.1 Peter Korsgaard
2023-06-26 3:00 ` Baruch Siach via buildroot
2023-06-26 5:50 ` Peter Korsgaard
2023-06-26 7:04 ` Peter Korsgaard [this message]
2023-07-16 6:20 ` Peter Korsgaard
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87a5wmogb0.fsf@48ers.dk \
--to=peter@korsgaard.com \
--cc=baruch@tkos.co.il \
--cc=buildroot@buildroot.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox