<story><title>Rediscovering the Intel AMT Vulnerability</title><url>https://www.tenable.com/blog/rediscovering-the-intel-amt-vulnerability</url></story><parent_chain></parent_chain><comment><author>kbenson</author><text>&lt;i&gt;Next, we reduced the response hash to one hex digit and authentication still worked. Continuing to dig, we used a NULL&amp;#x2F;empty response hash (response=&amp;quot;&amp;quot; in the HTTP Authorization header).&lt;p&gt;Authentication still worked. We had discovered a complete bypass of the authentication scheme.&lt;/i&gt;&lt;p&gt;What. the. fuck.&lt;p&gt;This is not the kind of bug you should ship in &lt;i&gt;anything&lt;/i&gt; if you have the barest bit of testing in place, much less a large company like Intel, in an enterprise feature which has a lot of security ramifications, and which has apparently existed for a long time (years?).&lt;p&gt;Edit: Also, this is really good evidence for short and hard disclosure deadlines.  What&amp;#x27;s the chance something as simple as this wasn&amp;#x27;t known by someone else?  All they had to do was decide to look and they found something within minutes.  It&amp;#x27;s not like this is obscure or doesn&amp;#x27;t get your much, it&amp;#x27;s about as juicy as they come.</text></comment>
<story><title>Rediscovering the Intel AMT Vulnerability</title><url>https://www.tenable.com/blog/rediscovering-the-intel-amt-vulnerability</url></story><parent_chain></parent_chain><comment><author>bobsam</author><text>Intel decided they have the right to put a whole secret computer inside your computer that only they can access. God knows what it does when no one is watching.&lt;p&gt;That&amp;#x27;s the problem you should discuss, not this particular exploit.</text></comment>