| ▲ | First public macOS kernel memory corruption exploit on Apple M5(blog.calif.io) |
| 238 points by quadrige 7 hours ago | 41 comments |
| |
|
| ▲ | dgellow 4 hours ago | parent | next [-] |
| The world is so not ready for the impact of LLMs on security issues. If true, congrats to the Calif team. It’s likely too technical for me to understand in details but looking forward to reading the 55 pages report |
| |
| ▲ | iqihs 3 hours ago | parent [-] | | you're assuming that blue teams and engineers are sitting around twiddling their thumbs | | |
| ▲ | nvr219 2 hours ago | parent | next [-] | | Most companies in the world do not have “blue teams”. They barely have any kind of security employee. | | | |
| ▲ | dgellow 3 hours ago | parent | prev [-] | | Not at all. I’m considering that the amount of vulnerable software in the wild is very, very large, with most organizations not managing their systems properly. Imagine all the small to medium size companies that do not have budgets for a dedicated, talented security team. And all the software that will never be patched. We are at the beginning of the exponential | | |
| ▲ | bottlepalm 26 minutes ago | parent [-] | | It makes you think will everything need to be rewritten from the ground up - potentially by AI itself, or AI having a very heavy hand in validating all of it. | | |
| ▲ | Gigachad 22 minutes ago | parent [-] | | There's so much much lower hanging fruit. Every job I've had has had basically everything massively out of date. Just keeping packages and framework versions up to date is a full time job and none of these companies have someone assigned to doing it. So much out of date software with known exploits left running for years. The only reason there hasn't been total disaster is no one has tried to hack it yet. |
|
|
|
|
|
| ▲ | vsgherzi 7 hours ago | parent | prev | next [-] |
| unfortunately a little light on the details. I'm very curious how the bug survived through MTE |
| |
| ▲ | dorianmariecom 6 hours ago | parent | next [-] | | 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... | | | |
| ▲ | vsgherzi 6 hours ago | parent | prev | next [-] | | 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 | | |
| ▲ | aiscoming 2 hours ago | parent | next [-] | | could be a different type of data only attack, which doesnt override the boundaries | | |
| ▲ | vsgherzi 2 hours ago | parent [-] | | Well it’s memory corruption so I think it’s pretty safe to assume it’s a bounds issue. I’m not sure if it’s possible to get this with something like type confusion tho I could be wrong here. |
| |
| ▲ | pjmlp 5 hours ago | parent | prev [-] | | Quite strange indeed, given that was one of the main points on their security conference a few months ago. | | |
| ▲ | vsgherzi 5 hours ago | parent [-] | | I can only imagine that 1. it’s to performance sensitive Or 2. The os is so darn large it’s hard to recompile everything |
|
| |
| ▲ | landr0id 6 hours ago | parent | prev | next [-] | | 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. | | |
| ▲ | LoganDark 4 hours ago | parent [-] | | IIRC, the GPU is behind a memory controller, so I doubt corrupting GPU memory alone could lead to an LPE. But I suppose it would give you someplace to store stuff if you can make something else read from it. |
| |
| ▲ | traceroute66 3 hours ago | parent | prev [-] | | > I'm very curious how the bug survived through MTE Its not the first time bugs get past MTE, happened with Google Pixel last year ... https://github.blog/security/vulnerability-research/bypassin... |
|
|
| ▲ | tkel an hour ago | parent | prev | next [-] |
| Another breathless marketing hype for Mythos. The curl report was much more sober. https://daniel.haxx.se/blog/2026/05/11/mythos-finds-a-curl-v... |
|
| ▲ | yieldcrv 5 hours ago | parent | prev | next [-] |
| 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 4 hours ago | parent [-] | | This is an lpe I believe what you’re describing is a zero click rce. | | |
| ▲ | yieldcrv 4 hours ago | parent [-] | | how much do you think it is worth in the bug bounty program | | |
| ▲ | vsgherzi 4 hours ago | parent [-] | | They don’t seem to state lpe as one of the bugs. Maybe 100k? There’s alot of factors that go into it so I’m really not able to say. I could see it going for lots more or lots less |
|
|
|
|
| ▲ | AgentME 5 hours ago | parent | prev | next [-] |
| First Mozilla, now even Apple is making up fake vulnerabilities to hype up Mythos. /sarcasm |
| |
| ▲ | baq 5 hours ago | parent | next [-] | | Cisco put up a totally bogus 10.0 CVE just for this reason, too | | | |
| ▲ | bstsb 4 hours ago | parent | prev | next [-] | | apple didn't "make up" this vulnerability, it was an external team reporting an issue | | |
| ▲ | oompydoompy74 2 hours ago | parent [-] | | The commenter was being sarcastic to highlight the current trend of dismissing Mythos, and LLM’s finding security vulnerabilities in general, as a non issue. |
| |
| ▲ | UqWBcuFx6NV4r 2 hours ago | parent | prev [-] | | screech nothing but stochastic parrots! glorified autocomplete! | | |
|
|
| ▲ | commandersaki 4 hours ago | parent | prev | next [-] |
| I bought the M5 specifically cause of MIE. Now I feel dumb. |
| |
| ▲ | vsgherzi 4 hours ago | parent | next [-] | | You shouldn’t, MTE blocks a large chunk of vulnerabilities and makes things like rop and jop very difficult if not impossible now. | | | |
| ▲ | aiscoming 2 hours ago | parent | prev [-] | | you should worry about npm/pypi malware, not memory corruption bugs |
|
|
| ▲ | bredren 5 hours ago | parent | prev [-] |
| Did the article get edited? There is not much description of the field trip. |
