Researchers Discover SplitSpectre, a New Spectre-like CPU Attack (zdnet.com)
An anonymous reader writes from a report via ZDNet: Three academics from Northeastern University and three researchers from IBM Research have discovered a new variation of the Spectre CPU vulnerability that can be exploited via browser-based code. The vulnerability, which researchers codenamed SplitSpectre, is a variation of the original Spectre v1 vulnerability discovered last year and which became public in January 2018. The difference in SplitSpectre is not in what parts of a CPU's microarchitecture the flaw targets, but how the attack is carried out. Researchers say a SplitSpectre attack is both faster and easier to execute, improving an attacker's ability to recover code from targeted CPUs. The research team says they were successfully able to carry out a SplitSpectre attack against Intel Haswell and Skylake CPUs, and AMD Ryzen processors, via SpiderMonkey 52.7.4, Firefox's JavaScript engine. The good news is that existing Spectre mitigations would thwart the SplitSpectre attacks.
I presume that since mitigation measures for Spectre also work against Split Spectre, that CPUs (like mine) which aren't vulnerable to Spectre are also not vulnerable to Split Spectre?
I realize that it's a bit of speculation but it seems like a reasonable conclusion.
I know it might surprise some people but not all recent processors are vulnerable. For example, according to intel, in their i7 lineup only their 45nm and 32nm process chips are vulnerable.
time to dig out my old kim-1 and forth env.
Oh you, managed languages are safe.
Okay so they aren't, but sandboxes are safe.
Okay alright there are bugs, but virtual machines are safe.
So about thos' virtual machines...
Yeah fuck you, throw another layer on, what does it matter.
linux has microcode updates as well!
Maybe its time to re-think not enabling the mitigations in the Linux by default?
This looking more exploitable in the wild all the time
Repeal the 17th Amendment TODAY! Also Please Read http://www.gnu.org/philosophy/right-to-read.html
The bigger and unspoken problem with these vulnerabilities and breaches that we've been seeing lately is that they all create significant penalties for the consumers along with a sense of being unable to do anything about them. People feel that the problems that can be fixed do so at the cost of time, and effort to patch, along with a near 50% reduction in power. Basically rendering their expensive computers impotent and useless paper weights. They also suffer a sense of hopelessness as there is little or nothing that they can do about it.
This all creates vulnerability fatigue, and worse still, indifference. Perhaps, even willful ignorance. People are increasingly saying; 'I'm tired of all this shit. I just want my stuff to work. I'm not going to worry about this shit anymore.'
So, rather than security being improved by researchers discoveries and the endless flood of "patches" and inconveniences. People are just closing their eyes and charging on ahead. 'Screw these esoteric vulnerabilities. Screw breaches. It happens. So what. The world doesn't end. Move on.'
People are sick and tired of hearing about risks, the inconveniences that they must endure, the scare mongering, and the ultimate futility of anything they do or think.
Frankly, I don't blame them.
News at 11:00.
Seriously - so they found another way to abuse spectre that still doesn't work with existing mitigation - what is exactly the important news here?