Hertzbleed Attack
Brilliant approach, really. Never occurred to me to try something like this!<p>Are you affected? Very likely. What can you do about it? Nerf your CPU performance by disabling &quot;turbo boost&quot; or equivalent. Should you do it? Probably not unless you&#x27;re particularly vulnerable (journalist, human rights activist, etc.)<p>One thing I found interesting that may get changed later, so I&#x27;m documenting it here, is in their FAQ they say:<p>&gt; Why did Intel ask for a long embargo, considering they are not deploying patches?
&gt;
&gt; Ask Intel.<p>So Intel <i>did</i> ask for a long embargo, then apparently did nothing about it. My guess is they investigated &quot;can we actually mitigate this thing with a microcode update?&quot; and arrived at the conclusion after actually trying - or possibly after external influences were exerted (you be the judge) - that no, there&#x27;s not much you can really do about this one.<p>Later in the document another FAQ says:<p>&gt; [...] Both Cloudflare and Microsoft deployed the mitigation suggested by De Feo et al. (who, while our paper was under the long Intel embargo, independently re-discovered how to exploit anomalous 0s in SIKE for power side channels).  [...]<p>Which is again telling us that there indeed WAS a long embargo placed on this research by Intel.<p>Only mentioning this here just in case the PR spin doctors threaten the researchers into removing mention of Intel on this one. Which honestly I hope doesn&#x27;t happen because my interpretation is that Intel asked for that long embargo so they could investigate really fixing the problem (state agencies have more methods at their disposal and wouldn&#x27;t need much time to exert influence over Intel if they decided to). Which speaks well of them IMO. But then again, not everybody&#x27;s going to come to that same conclusion which is why I&#x27;m slightly concerned those facts may get memory-holed.