Technology

Good writeup, but...

largest SIMD register on Zen2 is a 256bit register or 32 Bytes/characters. This exploit works by offering a half a register for unsuspecting processes to write data to, meaning 16 bytes/characters of data at a time. Please use passwords longer than 16 characters

This attack doesn't target passwords "typed by users", but AES binary passwords, which are either 128 or 256 bit long. Particularly it targets password used very often, like disk encryption passwords (both on end-user and server machines) or RAM encryption passwords (mostly used for securing VMs on servers).

What ends up in that register could be a password or cryptographic key, or it could be a chunk of HTML or a UUID, or who knows what.

It just happens that those same SIMD registers, are used to speed up encryption/decryption operations, so there is a very high chance of whatever data a malicious program manages to extract, to be either part of the key (about 30% chance), part of some random data either encrypted or decrypted (about 30% each), or a small chance of something else.

there is no way to target specific processes

when you are running javascript in a browser, you don't get as fine grained control over the host processor and the timing

Given that the attack can be executed millions of times per second, even with a low chance of hitting the right timing, the "beauty" of these attacks is that most of the time you will get the same data, which will be either detectable as "unsuccessful", or part of the disk/RAM encryption password. Simply running them for long enough, then looking at which data repeated the most, is going to give you the passwords to the most often running encryption processes.

The difference in impact to servers vs. user machines, is only because a server running the same software 24/7 is more likely to return meaningful data, than a user opening and closing random browser tabs, playing games, or turning the whole thing off.

Still, if the user has disk encryption enabled, that key is likely to be extracted even with a piece of JavaScript that fails the attack most of the time.