full-disclosure - Re: Microsoft Windows Vista/2003/XP/2000 file management security issues

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: <20070309184703.GH2791@sentinelchicken.org>
Date: Fri, 9 Mar 2007 13:47:03 -0500
From: Tim <tim-security@...tinelchicken.org>
To: "Roger A\. Grimes" <roger@...neretcs.com>
Cc: full-disclosure@...ts.grok.org.uk, bugtraq@...urityfocus.com
Subject: Re: Microsoft Windows Vista/2003/XP/2000 file
	management security issues

> So, let me get this. An app storing sensitive data doesn't make its own
> temp storage folders in a secure location, and instead relies upon one
> of the few folders in Windows that all users have Full Control to, and
> this is a Windows problem?  In Linux, if an app uses \tmp, is that a
> Linux issue?
> 
> Sounds like a developer issue to me.

No, I never said I blame Windows for a poorly written app such as this.
Don't jump to conclusions.        

Many developers might think using predictable filenames in TEMP might be
ok, since Windows doesn't (yet) have issues related to symlink attacks.
However, ZARAZA has shown a few ways to exploit this lame practice
anyway, beyond just a DoS.  That's all I'm saying.

tim

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