Timeline for How to protect/mitigate IntelME (CSME) JTAG attack over USB?
Current License: CC BY-SA 3.0
4 events
when toggle format | what | by | license | comment | |
---|---|---|---|---|---|
Nov 29, 2017 at 21:12 | comment | added | forest | Actually the main CPU is not supposed to grant JTAG access to the ME. The problem seems to be that the P2SB bridge is normally hidden but can be made unhidden (by root?), and this allows DCI to access the ME somehow. | |
Nov 12, 2017 at 21:06 | comment | added | myron-semack | @FranklinPiat Yes but exploiting the ME once you have JTAG Access isn’t much of a shock. Once you’re on the other side of the airtight hatchway you already own the system completely. You own more of the system than the OS does. Accessing the ME is just the bacon bits on the exploit salad at that point. | |
Nov 12, 2017 at 21:01 | comment | added | Franklin Piat | Nice answer, however M.Goryachy and M.Ermolov's attacks seems to specifically target Intel CSME. The main CPU/firmware flaw was disclosed and fixed in April 2017 (see ptsecurity's blog ) | |
Nov 12, 2017 at 13:27 | history | answered | myron-semack | CC BY-SA 3.0 |