3 ms·
This >I think the exploit would be extremely difficult, and this >The idea nagged at Prescher, so when he got home he fired up his desktop computer and set a
by pixl97 9y ago
This
>I think the exploit would be extremely difficult,
and this
>The idea nagged at Prescher, so when he got home he fired up his desktop computer and set about putting the theory into practice. At 2 a.m., a breakthrough: he’d strung together code that reinforced Fogh’s idea and suggested there was something seriously wrong.
Don't seem to match up. It may be hard, but even a security researcher doesn't bust a hard to exploit hole open in a few hours overnight. I believe that this was an area where no one was looking and now that its out in the open it will be much easier for others to exploit.
- 3chelon 9y agoYes, but again, proving there's an exploit is different to implementing it and actually stealing someone's banking details (which is the media definition of a scary hack). And you say "even a security researcher"... surely they are the guys most likely to be able to perform the exploit, in real life?
- solarkraft 9y agoTo prove the vulnerability is exploitable I'd ideally do ahead and do it. Has this not been done?
- workthrowaway27 9y agoIt's one thing to exploit something locally. It's another to exploit it remotely. And if you have local access to a machine I'm sure there are much easier ways to get root access to it.
- matt4077 9y agoBefore being patched, this exploit would have worked at any of the cloud providers: Google Compute Engine, AWS, etc. You could have run it on thousands of virtual machines and sifted through all the data of other VMs running on the same hardware. Oh, and it works (/worked) on browsers.
- not_kurt_godel 9y agoAs a general rule, I'd think the harder part is figuring out that the vulnernability is possible in the first place and formulating an approximate algorithm to exploit it. Implementation is a lot easier when you have a blueprint for what to do.