News for hackers. Stuff that matters.
Re:More Intel speculative execution vulnerabilities by systemdtrigger on Wednesday November 13, 2019 @03:25AM (#21522045)
One question- do these vulnerabilities , including spectre and meltdown only help in stealing information or can they also hijack your computer to do arbitrary things?
Re:More Intel speculative execution vulnerabilities by chii on Wednesday November 13, 2019 @03:29AM (#21522062)
depends on the information you steal.

If you steal passwords, then you can use said password to hijack whatever the passwords are protecting.

If you steal private keys, you may be able to use said keys to impersonate the victim (like via ssh into their remote machines).

But if you're asking if speculative vulns could directly lead to remote code execution, then no (since you already have given the attacker a measure of control, as they are able to execute code already).

Re:More Intel speculative execution vulnerabilities by rocqua on Wednesday November 13, 2019 @03:36AM (#21522091)
It can be used to defeat ASLR, which is a way to make exploiting code harder. However, defeating ASLR just makes it easier to deploy an exploit against a program, but you still need the exploit.

It doesn't immediately give code exec, but generally it wouldn't be very hard to turn arbitrary memory read capabilities into privilege escalation. As long as you know what the system is running.

Re:More Intel speculative execution vulnerabilities by systemdtrigger on Wednesday November 13, 2019 @03:44AM (#21522140)
So the sense I'm making is- that most of thesr attacks need to be supervised and need you to be a target in particular?
Re:More Intel speculative execution vulnerabilities by mrob on Wednesday November 13, 2019 @05:31AM (#21522661)
The attacker needs some way to execute code on your machine. The code doesn't need any special permissions, although attacks are more difficult (but not impossible) if it doesn't have access to high resolution timing information. You can be a target by visiting a webpage with JavaScript enabled.
Re:More Intel speculative execution vulnerabilities by paulddraper on Wednesday November 13, 2019 @03:46AM (#21522160)
To exploit these vulnerabilities, you already need (unprivileged, sandboxed) RCE.

These vulnerabilities "only" steal information; however that information could of course be leveraged into privilege escalation or anything else.

Re:More Intel speculative execution vulnerabilities by gpm on Wednesday November 13, 2019 @02:13PM (#21528195)
This isn't true unfortunately.

Being able to cause manipulate the control flow of code that already exists on the computer can be sufficient. See netspectre for an example that worked on real google cloud vms and local wired networks.

http://www.misc0110.net/web/files/netspectre.pdf

Re:More Intel speculative execution vulnerabilities by paulddraper on Wednesday November 13, 2019 @02:43PM (#21528595)
Wow, that is impressive.

Yes in theory you could do that, but to actually exploit in practice I would have guessed couldn't be done.

Re:More Intel speculative execution vulnerabilities by icedchai on Wednesday November 13, 2019 @03:43PM (#21529305)
Don't get too excited. From the paper: "In the Google cloud, we leak around 3 bits per hour from another virtual machine." This is, of course, under ideal conditions.
Re:More Intel speculative execution vulnerabilities by paulddraper on Wednesday November 13, 2019 @04:12PM (#21529623)
They estimated that with some dedicated hardware they could improve that by 2-10x.

Still not very useful for an attacker.

But still fascinating and impressive they could do it at all.

Re:More Intel speculative execution vulnerabilities by GrayShade on Wednesday November 13, 2019 @06:22AM (#21522942)
> To exploit these vulnerabilities, you already need (unprivileged, sandboxed) RCE.

Such as running JavaScript code served by an ad network.

Re:More Intel speculative execution vulnerabilities by paulddraper on Wednesday November 13, 2019 @12:10PM (#21526506)
Correct.

Point being, running arbitary (unprivileged, sandboxed) code is a prerequisite; an attacker can already max your CPU, mine crypto, etc.