The bug allows attackers to swipe data from a CPU’s registers. […] the exploit doesn’t require physical hardware access and can be triggered by loading JavaScript on a malicious website.
The bug allows attackers to swipe data from a CPU’s registers. […] the exploit doesn’t require physical hardware access and can be triggered by loading JavaScript on a malicious website.
My home server is only reachable via tailscale, so that is fine. But I have a VPS (and so does my work), the way I understand it that means I better hope my provider has patched their servers (and Hetzner in case of my job)? Good thing my Lemmy instance is on an ARM VPS, safe for now ;)
Tailscale… accessible from where? It would likely require an attacker to jump from the endpoint to a vulnerable application (or SSH) which, while possible, seems improbable. Maybe over time as the exploit gets packaged in more suites, or if targeted personally.
On the VPS, check cpuinfo to see if it’s one of the vulnerable ones. If it is, then I’d either ask them directly, avoid that kind of VPS for a while, or use it for non-sensitive stuff until it gets a fix.
ARM… will have its day. Speculative branching is too tempting to ignore, and too difficult to implement flawlessly. Just give them time 😉
It’s a wireguard based VPN, so asccessible from my Tailscale network ;) It would require someone hacking Tailscale, and if they manage that, they’d have a lot of more interesting, mainly corporate, targets than me :D
Planning to do so, I think it’s an EPYC. But I’m not home for another day and don’t have my certificate to SSH to the machine ;) For work I actually remembered we use a dedicated server, so all payload is controlled by us anyway.
As I said