Re:ThinkPwn: System Management Mode arbitrary code execution
by jsjohns2 on Tuesday July 05, 2016 @12:41PM
(#12037693)
> Do you think any of the firmware in your system comes from your OEM and is secure?
No, of course not. But I'm surprised that Lenovo would tacitly admit this.
Re:ThinkPwn: System Management Mode arbitrary code execution
by josteink on Wednesday July 06, 2016 @07:24AM
(#12042368)
To be honest this has been going on ever since the first day random OEMs started shipping X86-based machines. There's really nothing to admit.
Back then we had Amibios, Pheonix bios etc etc, but these days we call it "UEFI" and "firmware" and everyone gets up in arms about it.
Re:ThinkPwn: System Management Mode arbitrary code execution
by imglorp on Tuesday July 05, 2016 @12:46PM
(#12037726)
That's going to get complicated for network interactions and legislative bodies. Two examples come to mind.
First is the FCC vs WIFI channel selection in firmware. They want the choice to interfere be removed from the user in this occasion.
Second is cell carriers are not wild about unknown basebands conversing with their networks. In theory the network should defend against bad phones but they'd rather not test that.
That's literally what every vendor does nowadays. Do you think LG can get the code for the firmware of the SoCs they use in their phones? Do you think the coreboot guys can get the source for the Intel Management Engine firmware? Do you think any of the firmware in your system comes from your OEM and is secure?
This is a failure in the entire industry, and it's getting worse every day.
The proper solution would be simple, too: Allow everything to be flashed with custom software, but allow the user to set a cryptographic key with which updates have to be signed. By default, the system could accept the OEM key, the user could lock it further down.
Provides additional security for corporations and nerds, provides additional flexibility, provides the ability to modify the firmware.