From: Peter Korsgaard <peter@korsgaard.com>
To: buildroot@buildroot.org
Cc: Romain Naour <romain.naour@gmail.com>,
Thomas Petazzoni <thomas.petazzoni@bootlin.com>
Subject: Re: [Buildroot] [PATCH-2023.02.x] package/{glibc, localedef}: security bump to 2.36-117
Date: Sat, 30 Sep 2023 16:20:00 +0200 [thread overview]
Message-ID: <87edifagkv.fsf@48ers.dk> (raw)
In-Reply-To: <20230929222724.2372985-1-peter@korsgaard.com> (Peter Korsgaard's message of "Sat, 30 Sep 2023 00:27:24 +0200")
>>>>> "Peter" == Peter Korsgaard <peter@korsgaard.com> writes:
> Fixes the following security issues:
> CVE-2023-4527: If the system is configured in no-aaaa mode via
> /etc/resolv.conf, getaddrinfo is called for the AF_UNSPEC address
> family, and a DNS response is received over TCP that is larger than
> 2048 bytes, getaddrinfo may potentially disclose stack contents via
> the returned address data, or crash.
> CVE-2023-4806: When an NSS plugin only implements the
> _gethostbyname2_r and _getcanonname_r callbacks, getaddrinfo could use
> memory that was freed during buffer resizing, potentially causing a
> crash or read or write to arbitrary memory.
> CVE-2023-5156: The fix for CVE-2023-4806 introduced a memory leak when
> an application calls getaddrinfo for AF_INET6 with AI_CANONNAME,
> AI_ALL and AI_V4MAPPED flags set.
> Signed-off-by: Peter Korsgaard <peter@korsgaard.com>
Committed to 2023.02.x, thanks.
--
Bye, Peter Korsgaard
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
prev parent reply other threads:[~2023-09-30 14:20 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-29 22:27 [Buildroot] [PATCH-2023.02.x] package/{glibc, localedef}: security bump to 2.36-117 Peter Korsgaard
2023-09-30 13:53 ` Romain Naour
2023-09-30 14:20 ` 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=87edifagkv.fsf@48ers.dk \
--to=peter@korsgaard.com \
--cc=buildroot@buildroot.org \
--cc=romain.naour@gmail.com \
--cc=thomas.petazzoni@bootlin.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