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]

Message-ID: <7997.1319257403@turing-police.cc.vt.edu>
Date: Sat, 22 Oct 2011 00:23:23 -0400
From: Valdis.Kletnieks@...edu
To: bugs@....dhs.org
Cc: full-disclosure@...ts.grok.org.uk
Subject: Re: Symlink vulnerabilities

On Fri, 21 Oct 2011 19:59:59 EDT, bugs@....dhs.org said:

> Which I thought people really didn't care too much about anymore, I took a
> quick look at one of my ubuntu 8.04lts boxes:

> These are so easy to fix/avoid, I don't know why developers are still
> introducing them to their code.

It's Ubuntu.  What second userid is going to exploit the vulns?

Not sure if the above deserves a smiley or not.  But it's exactly the
mindset that causes these bugs.

In any case, the *right* answer isn't to play whack-a-mole fixing /tmp races,
what you should be doing is using pam_namespace or similar so each user gets
their own /tmp namespace.

Content of type "application/pgp-signature" skipped

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