The second comment on the page sums up what I was going to point out:
I'd be careful making assumptions like this ; the same was true of exploits like Spectre until people managed to get it efficiently running in Javascript in a browser (which did not take very long after the spectre paper was released). Don't assume that because the initial PoC is time consuming and requires a bunch of access that it won't be refined into something much less demanding in short order.
Let's not panic, but let's not get complacent, either.
It depends, some M-devices are iOS and iPadOS devices, which would have this hardware issue but don't have actual background processing, so I don't believe it's possible to exploit it the way described.
On Mac, if they have access to your device to be able to set this up they likely have other, easier to manage, ways to get what they want than going through this exploit.
But if they had your device and uninterrupted access for two hours then yes.
Someone who understands it all more than I do could chime in, but that's my understanding based on a couple of articles and discussions elsewhere.
Yeah I don't think this is a big-ish problem currently. But by having this vulnerability to point to, other CPU vendors have a good reason not to include this feature in their own chips.
What I’m worried about is Apple overreacting and bottlenecking my M3 pro because “security”. We already saw how fixes for these types of vulnerabilities on Intel and AMD silicon affected performance; no thank you.
Second, even if it is not exploitable in a malicious way, this could be great for jailbreaking more modern Apple devices and circumvent Apple's bullshit.
I have studied computer architecture and hardware security at the graduate level—though I am far from an expert. That said, any student in the classroom could have laid out the theoretical weaknesses in a "data memory-dependent prefetcher".
My gut says (based on my own experience having a conversation like this) the engineers knew there was a "information leak" but management did not take it seriously. It's hard to convince someone without a cryptographic background why you need to {redesign/add a workaround/use a lower performance design} because of "leaks". If you can't demonstrate an attack they will assume the issue isn't exploitable.
The more probable answer is that the NSA asked for the backdoor to be left in. They do all the time, it's public knowledge at this point. AMD and Intel chips have the requisite backdoors by design, and so does Apple. The Chinese and Russian designed chips using the same architecture models, do not. Hmmmm... They have other backdoors of course.
It's all about security theatre for the public but decrypted data for large organizational consumption.
I don't believe that explanation is more probable. If the NSA had the power to compell Apple to place a backdoor in their chip, it would probably be a proper backdoor. It wouldn't be a side channel in the cache that is exploitable only in specific conditions.
The exploit page mentions that the Intel DMP is robust because it is more selective. So this is likely just a simple design error of making the system a little too trigger-happy.
If you can't demonstrate an attack they will assume the issue isn't exploitable.
Absolutely. Theory doesn't always equal reality. The security guys submitting CVE's to pad their resumes should absolutely be required to submit a working exploit. If they can't then they're just making needless noise
There are definitely bullshit cves out there but I don't think that's a good general rule. Especially in this context where it's literally unpatchable at the root of the problem.
A newly discovered vulnerability baked into Apple’s M-series of chips allows attackers to extract secret keys from Macs when they perform widely used cryptographic operations, academic researchers have revealed in a paper published Thursday.
The flaw—a side channel allowing end-to-end key extractions when Apple chips run implementations of widely used cryptographic protocols—can’t be patched directly because it stems from the microarchitectural design of the silicon itself.
The vulnerability can be exploited when the targeted cryptographic operation and the malicious application with normal user system privileges run on the same CPU cluster.
Security experts have long known that classical prefetchers open a side channel that malicious processes can probe to obtain secret key material from cryptographic operations.
This vulnerability is the result of the prefetchers making predictions based on previous access patterns, which can create changes in state that attackers can exploit to leak information.
The breakthrough of the new research is that it exposes a previously overlooked behavior of DMPs in Apple silicon: Sometimes they confuse memory content, such as key material, with the pointer value that is used to load other data.
The original article contains 744 words, the summary contains 183 words. Saved 75%. I'm a bot and I'm open source!
Considering how bad apple programmers are I am not surprised. I created an apple account just so I can get apple tv. Sadly I made the account on tv.apple.com and didn't make a 2fa so now I can not log into appleid.apple.com or iCloud.com or into my Apple 4k+
I think it's not the devs, but the managers who push the devs. It usually is. In Apple's case the managers want devs to desperately keep everything in such a a way that it only works with Apple, cant work with anything else or we might lose a customer! It probably won't have caused this particular problem, but you get the idea.
I have a dormant apple account for I had an iPhone before. The annoying thing about that account in particular is that I need an apple device to manage that, so without it I can only hope to remember that password correctly. But setting this aside, that iPhone was a neat little phone and I do miss it at times.
A revolution in composition. First titanium (making phones somehow less durable), and now they can't even keep their own chips secure because of the composition of the chip lol
That is some grade A armchair micro architecture design you got going there.
Apple completely switched their lineup to the obvious next big thing in processing in less than two years, improving efficiency and performance by leaps and bounds. It has had astounding improvements in terms of generating heat and preserving battery life in traditional computing and they did it without outright breaking backward compatibility.
But oh, it turns out three years later someone found an exploit. Guess the whole thing is shit then.
edit: oh yeah and traditional x86 manufacturers have had the same type of exploit while still running hot
edit2: This is not to say Apple is our holy Jesus lord and saviour, they're plenty full of shit, but the switch to ARM isn't one of those things
I don't use any Apple products and am not planning to change this in the near future, but man, the stuff I've read and seen about the M chips did left me absolutely amazed.