From: random832@fastmail.com (Random832)
Subject: [TUHS] Old Unix vulnerabilities
Date: Sun, 14 May 2017 02:11:07 -0400 [thread overview]
Message-ID: <1494742267.712158.975859880.2F405BBE@webmail.messagingengine.com> (raw)
In-Reply-To: <alpine.BSF.2.20.1705140929150.67621@aneurin.horsfall.org>
On Sat, May 13, 2017, at 19:34, Dave Horsfall wrote:
> OK, I'll kick it off.
Oh, and since we're doing this... I independently noticed a buffer
overflow vulnerability in mkdir, and later discovered that someone else
had actually published a working exploit for the same bug... in 2004.
http://archive.cert.uni-stuttgart.de/bugtraq/2004/06/msg00035.html
next prev parent reply other threads:[~2017-05-14 6:11 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-13 23:34 Dave Horsfall
2017-05-14 5:52 ` Random832
2017-05-15 9:46 ` Tony Finch
2017-05-14 6:11 ` Random832 [this message]
2017-05-18 17:32 ` Tim Newsham
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=1494742267.712158.975859880.2F405BBE@webmail.messagingengine.com \
--to=random832@fastmail.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 NNTP newsgroup(s).