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


  1. Follow the lemmy.world rules.
  2. Only tech related content.
  3. Be excellent to each other!
  4. Mod approved content bots can post up to 10 articles per day.
  5. Threads asking for personal tech support may be deleted.
  6. Politics threads may be removed.
  7. No memes allowed as posts, OK to post as comments.
  8. Only approved bots from the list below, to ask if your bot can be added please contact us.
  9. Check for duplicates before posting, duplicates may be removed
  10. 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
[–] aeronmelon@lemmy.world 31 points 1 day ago (1 children)

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.

[–] john89@lemmy.ca -4 points 1 day ago (2 children)

If you think a website is unsafe, don’t open it.

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.

[–] CommanderCloon@lemmy.ml 0 points 5 hours ago (1 children)
[–] john89@lemmy.ca 1 points 3 hours ago

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.

[–] boonhet@lemm.ee 5 points 14 hours ago (1 children)

I mean, Intel did it first and I do believe AMD and Qualcomm also followed suit.

[–] john89@lemmy.ca 1 points 3 hours ago* (last edited 3 hours ago)

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.