From: Aurelien Jarno <aurelien@aurel32.net>
To: libc-stable@sourceware.org
Cc: Aurelien Jarno <aurelien@aurel32.net>
Subject: [2.31 COMMITTED 2/2] Add NEWS entry for CVE-2016-10228 (bug 19519)
Date: Mon, 3 Aug 2020 23:40:56 +0200 [thread overview]
Message-ID: <20200803214056.3767804-2-aurelien@aurel32.net> (raw)
In-Reply-To: <20200803214056.3767804-1-aurelien@aurel32.net>
(cherry picked from commit 17a0126abf02955cabf6256c67f8f9462a64163f)
---
NEWS | 4 ++++
1 file changed, 4 insertions(+)
diff --git a/NEWS b/NEWS
index 898501b1536..d3ffb822942 100644
--- a/NEWS
+++ b/NEWS
@@ -31,6 +31,10 @@ The following bugs are resolved with this release:
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.
--
2.27.0
prev parent reply other threads:[~2020-08-03 21:41 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-03 21:40 [2.31 COMMITTED 1/2] Rewrite iconv option parsing [BZ #19519] Aurelien Jarno
2020-08-03 21:40 ` Aurelien Jarno [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=20200803214056.3767804-2-aurelien@aurel32.net \
--to=aurelien@aurel32.net \
--cc=libc-stable@sourceware.org \
/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).