this post was submitted on 28 Jan 2025
277 points (97.3% liked)
Technology
61203 readers
4603 users here now
This is a most excellent place for technology news and articles.
Our Rules
- Follow the lemmy.world rules.
- Only tech related content.
- Be excellent to each other!
- Mod approved content bots can post up to 10 articles per day.
- Threads asking for personal tech support may be deleted.
- Politics threads may be removed.
- No memes allowed as posts, OK to post as comments.
- Only approved bots from the list below, to ask if your bot can be added please contact us.
- Check for duplicates before posting, duplicates may be removed
- Accounts 7 days and younger will have their posts automatically removed.
Approved Bots
founded 2 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
I need a bigger nerd than me to explain how much Apple users need to worry about this.
The main issue with these vulnerabilities is a loss in performance when the microcode patch gets applied.
On a more philosophical note, it's also a trend to release insecure products to tout performance metrics. Intel did it. Now it's apple's turn.
Don't trust corporations, ever.
Very. It's unpatchable. It's taking advantage of a speculative execution flaw, which is baked into the CPU microcode. This is the Apple M-chip version of Spectre/Meltdown that happened on x86 CPUs a few years ago.
The best Apple can do is attempt to add some code to the OS to help prevent this issue, but if Spectre was any example, it'll cause a hit to the CPU performance.
So this'll likely be mitigated soon, and while you're probably right about the performance hit (which will likely be minor), I don't think (most) Apple users need to be very worried about this.
Oh, yet another speculative execution flaw...
This is a real problem, and Apple can’t patch it out of the hardware. The only thing they can do is write software to run in advance of hardware execution to “randomize” when and where memory is written to and read from. That will slightly decrease the performance of these chips. The “older” chips from 2021 would see the worst performance reduction. M3 users probably won’t even be able to tell.
The attack vector is a web browser. Even a completely updated safari is vulnerable, but Chrome is seemingly easier to exploit (the way browsers store website data in memory is the key). An encrypted browser won’t change anything because the attack is reading the unencrypted data being displayed to the user.
It takes several minutes for a compromised website to perform the attack. So basic sense practices apply. If you think a website is unsafe, don’t open it. If you think something is happening, closing the suspicious sites immediately might stop the attack before any damage is done. I don’t know how easy it would be to compromise a trusted site, but it’s been done in the past.
Apple could potentially patch Safari to do things that make it harder for the attack to work correctly, and you can bet they’re already retooling the next generation of processors to get rid of this exploit. They did the same thing when an unpatchable exploit was found in the M1 series, M2s have a stopgap measure, and M3s were redrawn to make it an nonissue.
Ahh yes, back to the dark ages of the internet where just clicking the wrong link can completely compromise your system.
Thanks crapple and its useful idiots.
You do realize this kind of attack first appeared on x86 hardware, right?
https://thehackernews.com/2024/10/new-research-reveals-spectre.html?m=1
Yes, I realize that.
You do realize that this kind of attack happened after spectre and meltdown? Apple knew of the risks, but decided to ignore them.
I mean, Intel did it first and I do believe AMD and Qualcomm also followed suit.
Yes, and Apple decided to do the same thing knowing the risks.
"Intel did it!" is not a panacea for apple; it makes things worse for them.