bugtraq - Re: [Full-disclosure] Defense in depth -- the Microsoft way (part 8): execute everywhere!

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: <adc4ebd7bbff6745ba5ab9b8c3558386@localhost>
Date: Mon, 26 Aug 2013 09:16:07 -0600
From: James Lay <jlay@...ve-tothe-box.net>
To: <bugtraq@...urityfocus.com>
Subject: Re: [Full-disclosure] Defense in depth -- the Microsoft way (part  8): execute everywhere!

> On Sat, Aug 24, 2013 at 5:32 PM, Stefan Kanthak
> <stefan.kanthak@...go.de> wrote:
>> Hi,
>>
>> since it's start about 20 years ago Windows NT supports (fine 
>> grained)
>> ACLs, including the permission "execute file".
>>
>> In their very finite wisdom Microsoft but decided back then to have
>> this permission set on EVERY file a user creates (and assumes it is
>> set on local and remote file systems which dont support ACLs).
>>
>> The result: on Windows, malware can run everywhere (and since CWD
>> alias "." is in the path, can be started everywhere)!

Keep these coming...these are very interesting reads...thanks Stefan.

James