From: Peter Korsgaard <peter@korsgaard.com>
To: Fabrice Fontaine <fontaine.fabrice@gmail.com>
Cc: Anisse Astier <anisse@astier.eu>, buildroot@buildroot.org
Subject: Re: [Buildroot] [PATCH 1/1] package/nghttp2: security bump to version 1.57.0
Date: Mon, 30 Oct 2023 11:18:05 +0100 [thread overview]
Message-ID: <87bkcg5s82.fsf@48ers.dk> (raw)
In-Reply-To: <20231022211721.88737-1-fontaine.fabrice@gmail.com> (Fabrice Fontaine's message of "Sun, 22 Oct 2023 23:17:21 +0200")
>>>>> "Fabrice" == Fabrice Fontaine <fontaine.fabrice@gmail.com> writes:
> Fix CVE-2023-44487: The HTTP/2 protocol allows a denial of service
> (server resource consumption) because request cancellation can reset
> many streams quickly, as exploited in the wild in August through October
> 2023.
> Fix CVE-2023-35945: nghttp2 fails to release memory when PUSH_PROMISE or
> HEADERS frame cannot be sent, and nghttp2_on_stream_close_callback fails
> with a fatal error. For example, if GOAWAY frame has been received, a
> HEADERS frame that opens new stream cannot be sent.
> https://github.com/nghttp2/nghttp2/security/advisories/GHSA-vx74-f528-fxqg
> https://github.com/nghttp2/nghttp2/security/advisories/GHSA-6pcr-v3hg-752p
> https://github.com/nghttp2/nghttp2/compare/v1.41.0...v1.57.0
> 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 10:18 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-22 21:17 [Buildroot] [PATCH 1/1] package/nghttp2: security bump to version 1.57.0 Fabrice Fontaine
2023-10-25 19:16 ` Peter Korsgaard
2023-10-30 10:18 ` 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=87bkcg5s82.fsf@48ers.dk \
--to=peter@korsgaard.com \
--cc=anisse@astier.eu \
--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