H.R. Giger · 2018-05-04 18:36
Well here we go again.
"Intel itself classifies four of the Spectre-NG vulnerabilities as "high risk"; the remaining four are rated as "medium". According to our own research, risks and attack scenarios at Spectre-NG are similar to those at Spectre – with one exception.
One of the Spectre-NG flaws simplifies attacks across system boundaries to such an extent that we estimate the threat potential to be significantly higher than with Spectre. Specifically, an attacker could launch exploit code in a virtual machine (VM) and attack the host system from there – the server of a cloud hoster, for example. Alternatively, it could attack the VMs of other customers running on the same server. Passwords and secret keys for secure data transmission are highly sought-after targets on cloud systems and are acutely endangered by this gap. Intel's Software Guard Extensions (SGX), which are designed to protect sensitive data on cloud servers, are also not Spectre-safe."
https://www.heise.de/ct/artikel/Exclusive-Spectre-NG-Multiple-new-Intel-CPU-flaws-revealed-several-serious-4040648.html
Yuki Nagato · 2018-05-09 18:11
>>4554
This is a rather important issue, with Intel lying for more than a decade.
Their MC Patches are a pretty fuarrrking bad response to this soykaf.
HELIOS · 2018-05-09 19:54
>Alternatively, it could attack the VMs of other customers running on the same server. Passwords and secret keys for secure data transmission are highly sought-after targets on cloud systems and are acutely endangered by this gap. Intel's Software Guard Extensions (SGX), which are designed to protect sensitive data on cloud servers, are also not Spectre-safe."
Sounds like a deliberate backdoor to own people who rely on Qubes-alike distributions.
Masami Eiri · 2018-05-09 20:40
>>4586
Can someone clue me in on what actually ended up happening with the last round of patches? I remember Linus flipping his soykaf on them and getting on the front page of HN and everyone freaking out and then nothing. I know that they pushed out the updates on linux that do something different but I never understood the story behind how the conflict ended..
My intel chips arent running slow like they claimed the working patch would have done, so i assume they fixed something along the way so that they didnt have to use the original patch?
Please someone tell or link me to the end of the saga with this, because I feel like I was left in the dark after I got the updates.
Jim Hilger · 2018-05-10 21:48
>>4591
All in all, chip performance went from 7% all the way to 30%ish in performance decay. Thats from a handful of servers I oversee.