←back to thread

Memory Integrity Enforcement

(security.apple.com)
461 points circuit | 1 comments | | HN request time: 0.223s | source
Show context
gjsman-1000 ◴[] No.45187272[source]
I think hackers are not ready for the idea that unhackable hardware might actually be here. Hardware that will never have an exploit found someday, never be jailbroken, never have piracy, outside of maybe nation-state attacks.

Xbox One, 2012? Never hacked.

Nintendo Switch 2, 2025? According to reverse engineers... flawlessly secure microkernel and secure monitor built over the Switch 1 generation. Meanwhile NVIDIA's boot code is formally verified this time, written in the same language (ADA SPARK) used for nuclear reactors and airplanes, on a custom RISC-V chip.

iPhone? iOS 17 and 18 have never been jailbroken; now we introduce MIE.

replies(8): >>45187602 #>>45187884 #>>45188108 #>>45188283 #>>45188320 #>>45188444 #>>45190700 #>>45198883 #
1. bri3d ◴[] No.45188320[source]
I would deeply, strongly caution against using public exploit availability as any evidence of security. It’s a bad idea, because hundreds of market factors and random blind luck affect public exploitability more than the difficulty of developing an exploit chain.

Apple are definitely doing the best job that any firm ever has when it comes to mitigation, by a wide margin. Yet, we still see CVEs drop that are marked as used in the wild in exploit chains, so we know someone is still at it and still succeeding.

When it comes to the Xbox One, it’s an admirable job, in no small part because many of the brightest exploit developers from the Xbox 360 scene were employed to design and build the Xbox One security model. But even still, it’s still got little rips at the seams even in public: https://xboxoneresearch.github.io/games/2024/05/15/xbox-dump...