From: Peter Korsgaard <peter@korsgaard.com>
To: Fabrice Fontaine <fontaine.fabrice@gmail.com>
Cc: buildroot@buildroot.org
Subject: Re: [Buildroot] [PATCH 1/1] package/tiff: security bump to version 4.6.0
Date: Mon, 30 Oct 2023 18:23:57 +0100 [thread overview]
Message-ID: <87ttq82fde.fsf@48ers.dk> (raw)
In-Reply-To: <20231028161244.221857-1-fontaine.fabrice@gmail.com> (Fabrice Fontaine's message of "Sat, 28 Oct 2023 18:12:44 +0200")
>>>>> "Fabrice" == Fabrice Fontaine <fontaine.fabrice@gmail.com> writes:
> - Drop --without-x (now unrecognized)
> - Fix CVE-2023-40745: 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.
> - Fix CVE-2023-41175: 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.
> https://libtiff.gitlab.io/libtiff/releases/v4.6.0.html
> Signed-off-by: Fabrice Fontaine <fontaine.fabrice@gmail.com>
Committed to 2023.02.x and 2023.08.x, thanks.
--
Bye, Peter Korsgaard
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
prev parent reply other threads:[~2023-10-30 17:24 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-28 16:12 [Buildroot] [PATCH 1/1] package/tiff: security bump to version 4.6.0 Fabrice Fontaine
2023-10-30 17:23 ` Peter Korsgaard [this message]
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=87ttq82fde.fsf@48ers.dk \
--to=peter@korsgaard.com \
--cc=buildroot@buildroot.org \
--cc=fontaine.fabrice@gmail.com \
/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