From: Alexander Dahl <ada@thorsis.com>
To: ptxdist@pengutronix.de
Subject: Re: [ptxdist] [PATCH] libcurl: Version bump. 8.3.0 -> 8.4.0
Date: Thu, 12 Oct 2023 08:22:39 +0200 [thread overview]
Message-ID: <20231012-gaining-recycling-7fbcc78e2c38@ifak-system.com> (raw)
In-Reply-To: <20231011180236.1768772-1-christian.melki@t2data.com>
Hei hei,
Am Wed, Oct 11, 2023 at 08:02:36PM +0200 schrieb Christian Melki:
> Mostly smaller fixes.
> https://curl.se/changes.html#8_4_0
>
> Plugs two CVEs:
> CVE-2023-38546 cookie injection with none file
> CVE-2023-38545 SOCKS5 heap buffer overflow
For anyone interested, there's a nice read up on that heap overflow in
the blog of the maintainer:
https://daniel.haxx.se/blog/2023/10/11/how-i-made-a-heap-overflow-in-curl/
Greets
Alex
>
> Signed-off-by: Christian Melki <christian.melki@t2data.com>
> ---
> rules/libcurl.make | 4 ++--
> 1 file changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/rules/libcurl.make b/rules/libcurl.make
> index ad615bd87..61797e9ae 100644
> --- a/rules/libcurl.make
> +++ b/rules/libcurl.make
> @@ -15,8 +15,8 @@ PACKAGES-$(PTXCONF_LIBCURL) += libcurl
> #
> # Paths and names
> #
> -LIBCURL_VERSION := 8.3.0
> -LIBCURL_MD5 := 2fc6cf5cefa8b73e3826aa24befdccff
> +LIBCURL_VERSION := 8.4.0
> +LIBCURL_MD5 := 8424597f247da68b6041dd7f9ca367fe
> LIBCURL := curl-$(LIBCURL_VERSION)
> LIBCURL_SUFFIX := tar.xz
> LIBCURL_URL := https://curl.se/download/$(LIBCURL).$(LIBCURL_SUFFIX)
> --
> 2.34.1
>
>
next prev parent reply other threads:[~2023-10-12 6:24 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-11 18:02 Christian Melki
2023-10-12 6:22 ` Alexander Dahl [this message]
2023-10-18 7:42 ` [ptxdist] [APPLIED] " Michael Olbrich
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=20231012-gaining-recycling-7fbcc78e2c38@ifak-system.com \
--to=ada@thorsis.com \
--cc=ptxdist@pengutronix.de \
/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