From: "Daniel Cegiełka" <daniel.cegielka@gmail.com>
To: musl@lists.openwall.com
Subject: gethostbyname buffer overflow (glibc)
Date: Tue, 27 Jan 2015 17:59:36 +0100 [thread overview]
Message-ID: <CAPLrYES9oEF5XB32Q8tDxYuDJ8wOZ6iiZEQz3vxbun2vtqrYuQ@mail.gmail.com> (raw)
eg from:
http://www.openwall.com/lists/oss-security/2015/01/27/9
# gcc ghost.c && ./a.out
should not happen
retval = gethostbyname_r(name, &resbuf, temp.buffer,
sizeof(temp.buffer), &result, &herrno);
if (strcmp(temp.canary, CANARY) != 0) {
puts("vulnerable");
exit(EXIT_SUCCESS);
}
if (retval == ERANGE) {
puts("not vulnerable");
exit(EXIT_SUCCESS);
}
puts("should not happen");
exit(EXIT_FAILURE);
Double exit. Is something wrong with gethostbyname_r() in musl?
Daniel
next reply other threads:[~2015-01-27 16:59 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-27 16:59 Daniel Cegiełka [this message]
2015-01-27 17:10 ` Rich Felker
2015-01-27 17:23 ` Daniel Cegiełka
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=CAPLrYES9oEF5XB32Q8tDxYuDJ8wOZ6iiZEQz3vxbun2vtqrYuQ@mail.gmail.com \
--to=daniel.cegielka@gmail.com \
--cc=musl@lists.openwall.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.
Code repositories for project(s) associated with this public inbox
https://git.vuxu.org/mirror/musl/
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 NNTP newsgroup(s).