unofficial mirror of libc-alpha@sourceware.org
 help / color / mirror / Atom feed
From: Carlos O'Donell via Libc-alpha <libc-alpha@sourceware.org>
To: Aurelien Jarno <aurelien@aurel32.net>, libc-alpha@sourceware.org
Subject: Re: [PATCH v2] Add NEWS entry for CVE-2016-10228 (bug 19519)
Date: Mon, 3 Aug 2020 14:54:48 -0400	[thread overview]
Message-ID: <f7171543-c17e-6e0f-5df1-8d41f1604207@redhat.com> (raw)
In-Reply-To: <20200730115152.3545521-1-aurelien@aurel32.net>

On 7/30/20 7:51 AM, Aurelien Jarno wrote:
> ---
>  NEWS | 4 ++++
>  1 file changed, 4 insertions(+)
> 
> diff --git a/NEWS b/NEWS
> index 1ef4a0a7a47..0ce408528f2 100644
> --- a/NEWS
> +++ b/NEWS
> @@ -154,6 +154,10 @@ Changes to build and runtime requirements:
>  
>  Security related changes:
>  
> +  CVE-2016-10228: An infinite loop has been fixed in the iconv program when
> +  invoked with the -c option and when processing invalid multi-byte input
> +  sequences.  Reported by Jan Engelhardt.
> +
>    CVE-2020-10029: Trigonometric functions on x86 targets suffered from stack
>    corruption when they were passed a pseudo-zero argument.  Reported by Guido
>    Vranken / ForAllSecure Mayhem.
> 

OK for 2.32. Please push ASAP.

Reviewed-by: Carlos O'Donell <carlos@redhat.com>

-- 
Cheers,
Carlos.


  reply	other threads:[~2020-08-03 18:54 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-07-30 11:51 [PATCH v2] Add NEWS entry for CVE-2016-10228 (bug 19519) Aurelien Jarno
2020-08-03 18:54 ` Carlos O'Donell via Libc-alpha [this message]
2020-08-03 21:26   ` Aurelien Jarno

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

  List information: https://www.gnu.org/software/libc/involved.html

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=f7171543-c17e-6e0f-5df1-8d41f1604207@redhat.com \
    --to=libc-alpha@sourceware.org \
    --cc=aurelien@aurel32.net \
    --cc=carlos@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).