public inbox for glibc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "max at cxib dot net" <sourceware-bugzilla@sourceware.org>
To: glibc-bugs@sources.redhat.com
Subject: [Bug libc/12671] multiple vulnerabilities in netdb.h/aliases.h/glob.h
Date: Thu, 26 May 2011 05:31:00 -0000	[thread overview]
Message-ID: <bug-12671-131-IX2tEsTvBf@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-12671-131@http.sourceware.org/bugzilla/>

http://sourceware.org/bugzilla/show_bug.cgi?id=12671

--- Comment #3 from Max <max at cxib dot net> 2011-05-26 05:31:13 UTC ---
I have once again analized problems in netdb. The difference between a gnu and
netbsd is such that NetBSD seems to be vulnerable to stack overflow. I was
unable to reproduce this on Linux. The reason is simple because NetBSD is based
on another code.

http://cvsweb.netbsd.org/bsdweb.cgi/src/lib/libc/net/getservbyname_r.c
http://cvsweb.netbsd.org/bsdweb.cgi/src/lib/libc/net/getservbyport_r.c

Anyway, in my opinion, we should do something with alloca() calls. Certainly
limit the use of the stack to store data.

-- 
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.


  parent reply	other threads:[~2011-05-26  5:31 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-04-13 19:30 [Bug libc/12671] New: " max at cxib dot net
2011-04-18 14:28 ` [Bug libc/12671] " thoger at redhat dot com
2011-05-23  3:07 ` drepper.fsp at gmail dot com
2011-05-26  5:31 ` max at cxib dot net [this message]
2014-02-16 19:42 ` jackie.rosen at hushmail dot com
2014-05-28 19:43 ` schwab at sourceware dot org
2014-06-27 13:37 ` fweimer at redhat dot com
2015-02-24 11:08 ` [Bug libc/12671] multiple vulnerabilities in netdb.h/aliases.h/glob.h (CVE-2012-6686) fweimer at redhat dot com
2015-02-24 11:41 ` [Bug libc/12671] multiple vulnerabilities in netdb.h/aliases.h/glob.h (CVE-2012-6686, CVE-2013-4357) fweimer at redhat dot com
2015-02-25 13:08 ` xiaoyang at soojoy dot net

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-12671-131-IX2tEsTvBf@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: 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).