[1607, au] [Bug] Windows 10 default user profile is potentially writable by everyone

[Arthur]

The second link has the full details (inc. a manual fix).

 

https://www.reddit.com/r/sysadmin/comments/6qmn49/windows_10_default_user_profile_potentially/

 

I've been sitting on this issue for a while now because I wanted to give Microsoft the chance to fix the issue before it became wide-spread. But they decided it is not worth their time, so here I am.

 

If you had Windows 10 1607 installed on your system at any point in time (unless you did a fresh install of 1703 and not an upgrade) your default user profile might be writable by everyone, even after upgrading to 1703.

 

https://beingwinsysadmin.blogspot.co.uk/2017/07/bug-windows-10-default-user-profile-is.html

 

This is the story how I found out (by proxy) that the default user profile in Windows 10 is potentially writable by any user and the odyssey of trying to get this security bug fixed ... and failing to do so in the end.

 

For those who do not want to read the full story I posted a TL;DR version at the bottom.

 

[---Snip---]

 

TL;DR

 

• The default user profile under Windows 10 1607 (and any version upgraded from (and possibly through) that) is writeable by every user.
   
   
  
• Microsoft released a half-assed patch that only fixed the permissions for the "Startup" folder because it was the only exploit I mentioned in my original ticket.
   
   
  
• Microsoft released a CVE-2017-0295 article claiming that the issue has been fully fixed.
   
   
  
• Microsoft refuses to fix the issue properly because there is a "simple command everyone can execute" but has not (to my knowledge) told anyone about this command because everyone assumes the issue has been fixed by KB4022715 and KB4022725.
   
   
  
• Microsoft postponed the release of a proper fix until RS4 (March/April 2018) for an issue introduced in July 2016.
  

[ADMaster]

Does this bug effect only the DE / international version?

I just checked on a 1607 PC and all looks normal to me, I'm using en_us though.

 

Thanks,