All of lore.kernel.org
 help / color / mirror / Atom feed
From: Peter Korsgaard <peter@korsgaard.com>
To: Christian Stewart <christian@aperture.us>
Cc: Thomas Petazzoni <thomas.petazzoni@bootlin.com>,
	Anisse Astier <anisse@astier.eu>,
	"Yann E . MORIN" <yann.morin.1998@free.fr>,
	buildroot@buildroot.org
Subject: Re: [Buildroot] [PATCH v1 1/1] package/go: security bump to go1.21.8
Date: Wed, 20 Mar 2024 21:18:37 +0100	[thread overview]
Message-ID: <878r2cac82.fsf@48ers.dk> (raw)
In-Reply-To: <20240306003454.13352-1-christian@aperture.us> (Christian Stewart's message of "Tue, 5 Mar 2024 16:34:54 -0800")

>>>>> "Christian" == Christian Stewart <christian@aperture.us> writes:

 > Fixes the following CVEs:
 > CVE-2024-24783: crypto/x509: Verify panics on certificates with an unknown public key algorithm
 > CVE-2023-45290: net/http: memory exhaustion in Request.ParseMultipartForm
 > CVE-2023-45289: net/http, net/http/cookiejar: incorrect forwarding of sensitive headers and cookies on HTTP redirect
 > CVE-2024-24785: html/template: errors returned from MarshalJSON methods may break template escaping
 > CVE-2024-24784: net/mail: comments in display names are incorrectly handled

 > https://go.dev/doc/devel/release#go1.21.8

 > Signed-off-by: Christian Stewart <christian@aperture.us>

Committed to 2024.02.x and 2023.11.x, thanks.

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

      parent reply	other threads:[~2024-03-20 20:18 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-03-06  0:34 [Buildroot] [PATCH v1 1/1] package/go: security bump to go1.21.8 Christian Stewart via buildroot
2024-03-06  7:24 ` Peter Korsgaard
2024-03-20 20: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=878r2cac82.fsf@48ers.dk \
    --to=peter@korsgaard.com \
    --cc=anisse@astier.eu \
    --cc=buildroot@buildroot.org \
    --cc=christian@aperture.us \
    --cc=thomas.petazzoni@bootlin.com \
    --cc=yann.morin.1998@free.fr \
    /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.