All of lore.kernel.org
 help / color / mirror / Atom feed
From: Julien Olivain <ju.o@free.fr>
To: Peter Korsgaard <peter@korsgaard.com>
Cc: buildroot@buildroot.org, Thomas Devoogdt <thomas@devoogdt.com>
Subject: Re: [Buildroot] [PATCH] package/libsoup3: security bump to version 3.6.1
Date: Sun, 15 Dec 2024 11:40:02 +0100	[thread overview]
Message-ID: <b87691d15522cb870bb707d8f87e92b0@free.fr> (raw)
In-Reply-To: <20241215100724.3835761-1-peter@korsgaard.com>

On 15/12/2024 11:07, Peter Korsgaard wrote:
> Fixes the following security vulnerabilities:
> 
> CVE-2024-52531: GNOME libsoup before 3.6.1 allows a buffer overflow in
> applications that perform conversion to UTF-8 in
> soup_header_parse_param_list_strict.  Input received over the network 
> cannot
> trigger this.
> 
> https://www.cve.org/CVERecord?id=CVE-2024-52531
> 
> CVE-2024-52532: GNOME libsoup before 3.6.1 has an infinite loop, and 
> memory
> consumption.  during the reading of certain patterns of WebSocket data 
> from
> clients.
> 
> https://www.cve.org/CVERecord?id=CVE-2024-52532
> 
> Changelog: https://gitlab.gnome.org/GNOME/libsoup/-/blob/3.6.1/NEWS
> 
> Signed-off-by: Peter Korsgaard <peter@korsgaard.com>

Applied to master, thanks.

> ---
>  package/libsoup3/libsoup3.hash | 4 ++--
>  package/libsoup3/libsoup3.mk   | 2 +-
>  2 files changed, 3 insertions(+), 3 deletions(-)
> 
> diff --git a/package/libsoup3/libsoup3.hash 
> b/package/libsoup3/libsoup3.hash
> index 37ecd2db84..23af347903 100644
> --- a/package/libsoup3/libsoup3.hash
> +++ b/package/libsoup3/libsoup3.hash
> @@ -1,4 +1,4 @@
> -# From 
> https://download.gnome.org/sources/libsoup/3.6/libsoup-3.6.0.sha256sum
> -sha256  
> 62959f791e8e8442f8c13cedac8c4919d78f9120d5bb5301be67a5e53318b4a3  
> libsoup-3.6.0.tar.xz
> +# From 
> https://download.gnome.org/sources/libsoup/3.6/libsoup-3.6.1.sha256sum
> +sha256  
> ceb1f1aa2bdd73b2cd8159d3998c96c55ef097ef15e4b4f36029209fa18af838  
> libsoup-3.6.1.tar.xz
>  # Locally calculated
>  sha256  
> b7993225104d90ddd8024fd838faf300bea5e83d91203eab98e29512acebd69c  
> COPYING
> diff --git a/package/libsoup3/libsoup3.mk 
> b/package/libsoup3/libsoup3.mk
> index f8a7e26159..f2f96c2def 100644
> --- a/package/libsoup3/libsoup3.mk
> +++ b/package/libsoup3/libsoup3.mk
> @@ -5,7 +5,7 @@
>  
> ################################################################################
> 
>  LIBSOUP3_VERSION_MAJOR = 3.6
> -LIBSOUP3_VERSION = $(LIBSOUP3_VERSION_MAJOR).0
> +LIBSOUP3_VERSION = $(LIBSOUP3_VERSION_MAJOR).1
>  LIBSOUP3_SOURCE = libsoup-$(LIBSOUP3_VERSION).tar.xz
>  LIBSOUP3_SITE = 
> https://download.gnome.org/sources/libsoup/$(LIBSOUP3_VERSION_MAJOR)
>  LIBSOUP3_LICENSE = LGPL-2.0+
> --
> 2.39.5
> 
> _______________________________________________
> 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:[~2024-12-15 10:40 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-12-15 10:07 [Buildroot] [PATCH] package/libsoup3: security bump to version 3.6.1 Peter Korsgaard
2024-12-15 10:40 ` Julien Olivain [this message]
2024-12-28  8:43 ` 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=b87691d15522cb870bb707d8f87e92b0@free.fr \
    --to=ju.o@free.fr \
    --cc=buildroot@buildroot.org \
    --cc=peter@korsgaard.com \
    --cc=thomas@devoogdt.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.