3 ms·
If/when someone finds a way around the timer patch in your web browser (or if your browser doesn't have the patch yet for some weird reason), a website running
by jeroenhd 7y ago
If/when someone finds a way around the timer patch in your web browser (or if your browser doesn't have the patch yet for some weird reason), a website running javascript for long enough can extract kernel secrets and AES keys, a password manager's entire database, any application's authentication token and pretty much anything else in memory.
Executing such an attack is difficult and unreliable, but in my opinion this also means that casting a wide net might be worth it for the attacker instead of only using the exploit kit to target specific computers.
If you run any software in a virtual machine or docker app, this boundary is easily crossed. If you run any application whose supply chain might be attacked (for example, one of the million javascript files in an electron app), such an app can get root on your system through any sandboxing and virtualisation.
Edit: obviously, this is a worst case scenario.
- vbezhenar 7y agoMajority of users won't turn those protections off as they don't even know about them. So one can't really cast a wide net.
- bashinator 7y agoI think they meant casting a wide net in search of the small percentage of machines where the mitigation’s are turned off. An 0.01% success rate is okay if you hit ten million systems.
- snthd 7y agoIs it feisable to make privilege escalation of this sort impossible, by shifting cryptographic verification to dedicated hardware?
- waz0wski 7y agoIntel hardware has SGX, the concept of a secure enclave for sensitive data ... which is also vulnerable to the same class of speculative execution exploits on hardware generations prior to Cascade Lake Specifically it was a trio of vulnerabilities colloquially known as 'Foreshadow / L1TF': CVE-2018-3615, CVE-2018-3620, and CVE-2018-3646, https://en.wikipedia.org/wiki/Foreshadow_(security_vulnerability) https://en.wikipedia.org/wiki/Foreshadow_(security_vulnerabi...
- Maakuth 7y agoIt's not really a privilege escalation, but a method for completely bypassing memory protection. So keeping cryptographic verification outside the CPU is not enough, if you end up having your sensitive data in the RAM anyway.
- bluedino 7y agoWhat about on a database server that no web browser runs on?