https://www.us-cert.gov/ncas/current-activity/2017/05/07/Intel-Firmware-Vulnerability
https://github.com/CerberusSecurity/CVE-2017-5689
https://github.com/chipsec/chipsec/issues/212
https://support.lenovo.com/us/en/product_security/len-14963
http://en.community.dell.com/support-forums/laptop/f/3518/p/20011922/20995860
http://en.community.dell.com/techcenter/extras/m/white_papers/20443914
http://en.community.dell.com/techcenter/extras/m/white_papers/20443937
https://support.hp.com/us-en/document/c05507350
https://community.qualys.com/thread/17263-qids-or-scanning-advice-for-intel-amt-sa-00075
https://www.tenable.com/sc-dashboards/intel-sa-00075-detection
https://www.tenable.com/blog/intel-amt-vulnerability-detection-with-nessus-and-pvs-intel-sa-00075
Intel AMT chip bug suspected backdoor, but likely coding error
[…]Some researchers accused the vulnerability of being a backdoor. Tatu Ylonen, the inventor of the Secure Shell protocol told SC Media Charlie Demerjan, the researcher who spotted the flaw, claims to have been in discussions over bug with Intel for years urging them t to fix it. “If his claim is true (I have no reason to doubt it but have no independent evidence), then it begins to sound very much like a backdoor,” Demerjan said. “I mean, if someone knows their product has a vulnerability that undermines the security of pretty much every enterprise server in the world and most security tools, wouldn’t they want to disclose it to the government, one of their biggest customers?”[…]
https://www.scmagazine.com/intel-amt-flaw-likely-just-coding-error/article/655449/
[…]What is clear, however, is that this flaw (which has existed for more than 9 years) truly is somewhere between nightmarish and apocalyptic. Taking no action is not an option.
Firmware Security 