News for hackers. Stuff that matters.
Re:Finding a CPU Design Bug in the Xbox 360 by fps_doug on Monday January 08, 2018 @03:44AM (#16095476)
Scratches PowerPC off the list of trustworthy CPUs

Sooo, out you go, G5. Any suggestions what to use for online banking? A 486 can't handle all the jQuery and tracking scripts.

Re:Finding a CPU Design Bug in the Xbox 360 by LeoPanthera on Monday January 08, 2018 @04:16AM (#16095600)
In the list of possible risks to online banking (and why is it always online banking in these hypothetical world-is-ending scenarios?), CPU bugs are way down the list.
Re:Finding a CPU Design Bug in the Xbox 360 by exikyut on Monday January 08, 2018 @04:20AM (#16095613)
It's the stereotypical "why to use SSL" that everyone thinks of first.
Re:Finding a CPU Design Bug in the Xbox 360 by pjc50 on Monday January 08, 2018 @05:28AM (#16095838)
Note that the bank will carry on using their Intel systems on the front end, with probably some crawling horror buried in the back office. All the intranet webpages will be IE6-only or similar.
Re:Finding a CPU Design Bug in the Xbox 360 by nerflad on Monday January 08, 2018 @08:14AM (#16096455)
This. I am reasonably confident in my security on the client side, but my credit union's janky ASP site does not inspire confidence at all.
Re:Finding a CPU Design Bug in the Xbox 360 by SAI_Peregrinus on Monday January 08, 2018 @12:42PM (#16098368)
Some banks don't even use HTTPS consistently. Their security is almost always primarily through the legal system.
Re:Finding a CPU Design Bug in the Xbox 360 by jsheard on Monday January 08, 2018 @10:01AM (#16097135)
The xdcbt instruction was a custom addition for the 360s CPU so vanilla PowerPC chips shouldn't be affected by this.
Re:Finding a CPU Design Bug in the Xbox 360 by logfromblammo on Monday January 08, 2018 @10:57AM (#16097583)
Not by this, but it shows the chip has speculative execution, and is therefore vulnerable to Spectre.

In this specific instance, the xdcbt instruction accidentally does a bad thing in the Spectre Zone that leaks back into the real world through a side-channel in the L1 cache. Crafted malicious code could do another bad thing in the Spectre Zone that ordinarily isn't allowed in the real world, then leak the results back to the real world through any side-channel that works.

Only on Xbox 360, it could even use xdcbt vs dcbt for that side-channel. If you set code up to always execute xdcbt on core 2, and always dcbt on cores 0 and 1, you might be able to do timing-based attacks between core 0 (closer to L2) and core 1 (further from L2) comparing against core 2 (bypassing L2).

A different version of the same PowerPC chip family would have its own side-channels. All those side-channels are hardware-specific.

Re:Finding a CPU Design Bug in the Xbox 360 by adrianN on Monday January 08, 2018 @07:19AM (#16096236)
Run nested CPU simulators on a beowulf cluster of Raspberry Pis?
Re:Finding a CPU Design Bug in the Xbox 360 by exikyut on Monday January 08, 2018 @04:19AM (#16095611)
486s do not have branch predictors.

https://news.ycombinator.com/item?id=16088830

Re:Finding a CPU Design Bug in the Xbox 360 by KozmoNau7 on Monday January 08, 2018 @04:01AM (#16095542)
AFAIK the 32-bit Atoms (of Netbook fame) are not affected?
Re:Finding a CPU Design Bug in the Xbox 360 by SomeHacker44 on Monday January 08, 2018 @10:34AM (#16097392)
Atom CPUs were in-order execution, at least at first, AFAIK. So, without speculation and an OOE engine, Meltdown and Spectre can't happen.
Re:Finding a CPU Design Bug in the Xbox 360 by phire on Monday January 08, 2018 @11:40AM (#16097884)
Just because the execution is in-order, doesn't mean there is no speculative execution.

The 360 cpu (and the closely related ps3 cpu) is the perfect example of this. Despite the fact that it's 100% in-order, it has a very long instruction pipeline (upto 50 instructions long) and branch prediction. And that's all Spectre needs, a long pipeline + branch prediction.

I'm not even 100% sure the intel atom will be safe from Spectre & Meltdown. It's pipeline is much shorter, only 16 stages long, but it still speculatively executes up-to 32 instructions (2 instructions per cycle).

It just makes things harder, you have to find a Spectre gadget that's short enough. Though piss-easy for Meltdown, because you can just hand-assemble short code.

Re:Finding a CPU Design Bug in the Xbox 360 by skykooler on Monday January 08, 2018 @11:42AM (#16097896)
Older Atom processors (pre-2013), or a Raspberry Pi.