public inbox for buildroot@busybox.net
 help / color / mirror / Atom feed
From: Thomas Perale via buildroot <buildroot@buildroot.org>
To: Bernd Kuhls <bernd@kuhls.net>
Cc: Thomas Perale <thomas.perale@mind.be>, buildroot@buildroot.org
Subject: Re: [Buildroot] [PATCH 2/2] package/libcurl: security bump to version 8.19.0
Date: Fri, 20 Mar 2026 16:55:12 +0100	[thread overview]
Message-ID: <20260320155512.176951-1-thomas.perale@mind.be> (raw)
In-Reply-To: <20260312164456.3185719-2-bernd@kuhls.net>

In reply of:
> https://curl.se/ch/8.19.0.html
> https://curl.se/docs/security.html
> 
> Fixes the following CVEs:
> 
> CVE-2026-3805: use after free in SMB connection reuse
> CVE-2026-3784: wrong proxy connection reuse with credentials
> CVE-2026-3783: token leak with redirect and netrc
> CVE-2026-1965: bad reuse of HTTP Negotiate connection
> 
> Switch to sha256 tarball hash provided by upstream.
> 
> Updated license hash due to copyright year bump:
> https://github.com/curl/curl/commit/e83c82f05f9b714086e62db9fe2ea9be522239bc
> 
> Signed-off-by: Bernd Kuhls <bernd@kuhls.net>

Applied to 2025.02.x & 2026.02.x. Thanks

> ---
>  package/libcurl/libcurl.hash | 9 ++++-----
>  package/libcurl/libcurl.mk   | 2 +-
>  2 files changed, 5 insertions(+), 6 deletions(-)
> 
> diff --git a/package/libcurl/libcurl.hash b/package/libcurl/libcurl.hash
> index de3f2402e9..5aec080ef9 100644
> --- a/package/libcurl/libcurl.hash
> +++ b/package/libcurl/libcurl.hash
> @@ -1,5 +1,4 @@
> -# Locally calculated after checking pgp signature
> -# https://curl.se/download/curl-8.18.0.tar.xz.asc
> -# signed with key 27EDEAF22F3ABCEB50DB9A125CC908FDB71E12C2
> -sha256  40df79166e74aa20149365e11ee4c798a46ad57c34e4f68fd13100e2c9a91946  curl-8.18.0.tar.xz
> -sha256  e18f1989333b70044b2adfb7dc2f905d0119dbdcac3bc9f4bc9d540e3a29de5b  COPYING
> +# From https://github.com/curl/curl/releases/tag/curl-8_19_0
> +sha256  4eb41489790d19e190d7ac7e18e82857cdd68af8f4e66b292ced562d333f11df  curl-8.19.0.tar.xz
> +# Locally computed
> +sha256  82f2f4427d6545ee5aaac4f0b80428da6cc8ba41c2cf5da3a03680ec327b9681  COPYING
> diff --git a/package/libcurl/libcurl.mk b/package/libcurl/libcurl.mk
> index 7ebf26c3b1..3d00a4a33a 100644
> --- a/package/libcurl/libcurl.mk
> +++ b/package/libcurl/libcurl.mk
> @@ -4,7 +4,7 @@
>  #
>  ################################################################################
>  
> -LIBCURL_VERSION = 8.18.0
> +LIBCURL_VERSION = 8.19.0
>  LIBCURL_SOURCE = curl-$(LIBCURL_VERSION).tar.xz
>  LIBCURL_SITE = https://curl.se/download
>  LIBCURL_DEPENDENCIES = host-pkgconf \
> -- 
> 2.47.3
> 
> _______________________________________________
> buildroot mailing list
> buildroot@buildroot.org
> https://lists.buildroot.org/mailman/listinfo/buildroot
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot

  reply	other threads:[~2026-03-20 15:55 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-03-12 16:44 [Buildroot] [PATCH 1/2] package/mpd: bump version to 0.24.9 Bernd Kuhls
2026-03-12 16:44 ` [Buildroot] [PATCH 2/2] package/libcurl: security bump to version 8.19.0 Bernd Kuhls
2026-03-20 15:55   ` Thomas Perale via buildroot [this message]
2026-03-12 20:08 ` [Buildroot] [PATCH 1/2] package/mpd: bump version to 0.24.9 Julien Olivain via buildroot

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=20260320155512.176951-1-thomas.perale@mind.be \
    --to=buildroot@buildroot.org \
    --cc=bernd@kuhls.net \
    --cc=thomas.perale@mind.be \
    /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