It doesn't work for me, but I'm running Version 10.13.2 Beta (17C79a). So it looks like it is fixed in the next update.
Last edited:
Not defending it however you can trivially ready an admin
Password on a Windows PC with a simple boot disk which is normal behaviour...
Nope, prompts for admin credentials if I do that, latest beta.
You will get to user/password prompt windows open at the same time (the first will spawn the second). Punch in root, click on password field, leave it blank, then click OK. It’ll fail the first time, then work the second time.Latest beta seems to have fixed it on mine too.
Latest beta seems to have fixed it on mine too.
I seem to recall that Apple made a change to the System Preferences authentication early on in the High Sierra betas, so that it no longer uses the native MacOS prompt that pops up outside of the app. The bug has likely existed ever since in every release version of High Sierra.
As long as the home directory isn't encrypted. Also booting in recovery mode and terminal.can do the same with Macs forever by just booting into single user mode
As long as the home directory isn't encrypted. Also booting in recovery mode and terminal.
Yeah, High Sierra has been the sloppiest release of macOS/OS X I've seen in a very long time.Welcome to OS X 10.0 again. Glad I stayed on El Captain and Sierra and iOS 10
Another Tim Cook quality control disaster. This man’s talent has no beginning.
You need to enter root/blank in the second credential window. It’ll fail the first time after a slight delay, then work the second time.I don't know what the magic seems to be. I cannot get root with no password to login after a dozen tries. It does not work with Users & Groups after another dozen tries. Every time I try to use root to unlock Users & Groups, I get a dialog box saying root is trying to unlock Users & Groups, and if cancel the dialog nothing happens. This is from my account which is an admin account. Oh, however, it just occurred to me, I am running Version 10.13.2 Beta (17C79), so it looks like it's fixed in the next update.
There appears to be a serious bug in macOS High Sierra that enables the root superuser on a Mac with with a blank password and no security check.
The bug, discovered by developer Lemi Ergin, lets anyone log into an admin account using the username "root" with no password. This works when attempting to access an administrator's account on an unlocked Mac, and it also provides access at the login screen of a locked Mac.
![]()
To replicate, follow these steps from any kind of Mac account, admin or guest:
1. Open System Preferences
2. Choose Users & Groups
3. Click the lock to make changes
4. Type "root" in the username field
5. Move the mouse to the Password field and click there, but leave it blank
6. Click unlock, and it should allow you full access to add a new administrator account.
At the login screen, you can also use the root trick to gain access to a Mac after the feature has been enabled in System Preferences. At the login screen, click "Other," and then enter "root" again with no password.
This allows for admin-level access directly from the locked login screen, with the account able to see everything on the computer.
It appears that this bug is present in the current version of macOS High Sierra, 10.13.1, and the macOS 10.13.2 beta that is in testing at the moment. It's not clear how such a significant bug got past Apple, but it's likely this is something that the company will immediately address.
Until the issue is fixed, you can enable a root account with a password to prevent the bug from working. We have a full how to with a complete rundown on the steps available here.
Article Link: Major macOS High Sierra Bug Allows Full Admin Access Without Password - How to Fix
Can just see Craig at the next keynote. “We have made it super easy to allow guests to use your Mac, now you don’t need to even setup a guest account and the user has full access”.
You need to enter root/blank in the second credential window. It’ll fail the first time after a slight delay, then work the second time.
10 years ago I started buying Apple products to avoid this kind of bugs.
Funny how things change![]()
I'm more surprised you'd still have High Sierra Developer Beta 2 installed on multiple Macs. On my 2012 rMBP those early betas were a mess, but the release builds still start to lag way more than they should with just a few apps open.I've tested High Sierra Beta 2 Update 1 (17A291m) on multiple machines now, and the bug still doesn't seem to trigger there, although it does have the new login UI.
More accurately it allows a bad actor to exploit the same bug to re-enable passwordless root.