Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Peter Korsgaard <peter@korsgaard.com>
To: buildroot@buildroot.org
Cc: Anisse Astier <anisse@astier.eu>,
	Christian Stewart <christian@aperture.us>
Subject: Re: [Buildroot] [PATCH] package/go: security bump to version 1.21.3
Date: Fri, 13 Oct 2023 20:44:02 +0200	[thread overview]
Message-ID: <875y3a1hxp.fsf@48ers.dk> (raw)
In-Reply-To: <20231011114736.311388-1-peter@korsgaard.com> (Peter Korsgaard's message of "Wed, 11 Oct 2023 13:47:35 +0200")

>>>>> "Peter" == Peter Korsgaard <peter@korsgaard.com> writes:

 > Fixes CVE-2023-39325: rapid stream resets can cause excessive work
 > A malicious HTTP/2 client which rapidly creates requests and immediately
 > resets them can cause excessive server resource consumption.  While the
 > total number of requests is bounded to the http2.Server.MaxConcurrentStreams
 > setting, resetting an in-progress request allows the attacker to create a
 > new request while the existing one is still executing.

 > go1.21.3 (released 2023-10-10) includes a security fix to the net/http
 > package.

 > Signed-off-by: Peter Korsgaard <peter@korsgaard.com>

For 2023.02.x and 2023.08.x I have instead bumped to 1.20.10 which
contains the same fix.

-- 
Bye, Peter Korsgaard
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot

      parent reply	other threads:[~2023-10-13 18:44 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-10-11 11:47 [Buildroot] [PATCH] package/go: security bump to version 1.21.3 Peter Korsgaard
2023-10-11 20:02 ` Christian Stewart via buildroot
2023-10-12 14:38 ` Peter Korsgaard
2023-10-13 18:44 ` 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=875y3a1hxp.fsf@48ers.dk \
    --to=peter@korsgaard.com \
    --cc=anisse@astier.eu \
    --cc=buildroot@buildroot.org \
    --cc=christian@aperture.us \
    /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