First public macOS kernel memory corruption exploit on Apple M5

commandersaki•1 minute ago

I bought the M5 specifically cause of MIE. Now I feel dumb.

yieldcrv•20 minutes ago

from what they demonstrated, this seems to only be a $100,000 exploit in Apple's bug bounty platform, but if they package it right, it could be a $1.5 million exploit

They simply have to show it against a beta version of MacOS, and frame it as unauthorized access, and maybe from locked mode if possible

vsgherzi•about 2 hours ago

unfortunately a little light on the details. I'm very curious how the bug survived through MTE

vsgherzi•about 2 hours ago

Upon further reading on data only attacks

(https://www.usenix.org/publications/loginonline/data-only-at...)

This makes more sense. You don't trigger MTE since you're not doing anything for force MTE to take action the program isn't actually changing.

My other question would be, why didn't apple use fbounds checking here? They've been doing it aggressively everywhere else.

MTE plus fbounds checking everywhere should lead to an extremly hardened OS

pjmlp•about 1 hour ago

Quite strange indeed, given that was one of the main points on their security conference a few months ago.

vsgherzi•22 minutes ago

I can only imagine that

1. it’s to performance sensitive

2. The os is so darn large it’s hard to recompile everything

landr0id•about 2 hours ago

GPU memory/shaders/etc. isn't protected by MTE or PAC. They said "data-only", so I guess GPU commands could fit into this description.

dorianmariecom•about 2 hours ago

Memory Tagging Extension

Arm published the Memory Tagging Extension (MTE) specification in 2019 as a tool for hardware to help find memory corruption bugs. MTE is a memory tagging and tag-checking system, where every memory allocation is tagged with a secret. The hardware guarantees that later requests to access memory are granted only if the request contains the correct secret. If the secrets don’t match, the app crashes, and the event is logged. This allows developers to identify memory corruption bugs immediately as they occur.

https://support.apple.com/guide/security/operating-system-in...

AgentME•about 1 hour ago

First Mozilla, now even Apple is making up fake vulnerabilities to hype up Mythos. /s

baq•29 minutes ago

Cisco put up a totally bogus 10.0 CVE just for this reason, too

bredren•about 1 hour ago

Did the article get edited? There is not much description of the field trip.

First public macOS kernel memory corruption exploit on Apple M5

⚡ Community Insights

Discussion (11 Comments)Read Original on HackerNews