3 ms·
As I understand it, you would need to have an existing RCE to exploit the microcode patching process. h0t_max’s research means that future attacks — once your
by gorgoiler 4y ago
As I understand it, you would need to have an existing RCE to exploit the microcode patching process.
h0t_max’s research means that future attacks — once your local machine has been infiltrated by some other means — can do a lot more damage than simply encrypting your filesystem or sending spam. They can rewrite the way your CPU works.
When your OS gets attacked by malware it is attacking the layer above the bare metal on which your OS runs. The base hardware remains untouched. You can at least clean things up by installing a new OS on the bare metal.
If malware attacks the bare metal itself, then you are stuck out of luck.
- ndiddy 4y agoAs mentioned in the github page that this post links to, it's impossible to make a custom microcode update because the updates are RSA signed.
- anewpersonality 4y agoDidn’t they dump the private keys?
- sroussey 4y agoPublic key
- deleted 4y ago[deleted]
- anewpersonality 4y agoWhat can do they with the public key vs private key?
- pitaj 4y agoPublic keys can only be used to verify a signature, not to sign anything.
- anewpersonality 4y agoWas the public key found used to decrypt the microcode?
- NavinF 4y agoWhy would private keys be on the chip?
- reocha 4y agoExcept if someone finds a flaw in the microcode loader.