1.7.10p9, seems to be affected!Did you check to see if they were subject to it?
1.7.10p9, seems to be affected!Did you check to see if they were subject to it?
I had one kernel panic when installing 11.2.1 on my MBP 16. Yes, it booted back to 11.2. Then I tried again and went thru fine, now on 11.2.1.Anyone else having kernel panics when installing? Tried twice already on my MacBook Pro 16. Fortunately, it boots back to 11.2
The CVE doesn't agree with you.1.7.10p9, seems to be affected!
I am upgrading a new Macbook Pro M1, and the update seems to have hung. The progress bar has not moved for half an hour.Updating a Catalina MBP with this update. Downloaded quickly, but the update itself is taking a lot longer than you'd expect for simply an sudo patch. Must have other stuff in the Catalina update as well. OK, there go the fans on my MBP.
Mine has gone real slow...48 min...is now 11 min. I guess patience is a virtue that I don’t haveI am upgrading a new Macbook Pro M1, and the update seems to have hung. The progress bar has not moved for half an hour.
I have read of one other person having kp as well but, said member was in a different thread, if I am not mistaken.Anyone else having kernel panics when installing? Tried twice already on my MacBook Pro 16. Fortunately, it boots back to 11.2
I never got a timer, it just had the progress bar and it hung for 45 minutes. I force rebooted it, it rebooted a few times, now I got a progress bar and timer, with 10 minutes. My intel 16 had no problems. A little annoyed that we, once again, have update after an update.Mine has gone real slow...48 min...is now 11 min. I guess patience is a virtue that I don’t haveI was surprised how large this update was.
Did you see the article posted just a few minutes ago?Hoping & praying that a fix will come to allow my MBP to work off the battery....as soon as I updated to Big Sur...my battery says 1% contact service...now it only works when its plugged in....so much for portability![]()
Note to self: Sudo is a command-line tool related to super user access privileges (should have been defined in article IMO).
Now if it could just come standard with allowing us to use TouchID instead of typing our password.
Oh thanks, but here they say the version is vulnerable but not patched. Not a trustable source?The CVE doesn't agree with you.
Sudo Heap-Based Buffer Overflow Vulnerability — CVE-2021-3156 | CISA
us-cert.cisa.gov
Is Apple the first? Did other Unix and Linux push out the update too?
will be probably included in the next beta, but you can install it manually by downloading the pkg from https://github.com/sudo-project/sudo/releases/download/SUDO_1_9_5p2/sudo-1.9.5p2.mac1100.pkgAssuming it hasn't yet been fixed in the 11.3 betas?
This will not solve the problem because it won't replace the vulnerable version of sudo– it will leave the old one in /usr/bin and put a new copy in /usr/local/bin. Anyone running /usr/bin/sudo will run the old vulnerable version.will be probably included in the next beta, but you can install it manually by downloading the pkg from https://github.com/sudo-project/sudo/releases/download/SUDO_1_9_5p2/sudo-1.9.5p2.mac1100.pkg
Worked for me.
<shrug> Interesting that different advisories say different things. You can leave the snark aside, I'd hope that sudo's own homepage would correctly detail which versions had the bug.Oh thanks, but here they say the version is vulnerable but not patched. Not a trustable source?
Sudo.ws
Installing the PAM isn’t that hard; having to re-add it after each update is slightly annoying, though.Now if it could just come standard with allowing us to use TouchID instead of typing our password.