3 ms·
Potentially. The problem with X360 is it can’t run arbitrary native code, it only can run code digitally signed by MS. The hypervisor refuses to run an unsigne
by Const-me 9y ago
Potentially.
The problem with X360 is it can’t run arbitrary native code, it only can run code digitally signed by MS. The hypervisor refuses to run an unsigned code, and the key never leaves the CPU i.e. very hard to tamper with.
X360 can execute JavaScript in the web browser, and .NET in (now discontinued?) XNA. I’m not sure if it’s possible to exploit the bug if you can only run JavaScript or .NET, both are very high level and have strong security model on top of what’s in the hardware/OS/hypervisor.
- jsheard 9y agoSurely they use asymmetric crypto, so the private key needed to sign code isn't present on the console at all? Spectre might make it possible to dump the public keys but they're not very useful to us.
- fragmede 9y agoThe paper for Spectre includes a Javascript proof of concept - https://spectreattack.com/spectre.pdf https://spectreattack.com/spectre.pdf, though I don't know if the version of IE on the 360 supports web workers (though, unpatched, it's exceedingly like there's a way to exploit it from javascript that doesn't involve web workers).
- kevingadd 9y agoYou could have exploited this using XNA, potentially, yes. But I don't think the software for running your own builds on the hardware works anymore, so the threat has passed. These attacks certainly reduce the likelihood of a similar service appearing on current-gen consoles.