public inbox for glibc-bugs@sourceware.org help / color / mirror / Atom feed
From: "fweimer at redhat dot com" <sourceware-bugzilla@sourceware.org> To: glibc-bugs@sourceware.org Subject: [Bug network/17630] endless loop in getaddr_r (CVE-2014-9402) Date: Thu, 18 Dec 2014 06:17:00 -0000 [thread overview] Message-ID: <bug-17630-131-h4ld5SNts6@http.sourceware.org/bugzilla/> (raw) In-Reply-To: <bug-17630-131@http.sourceware.org/bugzilla/> https://sourceware.org/bugzilla/show_bug.cgi?id=17630 Florian Weimer <fweimer at redhat dot com> changed: What |Removed |Added ---------------------------------------------------------------------------- Summary|endless loop in getaddr_r |endless loop in getaddr_r | |(CVE-2014-9402) Alias| |CVE-2014-9402 -- You are receiving this mail because: You are on the CC list for the bug.
next prev parent reply other threads:[~2014-12-18 6:17 UTC|newest] Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top 2014-11-20 13:44 [Bug network/17630] New: endless loop in getaddr_r yashavanth.hsn at gmail dot com 2014-11-20 14:47 ` [Bug network/17630] " schwab@linux-m68k.org 2014-11-24 16:29 ` yashavanth.hsn at gmail dot com 2014-11-24 16:31 ` yashavanth.hsn at gmail dot com 2014-11-24 16:58 ` schwab@linux-m68k.org 2014-11-25 9:48 ` yashavanth.hsn at gmail dot com 2014-12-09 13:34 ` schwab@linux-m68k.org 2014-12-12 14:06 ` fweimer at redhat dot com 2014-12-15 9:26 ` yashavanth.hsn at gmail dot com 2014-12-15 9:34 ` schwab@linux-m68k.org 2014-12-15 9:50 ` yashavanth.hsn at gmail dot com 2014-12-15 9:50 ` fweimer at redhat dot com 2014-12-16 9:10 ` cvs-commit at gcc dot gnu.org 2014-12-16 9:11 ` fweimer at redhat dot com 2014-12-18 1:07 ` cvs-commit at gcc dot gnu.org 2014-12-18 6:17 ` fweimer at redhat dot com [this message] 2015-01-14 12:19 ` [Bug network/17630] endless loop in getaddr_r (CVE-2014-9402) cvs-commit at gcc dot gnu.org 2015-01-14 13:13 ` cvs-commit at gcc dot gnu.org 2015-01-16 16:59 ` cvs-commit at gcc dot gnu.org 2015-01-16 17:02 ` cvs-commit at gcc dot gnu.org 2015-01-16 17:03 ` cvs-commit at gcc dot gnu.org 2015-01-21 13:56 ` cvs-commit at gcc dot gnu.org 2015-01-29 18:50 ` cvs-commit at gcc dot gnu.org 2015-02-12 13:05 ` cvs-commit at gcc dot gnu.org 2015-02-23 14:06 ` 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-17630-131-h4ld5SNts6@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).