Want to read Slashdot from your mobile device? Point it at m.slashdot.org and keep reading!

 



Forgot your password?
typodupeerror
×
Security Intel Operating Systems Hardware

Researchers Discover SplitSpectre, a New Spectre-like CPU Attack (zdnet.com) 48

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.
This discussion has been archived. No new comments can be posted.

Researchers Discover SplitSpectre, a New Spectre-like CPU Attack

Comments Filter:
  • Missing Information (Score:4, Interesting)

    by Jane Q. Public ( 1010737 ) on Tuesday December 04, 2018 @10:54PM (#57751162)
    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.
    • by Waffle Iron ( 339739 ) on Tuesday December 04, 2018 @11:52PM (#57751286)

      time to dig out my old kim-1 and forth env.

      Sorry, but security researchers have recently discovered that due fundamental architectural issues, a hypothetical malicious program could trivially access *all* of the data on any 6502-based system.

  • They laughed (Score:4, Insightful)

    by Anonymous Coward on Tuesday December 04, 2018 @11:19PM (#57751228)

    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.

  • 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

    • Re: (Score:3, Insightful)

      by vyvepe ( 809573 )

      No, Linus is right. The performance impact of the patches is big.

      If you have up to date browser then you do not have a problem. Resolution of timers available from scripts is lowered to make this attack infeasible.

      If you are running executable from web then you have much bigger worry than spectre. The executable can damage you directly instead of trying to rely on a a "cooperation" of another process.

      These bugs are mostly a serious worry for companies renting virtual machines where executables run in the im

      • Why is this marked insightful? This has nothing to do with "browsers" or the "web".
        • Comment removed based on user account deletion
        • by vyvepe ( 809573 )

          Why is this marked insightful? This has nothing to do with "browsers" or the "web".

          It has a LOT to do with browsers and web. It has a lot to do with anything which runs a code downloaded somewhere from internet. Browsers with their java script engines are the first and the most easy target That is because the browsers run any java script from any hacked or malicious web site. Some email clients can interpret java script too. Disable java script in email client (if it executes it at all - most probably do not do it nowadays). Disable java script in browser or update the browser. It is reco

  • by Anonymous Coward

    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 n

  • 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?

Some people manage by the book, even though they don't know who wrote the book or even what book.

Working...