News for hackers. Stuff that matters.
Re:MIT researchers uncover ‘unpatchable’ flaw in Apple M1 chips by jprx on Friday June 10, 2022 @02:00PM (#31697385)
Additionally, if can find a way to trick a user into installing a malicious kext, why even bother with PACMAN? You already have arbitrary kernel code execution!
Re:MIT researchers uncover ‘unpatchable’ flaw in Apple M1 chips by throwaway290 on Friday June 10, 2022 @03:33PM (#31698480)
Perhaps the kext with the overflow may not necessarily look malicious? It can serve as an actually useful kext and pass review.
Re:MIT researchers uncover ‘unpatchable’ flaw in Apple M1 chips by aenis on Saturday June 11, 2022 @12:11AM (#31701850)
These days all kexts look malicious.
Re:MIT researchers uncover ‘unpatchable’ flaw in Apple M1 chips by ntauthority on Saturday June 11, 2022 @04:45AM (#31702966)
Yeah. The bundled ones in the main OS image are the worst. Who the hell knows what nefarious acts lie behind IOPCIFamily.kext?!

/s, though not entirely, moving more stuff to unprivileged contexts would be nice

Re:MIT researchers uncover ‘unpatchable’ flaw in Apple M1 chips by shp0ngle on Friday June 10, 2022 @11:52PM (#31701761)
yeah but if you can trick the user to do that, you can already trick him to do more
Re:MIT researchers uncover ‘unpatchable’ flaw in Apple M1 chips by sgjohnson on Saturday June 11, 2022 @01:05PM (#31706057)
First you need to trick Apple into signing that kext (which is getting more difficult by the day even for legitimate uses), or get the user to disable SIP first.
Re:MIT researchers uncover ‘unpatchable’ flaw in Apple M1 chips by throwaway290 on Sunday June 12, 2022 @03:04PM (#31717272)
Didn't many tools require disabling SIP, like Homebrew? Is this no longer true?
Re:MIT researchers uncover ‘unpatchable’ flaw in Apple M1 chips by sgjohnson on Monday June 13, 2022 @09:47AM (#31725498)
This hasn't been true for at least 2 major macOS releases.

But yes, there was a time when editing even /etc/sudoers required disabling SIP. That time is long gone.