public inbox for glibc-bugs@sourceware.org help / color / mirror / Atom feed
From: "cvs-commit at gcc dot gnu.org" <sourceware-bugzilla@sourceware.org> To: glibc-bugs@sourceware.org Subject: [Bug localedata/17325] iconv from ccsid 937 to utf-8 access invalid memory (CVE-2014-6040) Date: Wed, 03 Sep 2014 17:52:00 -0000 [thread overview] Message-ID: <bug-17325-131-GwUPvzXctJ@http.sourceware.org/bugzilla/> (raw) In-Reply-To: <bug-17325-131@http.sourceware.org/bugzilla/> https://sourceware.org/bugzilla/show_bug.cgi?id=17325 --- Comment #4 from cvs-commit at gcc dot gnu.org <cvs-commit at gcc dot gnu.org> --- This is an automated email from the git hooks/post-receive script. It was generated because a ref change was pushed to the repository containing the project "GNU C Library master sources". The branch, master has been updated via 41488498b6d9440ee66ab033808cce8323bba7ac (commit) from a78b712d405b55405b425e9b1453745615483003 (commit) Those revisions listed above that are new to this repository have not appeared on any other notification email; so we list those revisions in full, below. - Log ----------------------------------------------------------------- https://sourceware.org/git/gitweb.cgi?p=glibc.git;h=41488498b6d9440ee66ab033808cce8323bba7ac commit 41488498b6d9440ee66ab033808cce8323bba7ac Author: Florian Weimer <fweimer@redhat.com> Date: Wed Sep 3 19:45:43 2014 +0200 CVE-2014-6040: Crashes on invalid input in IBM gconv modules [BZ #17325] These changes are based on the fix for BZ #14134 in commit 6e230d11837f3ae7b375ea69d7905f0d18eb79e5. ----------------------------------------------------------------------- Summary of changes: ChangeLog | 17 +++++++++++++++++ NEWS | 7 ++++++- iconvdata/Makefile | 1 + iconvdata/ibm1364.c | 3 ++- iconvdata/ibm932.c | 5 +++-- iconvdata/ibm933.c | 2 +- iconvdata/ibm935.c | 2 +- iconvdata/ibm937.c | 2 +- iconvdata/ibm939.c | 2 +- iconvdata/ibm943.c | 5 +++-- iconvdata/run-iconv-test.sh | 18 ++++++++++++++++++ 11 files changed, 54 insertions(+), 10 deletions(-) -- You are receiving this mail because: You are on the CC list for the bug.
next prev parent reply other threads:[~2014-09-03 17:52 UTC|newest] Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top 2014-08-28 17:46 [Bug localedata/17325] New: iconv from ccsid 937 to utf-8 access invalid memory azanella at linux dot vnet.ibm.com 2014-08-28 17:46 ` [Bug localedata/17325] " azanella at linux dot vnet.ibm.com 2014-08-29 8:40 ` fweimer at redhat dot com 2014-08-29 9:37 ` fweimer at redhat dot com 2014-08-29 9:57 ` fweimer at redhat dot com 2014-08-29 12:06 ` azanella at linux dot vnet.ibm.com 2014-08-29 12:18 ` fweimer at redhat dot com 2014-09-02 5:40 ` [Bug localedata/17325] iconv from ccsid 937 to utf-8 access invalid memory (CVE-2014-6040) fweimer at redhat dot com 2014-09-03 17:52 ` cvs-commit at gcc dot gnu.org [this message] 2014-09-03 17:56 ` fweimer at redhat dot com 2014-09-05 13:16 ` cvs-commit at gcc dot gnu.org 2015-01-16 16:59 ` cvs-commit at gcc dot gnu.org 2015-01-16 17:03 ` cvs-commit at gcc dot gnu.org 2015-01-29 18:47 ` cvs-commit at gcc dot gnu.org 2015-02-23 14:23 ` cvs-commit at gcc dot gnu.org 2015-02-23 15:02 ` cvs-commit at gcc dot gnu.org
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=bug-17325-131-GwUPvzXctJ@http.sourceware.org/bugzilla/ \ --to=sourceware-bugzilla@sourceware.org \ --cc=glibc-bugs@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).