Attacker would need to have login on the machine.So is this a zero day, drive-by vulnerability? Or does the attacker have to have physical access?
It's a bug that elevates privileges.
Attacker would need to have login on the machine.So is this a zero day, drive-by vulnerability? Or does the attacker have to have physical access?
This has been one of my favorites.
Not exhaustively; static analysis and run-time analysis tools do exist; but they have limitations.I'd think we'd have better tools/procedures for finding bugs like this a lot sooner.
Is there not an automated tool that can look at some code and say "hey, right here it's possible for a heap overflow to occur and there's no error handling code to deal with it"?
Yes, you can delete su but it's better just to get the patch. Removing su could break other software on your computer so only do it if you're really sure what you're doing. Sudo can also be removed but I don't recommend it either.Is there no mitigation action that can be taken to seal this off until a patch is issued? Maybe something short of "delete su and sudo from your Mac"?
macOS security is top notch, pretty sure you need to input your password for most malware hacks, not all though so theoretically...yes.So this is a drive-by.
Visit a website that installs malware. Then a remote attacker can connect to your ip address and invoke the vulnerability?
Thanks for the link. I agree that the patch is best, but what do you do while awaiting the patch? And, since this impacts all older versions of macOS what about machines running OSs that are no longer patched? Upgrading to get patched isn't always an option.Yes, you can delete su but it's better just to get the patch. Removing su could break other software on your computer so only do it if you're really sure what you're doing. Sudo can also be removed but I don't recommend it either.
Example: https://unix.stackexchange.com/questions/426012/how-do-you-uninstall-the-sudo-command
Sigh ... if I must. The "root" cause is someone can "administer" themselves as an "owner" making them a PsEudo god with "permissions". It's like "hosting" an "A+ WRX", it's fun but very dangerous in the wrong hands behind the "wheel".Can someone please explain the 'root' cause of this? 😄
Except that Apple's care and updating of its BSD core is non-existent. If they were routinely updating to the latest, scanning for vulnerabilities, etc. then yeah they should get a pass. But they don't and so Apple should get all the blame.This vulnerability has been present for more than a decade in all sorts of UNIXes! It's not something at all limited to Apple's QA...
Mojave and Catalina are both affected as well.Why is only Big Sur affected and not Mojave or Catalina or earlier macOSes?
A bit like welding the doors shut on your car to stop other people from stealing itIs there no mitigation action that can be taken to seal this off until a patch is issued? Maybe something short of "delete su and sudo from your Mac"?
The headline and article summary only mention Big Sur. That is absolutely terrible and irresponsible writing from MacRumors.com. It will give Mac users that are not on Big Sur a false sense of security.Mojave and Catalina are both affected as well.
Yeah.It is fascinating that, despite the three RCs for 11.2, Apple did not care enough to update sudo to a patched version. Can someone with more knowledge explain? Am I missing something here?
Yeah.So, mostly free OSes. That's not much of a defense....
Devs knew about the potential, and chose not to address it. They would rather rush a beta product to market.
"Last week, there was speculation that the macOS Big Sur 11.2 update may address the sudo vulnerability, though it was not definitively known at the time if the bug would affect macOS. While it was found that sudo was left unchanged in macOS Big Sur 11.2, it is now clear that macOS is affected by the exploit."
As a trillion dollar company, this is something Apple should have been aware of, regardless. ZDNet does not reside in some dark corner of the Internet. It's a major news publication site for their industry. Shotty work.Yeah.
Poor reporting on MacRumors' part.
If you read the ZDNet article that is listed as the source (Link), which was written today, you'll see that "
A British security researcher has discovered today that a recent security flaw in the Sudo app also impacts the macOS operating system, and not just Linux and BSD, as initially believed."
So, the flaw was discovered last week. But they didn't know if macos was affected or not since the researchers who initially found the bug only tested a few Linux distributions. A different researcher confirmed today (2/3/21) that macos is also affected.
Also, according to that same article, "The researcher said he notified Apple of the issue earlier today."
So, Apple was only notified today about the flaw. So they could not have patched the vulnerability earlier than that. And the original researchers who discovered the flaw in the first place probably didn't make Apple aware of the vulnerability before today either.