From: Carlos O'Donell <carlos@redhat.com>
To: Siddhesh Poyarekar <siddhesh@redhat.com>
Cc: libc-alpha@sourceware.org
Subject: Re: [PATCH] NEWS: Document CVE-2023-25139.
Date: Tue, 7 Feb 2023 18:39:02 -0500 [thread overview]
Message-ID: <6bf44d41-21ae-8b46-1418-861cafaf40a0@redhat.com> (raw)
In-Reply-To: <CAAmeS-aRfhwp4ONS890+P5K5j1pfB4m883Bz-4PThQUM3_ZH3A@mail.gmail.com>
On 2/6/23 13:36, Siddhesh Poyarekar wrote:
> On Mon, Feb 6, 2023 at 10:36 AM Carlos O'Donell <carlos@redhat.com> wrote:
>>
>> ---
>> NEWS | 7 ++++++-
>> 1 file changed, 6 insertions(+), 1 deletion(-)
>>
>> diff --git a/NEWS b/NEWS
>> index b227e72c9c..a7979a9cd3 100644
>> --- a/NEWS
>> +++ b/NEWS
>> @@ -21,7 +21,12 @@ Changes to build and runtime requirements:
>>
>> Security related changes:
>>
>> - [Add security related changes here]
>> + CVE-2023-25139: When the printf family of functions is called with a
>> + format specifier that uses an <apostrophe> (enable grouping) and a
>> + minimum width specifier, the resulting output could be larger than
>> + reasonably expected by a caller that computed a tight bound on the
>> + buffer size. The resulting larger than expected output could result
>> + in a buffer overflow in the printf family of functions.
>>
>
> LGTM.
>
> Reviewed-by: Siddhesh Poyarekar <siddhesh@sourceware.org>
>
Thanks. Pushed. I'm backporting to release/2.37/master right now.
--
Cheers,
Carlos.
prev parent reply other threads:[~2023-02-07 23:39 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-06 15:36 Carlos O'Donell
2023-02-06 18:36 ` Siddhesh Poyarekar
2023-02-07 23:39 ` Carlos O'Donell [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=6bf44d41-21ae-8b46-1418-861cafaf40a0@redhat.com \
--to=carlos@redhat.com \
--cc=libc-alpha@sourceware.org \
--cc=siddhesh@redhat.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).