Kevin Karhan :verified:<p><span class="h-card" translate="no"><a href="https://social.treehouse.systems/@marcan" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@<span>marcan</span></a></span> <em>nodds in agreement</em> <a href="https://infosec.space/tags/Apple" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>Apple</span></a> doesn't need to have backdoors in Hardware when their entire <a href="https://infosec.space/tags/iCould" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>iCould</span></a> <a href="https://www.youtube.com/watch?v=Ev9_oDHNf-4" rel="nofollow noopener noreferrer" target="_blank">is</a> <a href="https://www.youtube.com/watch?v=r38Epj6ldKU" rel="nofollow noopener noreferrer" target="_blank">backdoored</a> and can be <a href="https://www.youtube.com/watch?v=ifOifNBgyRg" rel="nofollow noopener noreferrer" target="_blank">weaponized</a> to <a href="https://www.youtube.com/watch?v=ZzS2vwDUO9U" rel="nofollow noopener noreferrer" target="_blank">brick devices</a>.</p><ul><li>OFC similar functionality can be achieved with <a href="https://infosec.space/tags/CompuTrace" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>CompuTrace</span></a> on <a href="https://infosec.space/tags/amd64" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>amd64</span></a>-based <a href="https://infosec.space/tags/Laptops" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>Laptops</span></a> (i.e. <a href="https://infosec.space/tags/ThinkPads" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>ThinkPads</span></a>) and compared to that, <a href="https://infosec.space/tags/AMT" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>AMT</span></a> + <a href="https://infosec.space/tags/ManagmentEngine" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>ManagmentEngine</span></a> is trivial to <a href="https://infosec.space/tags/exploit" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>exploit</span></a> and should be considered real <a href="https://infosec.space/tags/backdoors" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>backdoors</span></a> (abeit <em>"well meaning"</em> in the sense of remote provisioning of entire fleets of devices)...</li></ul><p>Either way, these are not inherent to the used <a href="https://infosec.space/tags/Silicon" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>Silicon</span></a>, but entirely <a href="https://infosec.space/tags/Firmware" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>Firmware</span></a>-based.</p><ul><li>AMT for example requires a <em>"<a href="https://infosec.space/tags/Intel" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>Intel</span></a> <a href="https://infosec.space/tags/vPro" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>vPro</span></a>"</em> configuration with Intel-made Ethernet NICs (i.e. i2xx & i3xx - Series) with a Q- or C-series Chipset & supporting <a href="https://infosec.space/tags/UEFI" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>UEFI</span></a>, so most Systems with cheap <a href="https://infosec.space/tags/Realtek" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>Realtek</span></a>-NICs aren't exploitable straight-away, and even then it requires certain settings to work, so not an easy <em>"<a href="https://infosec.space/tags/Pwn2Own" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>Pwn2Own</span></a>"</em> style exploitability...</li></ul>