Published: Mon, December 04, 2017
Tech | By Dwayne Harmon

Updating macOS can bring back the nasty "root" security bug

Updating macOS can bring back the nasty

The vulnerability was reported yesterday by a software developer on Twitter. All Macs running High Sierra appeared to be affected.

You'd think that would be the end of Apple's software troubles for this week, but you'd be wrong.

If you had yet to upgrade to the very latest version of High Sierra - that is, you were running 10.13.0 - and you install the patch and THEN upgraded to 10.13.1, the "root" access bug rears its head once again.

Recently, Mac computers were reported to be facing, what is referred to as the "root" issue bug.

This has been an incredibly awful week for Apple's operating systems.

The solution is a simple one - but one that has not been made sufficient clear by Apple.

It is noted that remotely realize the vulnerability impossible - the attacker must still have direct access to your device.

The serious and surprising root security bug in macOS High Sierra is back for some users, shortly after Apple declared it fixed.

The glitch is a rare and potentially embarrassing failure for Apple, whose software is generally known for being less prone to hacking and malware infections than Windows software from. As a temporary measure Apple recommends to activate the root user and set the password manually. To do this in the settings section "Users and groups" click on the button with a lock.

In a Medium post today, Ergin today said his Twitter disclosure about the Mac bug was met with "many reactions like a blast". "And worse, two of those Mac users say they've also tried re-installing Apple's security patch after that upgrade, only to find that the "root" problem still persists until they reboot their computer, with no warning that a reboot is necessary". "This is really REALLY bad".

"A password prompt that authenticates as root with an empty password would be a black eye for any OS".

Several experts have lambasted Apple for allowing the vulnerability in the first place. Users who had not installed macOS 10.13.1 and thus were running a prior version of the OS when they received the security update, found that installing 10.13.1 resurfaced the bug, according to a report from Wired.

Like this: