Follow Slashdot stories on Twitter

 



Forgot your password?
typodupeerror
×
Bug Intel Security

Researchers Disclose New 'Inverse Spectre Attack' (digitaljournal.com) 96

A new Intel security flaw has been discovered that potentially allows passwords to be stolen. An anonymous reader quotes Digital Journal: As EE News reports, researchers said the new flaw enables an "inverse spectre attack". According to Giorgi Maisuradze and Professor Dr. Christian Rossow a ret2spec (return-to-speculation) vulnerability with the chips allows for would-be attackers to read data without authorization. According to Professor Rossow: "The security gap is caused by CPUs predicting a so-called return address for runtime optimization."

The implications of this are: "If an attacker can manipulate this prediction, he gains control over speculatively executed program code. It can read out data via side channels that should actually be protected from access." This means, in essence, that malicious web pages could interpret the memory of the web browser in order to access and copy critical data. Such data would include stored passwords.

"At least all Intel processors of the past ten years are affected by the vulnerabilities," reports EE News, adding "Similar attack mechanisms could probably also be derived for ARM and AMD processors...."

"Manufacturers were notified of the weaknesses in May 2018 and were granted 90 days to remedy them before the results were published. That deadline has now expired."
This discussion has been archived. No new comments can be posted.

Researchers Disclose New 'Inverse Spectre Attack'

Comments Filter:
  • Okay thanks (Score:2, Funny)

    by Anonymous Coward

    I will worry about it. I promise.

  • by Anonymous Coward

    Any clout the brand had has been destroyed in the past year. What shoddy system design.

  • Could probably... (Score:2, Interesting)

    by Anonymous Coward

    How much is intel paying for the AMD FUD this time?

  • by Anonymous Coward

    I can barely afford an old Core2Duo for 50 bucks (case and all). And I have actually for real been a target of my own country. How the hell am I supposed to mitigate all this? I run a well-"secured" Linux with at least daily updates of everything, but what's the point? Sure, a few of those bugs can be worked-around in software. But what does it matter? It takes a single proper one, and I'm done.

    I can only console myself with the fact, that if nothing happened until now, then nothing may happen. But I just c

    • Use an old processor without speculative execution features? Some lower end ARMs and Atoms also are immune, I think.

    • I can barely afford an old Core2Duo for 50 bucks (case and all).

      Should have bought an old Athlon for fifty bucks instead. Lots of us tried to tell you that Intel was unscrupulous. Buying used hardware helps increase the value of new hardware because buyers know that there will be a buyer for their surplus so that they don't have to pay to dispose of it. Even by buying a used Intel system, you helped out Intel. Full disclosure, I bought a fifty dollar C2D as well. I still have it, but I'm not using it. Maybe I'll give it away to someone who doesn't care about security, s

    • Comment removed based on user account deletion
    • by AHuxley ( 892839 )
      Buy an older computer and find a supported OS for it.
    • by Nite_Hawk ( 1304 )

      Terribly sorry to hear about your situation. I hope things improve! FWIW, I think it's helpful to look at these issues (and really the the world in general) as a system of probabilities. Even absent these vulnerabilities your system is quite likely vulnerable to some other attack vector (as is mine, and as is basically every computer on the planet). It's just a question of how difficult is it to exploit and how likely is it that someone is going to do so.

      If you are truly worried that your government mig

  • IMNSHO, the whole realm of Spectre/Meltdown vulnerabilities - while an interesting lab experiment - are complete horseshit. Consider:

    1) In order for ANY of these vulnerabilities to be useful, you MUST be running malware on your system. If so, you are already hosed.

    2) Given the enormous realms of malware extant than can much more quickly and easily grab your data (Hello, Equifax!), any true hacker would laugh at trying to use these vulnerabilities, because...

    3) The idea that malware can tickle the cache m
    • by drinkypoo ( 153816 ) <drink@hyperlogos.org> on Saturday August 11, 2018 @06:24PM (#57109100) Homepage Journal

      IMNSHO, the whole realm of Spectre/Meltdown vulnerabilities - while an interesting lab experiment - are complete horseshit.

      Intel apologists are equally irrational to YHWH apologists.

      In order for ANY of these vulnerabilities to be useful, you MUST be running malware on your system. If so, you are already hosed.

      Javascript. Malware hidden in software. Virtualization. These are all real-world scenarios which affect basically everyone.

      Given the enormous realms of malware extant than can much more quickly and easily grab your data (Hello, Equifax!), any true hacker would laugh at trying to use these vulnerabilities, because...

      You're already vulnerable to shooting, so why worry about stabbing?

      The idea that malware can tickle the cache millions of times to grab data (presuming it has not already been flushed), interpret said data and then prey that it is something useful, like passwords, when cache is normally filled with instructions more than data...

      ...has been demonstrated. Millions of times, so what? My computer does millions of things thousands of times per second.

      Any of you who are now delaying purchases, etc. while you twist your hanky are doing the rest of us a favor by forcing prices down, so - Keep It Up!!

      I'm not delaying purchases. I'm just happy I'm not using Intel, which is not only vulnerable to MELTDOWN, but is more vulnerable to SPECTRE-type attacks than my AMD CPU.

      • "Intel apologists are equally irrational to YHWH apologists."
        Considering that these vulnerabilities also (largely) apply to AMD and ARM, your cheap-shot snark is duly noted and ignored for the shit it is.
        "Javascript. Malware hidden in software. Virtualization. These are all real-world scenarios which affect basically everyone."
        Lots of word salad with no proof. Yawn...
        "You're already vulnerable to shooting, so why worry about stabbing?"
        That's a really stupid analogy, but let's pursue it for the fuck of it.
        • by drinkypoo ( 153816 ) <drink@hyperlogos.org> on Saturday August 11, 2018 @07:32PM (#57109378) Homepage Journal

          Considering that these vulnerabilities also (largely) apply to AMD and ARM, your cheap-shot snark is duly noted and ignored for the shit it is.

          Mitigation is cheaper on AMD, because they at least tried to do the right thing. And they only tend to be a problem for 64-bit ARM. The biggest failures here are Intel and IBM.

          Lots of word salad with no proof. Yawn...

          There's no proof that those are real-world scenarios?

          I can much more easily defend against a stabbing, because they need to be at very close range. (i.e. On your fucking system) whereas a bullet can travel over a mile and kill you.

          Javascript is on your system. Malware hidden in applications is real, and on people's systems.

          The rest of your statements are equally delusional and devoid of rationality, so...

          ...they're totally rational and you couldn't find any good arguments against them, either, so you just gave up. Noted.

          • by Anonymous Coward

            The question at the heart of the "so what?" argument is whether or not the person understands that the "brain" that is at the core of any microprocessor just does whatever its instructions tell it. If it gets an instruction to take the contents of register A and add the contents of register B, (perform binary addition) and store them back in A, that's what it will do. The security applied by the operating system involves basically making sure that the software the user is trying to make it run is to make

          • "Mitigation is cheaper on AMD, because they at least tried to do the right thing. And they only tend to be a problem for 64-bit ARM. The biggest failures here are Intel and IBM."
            OK, so everyone replace all of your Intel, 32-bit ARM and IBM CPUs immediately, because...

            "There's no proof that those are real-world scenarios?"
            Nope, none outside of lab conditions. Show me otherwise....I'm waiting....

            "Javascript is on your system. Malware hidden in applications is real, and on people's systems."
            Wait a minute! Th
          • Javascript is on your system. Malware hidden in applications is real, and on people's systems.

            The capabilities of the attack vector are important. Reading memory is not an issue for drive by malware.

      • Javascript. Malware hidden in software. Virtualization. These are all real-world scenarios which affect basically everyone.

        No they aren't. The ability to read a memory location through speculation is irrelevant unless you have hours to exfiltrate memory from a system and even longer to analyse it. In order to make use of these vulnerabilities someone needs to have intimiate knowledge of the system they are currently on.

        Drive by malware utilising spectre is not a real-world scenario.

        If you offer someone server time on the cloud, be worried. If you're a government agencency with hostile state actors embedded and attempting to ele

    • by Anonymous Coward

      1) In order for ANY of these vulnerabilities to be useful, you MUST be running malware on your system. If so, you are already hosed.

      Javascript is sufficient for many of these timing based attacks, even if it slows things down a little more. Proof of principle code already exists and show it can read quite a bit of browser memory in the time a person would reasonably spend on a page. I hope you're running NoScript and none of the sites you grant exceptions to ever get hacked...

    • Re: (Score:2, Informative)

      by Anonymous Coward

      It sounds like you haven't read the details of these attack vectors.

      1. The family of Spectre vulnerabilities are exploitable from javascript.
      2. Yes, there is much malware, that doesn't make Spectre and meltdown attacks any less viable/devastating.
      3. Statistical attacks have been used for a long time. Computers are great at performing them, because, yes, they are computers. Side channels don't need much bandwidth to steal critical information, like say, a users password or bank account details.

      These att

    • I thought the same thing, more or less, based on my understanding of basically how the low-level attack works. As it turns out, I was wrong. They have figured out how to use a "no big deal" issue to build an important and powerful attack around it. I got lost in the details and "couldn't see the forest for the trees", so to speak.

      Others have pointed out "maleware running" could be JavaScript. Not even that is necessary, though - even sending specially crafted TCP packets to the target can do the trick! Goog

      • Well, when google is your technical authority, it's understandable that you'd be dead wrong...."even sending specially crafted TCP packets to the target can do the trick! Google Netspectre for details."

        IF you actually READ TFA, you'll see that it REQUIRES a "gadget" (read: malware code) running on your fucking machine!! (I swear, the tech level on /. has descended to fucking Alex Jones level of paranoia - facts be damned!!) FFS!!
        • The term "gadget", in this context, means vulnerable code, preferably OS code, an especially kernel code. That's pre-existing code, part of the OS, that's vulnerable.

          For Netspectre, an interesting gadget is a network card driver that is vulnerable.

          Gadget does NOT mean malware.

          • "For Netspectre, an interesting gadget is a network card driver that is vulnerable."
            OK, show me one. Or, to be more exact (and I have written device drivers,BTW) show me a vulnerability worth its name that relies on ONE specific flaw in ONE specific NIC device driver, given the wide range of NIC drivers.
            Sheesh! The lengths you guys will go to to defend the indefensible. (Indefensible, in this case, that the whole realm of SM panic is manifested by this weakest of arguments....)
            • Here a couple of examples of Spectre gadgets. Suppose we have this code making sure the input doesn't try to access beyond the end of an array:

              if (x array1_size)
              y = array2[array1[x] * 4096];

              Or maybe this code you might find in a firewall such as iptables. It checks to make sure the protocol of the packet is either TCP, udp, icmp, or another valid protocol:

              if (packet.ethertype = maxtype) {
              CurrentProt = EtherTypes[packet.ethertype];
              }

              Can you spot the problem?

            • Here's the code for the driver uses with Intel network gigabit network cards. Hardly anyone ever uses that, right? Only people with Intel motherboards or Intel network cards, and other companies network cards that use the Intel chip.

              https://github.com/torvalds/li... [github.com]

              I see a couple hundred if statements in there. Maybe 20% of those will serve as a gadget. I bet you can find three or four bounds checks. In my other reply I showed you how to use a bounds check as a Spectre gadget.

  • by TeknoHog ( 164938 ) on Saturday August 11, 2018 @06:08PM (#57109040) Homepage Journal

    return to Spectre
    address stack blown
    go side channel
    no safe zone

  • Well all of this goes back to what I have said to everyone I know, "Do nothing important in a WEB Browser". Which I get "It is safe and easy I do it all the time.

    At least paying for a stamp to mail in a bill payment buys you protection that is lacking in WEB based tools. If your mail is tampered with, it is a crime. Granted the Gov my take a peek, but better than someone trying to drain your accounts.

    The way things are going lynx is looking pretty good :)

    • Granted the Gov my take a peek, but better than someone trying to drain your accounts.

      The CA FTB decided I owed them money (I didn't) and drained my bank account. I filed for the back taxes and naturally I haven't heard from them since. They stole my money and I will never see it again. Assuming the government isn't going to steal from you is ridiculous.

  • Maybe it's too late. There was a chance back with the DOS, but not now. Computers are great but people are shit
  • the only safe computers will be the ones completely disconnected from the internet, kept locked in a secure room where only authorized personnel are allowed to enter, i think its time for a completely new architecture built with security in mind from the ground up and the same goes for the software, no back doors, no remote code allowed to execute unless it is sandboxed and unable to touch the system
  • Manufacturers were notified of the weaknesses in May 2018 and were granted 90 days to remedy them before the results were published.

    90 days may be the standard for Responsible Disclosure, but that's only reasonable for issuing a software patch. Intel doesn't issue new silicon to everyone affected within 90 days, it can take over a year before the next chips are available, and those might've had their design locked down well beyond that.

    • Manufacturers were notified of the weaknesses in May 2018 and were granted 90 days to remedy them before the results were published.

      90 days may be the standard for Responsible Disclosure, but that's only reasonable for issuing a software patch. Intel doesn't issue new silicon to everyone affected within 90 days, it can take over a year before the next chips are available, and those might've had their design locked down well beyond that.

      Then the only reasonable thing is to tell everyone right away

  • Richard Stallman clearly predicted this: https://en.wikipedia.org/wiki/... [wikipedia.org]

"I got everybody to pay up front...then I blew up their planet." "Now why didn't I think of that?" -- Post Bros. Comics

Working...