public inbox for glibc-bugs@sourceware.org help / color / mirror / Atom feed
From: "siddhesh at redhat dot com" <sourceware-bugzilla@sourceware.org> To: glibc-bugs@sources.redhat.com Subject: [Bug libc/14134] New: iconv() segfaults if the invalid multibyte character 0xffff is input when converting from IBM930 Date: Wed, 23 May 2012 01:48:00 -0000 [thread overview] Message-ID: <bug-14134-131@http.sourceware.org/bugzilla/> (raw) http://sourceware.org/bugzilla/show_bug.cgi?id=14134 Bug #: 14134 Summary: iconv() segfaults if the invalid multibyte character 0xffff is input when converting from IBM930 Product: glibc Version: unspecified Status: NEW Severity: critical Priority: P2 Component: libc AssignedTo: unassigned@sourceware.org ReportedBy: siddhesh@redhat.com CC: drepper.fsp@gmail.com Classification: Unclassified Description of problem: When converting IBM930 code with iconv(), if IBM930 code which includes invalid multibyte character "0xffff" is specified, then iconv() segfaults. Version-Release number of selected component (if applicable): glibc-2.5-81.el5_8.2 How reproducible: Always Steps to Reproduce: Run the following command: echo '0x0e 0x43 0x8c 0xff 0xff 0x43 0xbd 0x43 0xbd' | xxd -r | iconv -f IBM930 -t UTF-8 Actual results: Segfault Expected results: サiconv: illegal input sequence at position 3 -- Configure bugmail: http://sourceware.org/bugzilla/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
next reply other threads:[~2012-05-23 1:48 UTC|newest] Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top 2012-05-23 1:48 siddhesh at redhat dot com [this message] 2012-05-23 1:50 ` [Bug libc/14134] " siddhesh at redhat dot com 2012-06-06 13:25 ` siddhesh at redhat dot com 2014-06-13 14:05 ` fweimer at redhat dot com 2014-08-29 9:57 ` fweimer at redhat dot com 2014-08-29 9:59 ` fweimer at redhat dot com 2014-09-02 5:40 ` [Bug libc/14134] iconv() segfaults if the invalid multibyte character 0xffff is input when converting from IBM930 (CVE-2012-6656) fweimer at redhat dot com 2014-09-03 17:52 ` 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:50 ` cvs-commit at gcc dot gnu.org 2015-02-23 14:23 ` cvs-commit at gcc dot gnu.org 2015-02-23 15:03 ` 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-14134-131@http.sourceware.org/bugzilla/ \ --to=sourceware-bugzilla@sourceware.org \ --cc=glibc-bugs@sources.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: 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).