I expect that they will have this patched tomorrow. This is the worst macOS vulnerability I've heard about in a long, long time.
I was trying to reproduce this on Sierra (my current OS) to see if it also happens there.
My experience: the root account was disabled, so this bug/exploit wouldn't work. If I enabled the root account (via Directory Utility) without any password, then sure I could log in as root from the login screen without a password, but that's no saying much.
So is the issue that the root account is enabled on High Sierra by default? If someone in High Sierra opens Directory Utility, clicks the lock and enters an admin password, then checks the edit menu, is there a menu item "Enable Root User" or "Disable Root User"?
What a disaster. Heads will roll and procedures will change over this one.
Its what happens when you have a clueless CEO running the operation. He thinks an iPad is a computer, so what do you expect.
This is unbelievably shoddy for a company like Apple. Just shows their inattention to all things Mac at the benefit of iPhone.
That's not to say OS11 isnt one of the buggiest iOS releases EVER, because it is.
"If someone knows the password of a user on your system". If someone knows your password to your admin user you pretty much deserve whatever happens
This is worrying. Apple need to focus on Mac and stop rushing! What’s happening with Apple?
Enter your own account password and it should unlock. I have no idea what's going on now.Admin account. I only have the one account. Tried this numerous times. It does not work for me.
/// WITHDRAW ///
Excellent answer; thank you for a thoughtful answer. But it brings up another question, as I looked at my not-yet-upgraded system, and it doesn't have a root password, and 'root' is not enabled. I've got my account as an Admin, and never set a 'root' password. But it isn't getting somehow a problem.
So on High Sierra, yes, 'root' has a blank password, but isn't the bug that the process of upgrading did an enablement. You only upgrade once, so the true bug is just that the status was changed when it shouldn't have been touched -- so setting it back to Disabled fixes it. Or is there some sort of daemon that keeps re-enabling it? If not, then how could 'root' -- blank password or not -- be a viable credential for any purpose at all (including attempting to log in or change the security locks)?
UPDATE: Tried it out -- in fact, the condition reactivates, and 'root' is re-enabled. Presumably not a daemon as the culprit, but the credential challenge routine itself does the deed as part of its work. Oh, my.
It has no impact until it does, and then it's basically keys to the kingdom. Usually a hacker has to be clever to get this level of access...I’ll download and install the fix. Meanwhile, this bug has zero impact on my life.
Only my home iMac. (Uni laptop not updated yet.). No other users. Not online until I am. And finally: I don’t store much of anything locally and my online life is an open book. I am not experiencing any anxiety.Wow. I know I'm not adding anything to the discussion, but just feel the need to say it again: "Wow."
This is disastrous. Used to be that "the root user is disabled by default" was a held up as a real security feature. Apparently it's not only enabled, but trivial to access.
I'd love to know what the mistake was that causes this. This strikes me as a teachable moment if ever there was one.
It has no impact until it does, and then it's basically keys to the kingdom. Usually a hacker has to be clever to get this level of access...
I'd imagine a lot of people have guest accounts (they're convenient) turned on and have no idea what root is.
I tried again. Entered root as the username in the first dialog box, left password blank. Entered root again in the second prompt, left password blank. And it worked!!![]()
are you seeing this in the terminal? SSH? I've been trying a few things to try to see if the issue can be replicated on the command line, but have not had success. Seems like the GUI is the only place to replicate the issue.
on my recently repaired mbp the name 'root' is already being used by another user