Slashdot Mirror
Microsoft Live Account Credentials Leaking From Windows 8 And Above (hackaday.com)
An anonymous reader writes: Discovered in 1997 by Aaron Spangler and never fixed, the WinNT/Win95 Automatic Authentication Vulnerability (IE Bug #4) is certainly an excellent vintage. In Windows 8 and 10, the same bug has now been found to potentially leak the user's Microsoft Live account login and (hashed) password information, which is also used to access OneDrive, Outlook, Office, Mobile, Bing, Xbox Live, MSN and Skype (if used with a Microsoft account). The bug itself seems to be present in all Windows systems since Windows 95 / NT, although only Windows 8 and above are effectively compromised. To see if your machine is affected, you may want to check the public demonstration of the exploit, set up by the guys from [Perfect Privacy] and based on [VladikSS] original work. Basically, the default User Authentification Settings of Edge/Spartan (also Internet Explorer, Outlook) lets the browser connect to local network shares, but erroneously fail to block connections to remote shares. To exploit this, an attacker would simply set up a network share. An embedded image link that points to that network share is then sent to the victim, for example as part of an email or website. As soon as the prepped content is viewed inside a Microsoft product such as Edge/Spartan, Internet Explorer or Outlook, that software will try to connect to that share in order to download the image. Doing so, it will silently send the user's Windows login username in plaintext along with the NTLMv2 hash of the login password to the attacker's network share.
Yes, the use of the word "share" can be misconstrued in this context.
Think of it in the context of heroin users "sharing" a needle, or when a child coughs directly into your face to "share" his cold with you.
Just cruising through this digital world at 33 1/3 rpm...
If I block outbound CIFS/SMB connections at the firewall, this should solve the issue, correct?
My eyes reflect the stars and a smile lights up my face.
If we had an article for every security vulnerability/backdoor found in a Microsoft product, it'd be impossible to find anything else on Slashdot.
What's newsworthy in this case is that the vulnerability remains unpatched since 1997. That is older than some of my kids. That's almost old enough to drink.
I am not your blowing wind, I am the lightning.
I always found it odd when accessing network shares between users with the same name and password that it never prompted me for one.
It was a great workaround back before active directory. If you didn't have access to a share, just figure out the owner's username (pre-populated on their lock screen), and create a new local user on your machine with the same username, connect to the share as that user, done.
And plenty old enough to drink in Europe ;)
It can be over the internet.
Confusion between the local network and the internet is the source of the problem. Windows is supposed to automatically log in to LOCAL shares. Instead it will automatically log in to shares anywhere on the internet, when it sees a link to a share.
For the love of all that is holy.. consolidate some of these logins, Microsoft!
They did that with Microsoft Passport (also known as .NET Passport, Microsoft Passport Network, and Windows Live ID).
I'm not sure how it fared or what the overall success rate of the consolidation was.
Just cruising through this digital world at 33 1/3 rpm...
It was a great workaround back before active directory. If you didn't have access to a share, just figure out the owner's username (pre-populated on their lock screen), and create a new local user on your machine with the same username, connect to the share as that user, done.
That workaround doesn't work... the password has to match as well.
What part of "shall not be infringed" is so hard to understand?
The critical thing that isn't getting enough attention here is that it requires IE to work. If you visit the test site in Chrome or Firefox it tells you to come back in IE. So it's not nearly as bad as it first appears.
const int one = 65536; (Silvermoon, Texture.cs)
SJW, n: "Someone I don't like, and by the way I'm a fuckwit" - AC
I'd prefer if it didn't do much distinction. One compromised device inside a local network shouldn't be enough to escalate it to control every device inside. If you trust devices on a basis "its in our network", then you are doing something wrong.
Its "login consolidation" (specifically the move with Windows 8 and 10 to use your Live/Hotmail/Outlook/Microsoft/etc login as your desktop login) that is the cause of this bug in the first place.
Thankfully I am on Windows 7 (and would use a local login rather than a cloud login in any case even on Windows 10) so this issue doesn't affect me. (no domains, VPNs or anything else involved either, its just a local login for my desktop)
I'm not sure what's more pathetic here, the age of this Microsoft bug, or the fact that so many firewalls do NOT block the relevant outbound TCP ports by default.
Seems both are equally as culpable.