public inbox for glibc-cvs@sourceware.org help / color / mirror / Atom feed
From: Dmitry Levin <ldv@sourceware.org> To: glibc-cvs@sourceware.org Subject: [glibc/release/2.27/master] Add NEWS entry for CVE-2016-10228 (bug 19519) Date: Tue, 21 Sep 2021 00:54:22 +0000 (GMT) [thread overview] Message-ID: <20210921005422.39D773858412@sourceware.org> (raw) https://sourceware.org/git/gitweb.cgi?p=glibc.git;h=8fb94f88249508cdc9addd01ca6124d3d8b94d69 commit 8fb94f88249508cdc9addd01ca6124d3d8b94d69 Author: Aurelien Jarno <aurelien@aurel32.net> Date: Thu Jul 30 10:07:33 2020 +0200 Add NEWS entry for CVE-2016-10228 (bug 19519) (cherry picked from commit 17a0126abf02955cabf6256c67f8f9462a64163f) Diff: --- NEWS | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/NEWS b/NEWS index b0ef9dc65a..9d13f62582 100644 --- a/NEWS +++ b/NEWS @@ -38,6 +38,10 @@ Deprecated and removed features, and other changes affecting compatibility: 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-2017-18269: An SSE2-based memmove implementation for the i386 architecture could corrupt memory. Reported by Max Horn.
reply other threads:[~2021-09-21 0:54 UTC|newest] Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20210921005422.39D773858412@sourceware.org \ --to=ldv@sourceware.org \ --cc=glibc-cvs@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: linkBe 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).