full-disclosure - Re: Symlink vulnerabilities

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date: Sat, 22 Oct 2011 07:54:47 -0400 (EDT)
From: bugs@....dhs.org
To: "Tavis Ormandy" <taviso@...xchg8b.com>
Cc: full-disclosure@...ts.grok.org.uk
Subject: Re: Symlink vulnerabilities


I apologize as my search wasn't a complex method, just a quick grep for
signs of /tmp misuse. Indeed creating a directory under /tmp is a safeway
to handle tmp files.

> bugs@....dhs.org wrote:
>>
>> bashbug:
>>
>> /usr/bin/bashbug:TEMPDIR=$TMPDIR/bbug.$$
>>
>> Maybe I should use bashbug to report a bug in bashbug?
>>
>
> I took a quick look, it's actually using mkdir to create a temporary
> directory in /tmp, which it uses for collecting support files.
>
> This is actually a safe way to use /tmp, assuming you check the return
> code
> of mkdir (which it does). The mkdir() system call behaves very differently
> to open(), and is not vulnerable to these attacks.
>
> Tavis.
>
> --
> -------------------------------------
> taviso@...xchg8b.com | pgp encrypted mail preferred
> -------------------------------------------------------
>
> _______________________________________________
> Full-Disclosure - We believe in it.
> Charter: http://lists.grok.org.uk/full-disclosure-charter.html
> Hosted and sponsored by Secunia - http://secunia.com/
>


_______________________________________________
Full-Disclosure - We believe in it.
Charter: http://lists.grok.org.uk/full-disclosure-charter.html
Hosted and sponsored by Secunia - http://secunia.com/