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 libc/11884] Unbounded alloca() in node parameter of getaddrinfo()
Date: Mon, 30 Jun 2014 17:24:00 -0000 [thread overview]
Message-ID: <bug-11884-131-YNPLLq6L90@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-11884-131@http.sourceware.org/bugzilla/>
https://sourceware.org/bugzilla/show_bug.cgi?id=11884
Florian Weimer <fweimer at redhat dot com> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |fweimer at redhat dot com
Flags| |security+
--- Comment #10 from Florian Weimer <fweimer at redhat dot com> ---
(In reply to Kees Cook from comment #5)
> Looks like this issue may be getting mitigated in other ways already:
>
> $ ./getaddrinfo 100
> getaddrinfo: Connection timed out
> $ ./getaddrinfo 1000
> getaddrinfo: Invalid argument
You would have to use a much larger argument, probably something around this:
$ ./getaddrinfo 16000000
I haven't got an unpatched glibc 2.7 around to test.
This may have been fixed by 34a9094f49241ebb72084c536cf468fd51ebe3ec, which
went into glibc 2.14. It has been backported by some downstream distributions,
e.g. <https://bugzilla.redhat.com/show_bug.cgi?id=797096>.
--
You are receiving this mail because:
You are on the CC list for the bug.
next prev parent reply other threads:[~2014-06-30 17:24 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <bug-11884-131@http.sourceware.org/bugzilla/>
2011-04-27 11:16 ` thoger at redhat dot com
2011-05-21 3:48 ` drepper.fsp at gmail dot com
2014-06-30 17:24 ` fweimer at redhat dot com [this message]
2010-08-05 5:12 [Bug libc/11884] New: Unbound " cdn at chromium dot org
2010-08-05 5:12 ` [Bug libc/11884] Unbounded " cdn at chromium dot org
2010-08-05 5:14 ` cdn at chromium dot org
2010-08-18 17:12 ` cdn at chromium dot org
2010-09-12 15:27 ` kees at outflux dot net
2010-09-12 15:41 ` kees at outflux dot net
2010-09-12 15:51 ` kees at outflux dot net
2010-09-12 20:41 ` cdn at chromium dot org
2010-09-12 22:56 ` kees at outflux dot net
2010-09-14 0:15 ` cdn at chromium dot org
2010-09-14 0:36 ` pasky at suse dot cz
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-11884-131-YNPLLq6L90@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: 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).