Re:Errata prompt Intel to disable TSX in Haswell, early Broa...
by 0x0 on Tuesday August 12, 2014 @04:20PM
(#8169921)
Well. Microcode updates are lost on reboot, and they can only be applied from privileged code. Which means you'll have to be able to slip rogue code into the BIOS or the kernel, at which point you already have full control. The "negative ring" levels of code (SMI, etc) are quite powerful already.
But a trojanized microcode update file inside an otherwise regular BIOS would be a nice hiding spot, hard to detect and analyze, at least for anyone outside Intel.
Re:Errata prompt Intel to disable TSX in Haswell, early Broa...
by AlyssaRowan on Tuesday August 12, 2014 @04:50PM
(#8170073)
Or you could just use SMM or IPMI.
Re:Errata prompt Intel to disable TSX in Haswell, early Broa...
by sillysaurus3 on Tuesday August 12, 2014 @05:03PM
(#8170165)
Use those how? Would you go into detail?
Re:Errata prompt Intel to disable TSX in Haswell, early Broa...
by amluto on Tuesday August 12, 2014 @07:39PM
(#8170772)
See, for example: http://www.eecs.ucf.edu/%7Eczou/research/SMM-Rootkits-Secure...
If you're an OS, then you need some kind of exploit to update SMM code. But if you're the BIOS, then you have complete control over what happens in SMM mode.
I would guess that the first layer of protection comes from limiting the scope of microcode updates. Perhaps there's a semiconductor engineer out there who knows more?