Live data from Hacker News

Zenbleed

lock.cmpxchg8b.com

341–350 of 378 posts

Re: Zenbleed

#341
post #340

Earlier quoted context omitted.

Under what circumstances is this not a medium? The only case this applies is if you have public runners running completely untrusted code, and if you're doing that I hope you're doing it on EPYC, which is fixed. And if you're doing that, you're probably mining crypto for randoms.

What about running JavaScript on a browser?

I am very doubtful that there exists any JavaScript that compiles to the specific instructions needed for this exploit.

Re: Zenbleed

#342

Earlier quoted context omitted.

The problem is, VMs aren't really "Virtual Machines" anymore. You're not parsing opcodes in a big switch statement, you're running instructions on the actual CPU, with a few hardware flags that the CPU says will guarantee no data or instruction overlap. It promises! But that's a hard promise to make in reality.

> you're running instructions on the actual CPU Just how many times is the average operating system workload (with or without a virtual machine also running a second average operating system workload) context switching a second? Like... unless I'm wrong... the kernel is the main process, and then it slices up processes/threads, and each time those run, they have their own EAX/EBX/ECX/ESP/EBP/EIP/etc. (I know it's RAX…

> Like... unless I'm wrong... the kernel is the main process,

A nice way of thinking about it is the kernel visualizes the CPU among multiple programs.

Great reading material on all this OS stuff: https://pages.cs.wisc.edu/~remzi/OSTEP/

Re: Zenbleed

#343

Earlier quoted context omitted.

That's not very convenient. I want docker to be able to use all my cores when I build an image.

Docker is not a VM. It uses the same kernel as the host

Only on Linux. On other systems it's a VM.

Re: Zenbleed

#344

Earlier quoted context omitted.

Yes but the Firecracker VMs are pinned to specific cores. So no two tenants never share a CPU core. Other than Rowhammer, has there been a hardware vulnerability of this nature that has worked x-core? I don't recall. Still, I think that if your company is handling user data it's worth seriously considering dedicated instances for any service that encounters plaintext user information.

Interesting. Physical cores or SMT virtual cores? Is there a link to their docs about this?

I honestly think I only ever saw an AWS Security Eng tweet about it lol sorry

Re: Zenbleed

#345
post #311
post #201

Earlier quoted context omitted.

It's good that they published patches early, isn't it?

Publishing patches early is good. Publishing patches unexpectedly before embargo isn't.

The second sentence seems to contradict the first.

Re: Zenbleed

#346

Earlier quoted context omitted.

Eric Brandwine (VP/DE @ AWS) said publicly in 2019 that EC2 had never scheduled different tenants on the same physical core at the same time, even before we learned about these kinds of side-channel attacks. https://www.youtube.com/watch?v=kQ4H6XO-iao&t=2485s

Yes (lowest vCPU seems to be 2 everywhere), and that protects against this attack. However, this thread was talking about airgapping hosts, which is needed for the general threat of VM escapes.

At least Fargate and Lightsail can select < 2 vCPU. (and maybe micro EC2 instance types?)

Re: Zenbleed

#347

Earlier quoted context omitted.

Yes (lowest vCPU seems to be 2 everywhere), and that protects against this attack. However, this thread was talking about airgapping hosts, which is needed for the general threat of VM escapes.

At least Fargate and Lightsail can select < 2 vCPU. (and maybe micro EC2 instance types?)

Well, that does sound like those were vulnerable then, if they happened to run on Zen 2. (Obviously microcode patched by now.)

As usual, cost is the biggest hindrance to security.

Re: Zenbleed

#348
post #340

Earlier quoted context omitted.

What about running JavaScript on a browser?

I am very doubtful that there exists any JavaScript that compiles to the specific instructions needed for this exploit.

It can be exploited through JavaScript according to CloudFlare: https://blog.cloudflare.com/zenbleed-vulnerability/

Re: Zenbleed

#350
Every time I think it's insane to contemplate making one's own chips something like this comes up, and I realize it's insane to let so much of our lives depend on these insanely complicated devices. It feels like walking on a tightrope above an unbounded fractal chasm.
Post reply on HN