bugtraq - race condition in .net core System.IO.Directory.Delete allowing deletion of entire drives

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>] [day] [month] [year] [list]

Message-ID: <CA+jjjYQDG1QqcvQ+h4fGXfQYPNuJbEQ8f6XhyKEMgqJL7N+8Ug@mail.gmail.com>
Date: Mon, 17 Sep 2018 18:30:22 -0700
From: Joshua Hudson <joshudson@...il.com>
To: bugtraq@...urityfocus.com
Subject: race condition in .net core System.IO.Directory.Delete allowing
 deletion of entire drives

Here's a link to the original reporting of this class of bug:
https://seclists.org/bugtraq/2000/May/67

In looking for how to deal with this problem on Windows, I discovered
that .net core has
essentially the same security bug.

That file system node might have been a directory when FindNextFile
returned it, but it's a symlink to c:\users now. Goodbye half your
data (on average) before hitting a locked file.

https://github.com/dotnet/corefx/issues/32082

Microsoft does not want to believe this is a security bug. I do not
know what to do.