From 0a9b1bf17f25372f10edce612cb56a22d2aab164 Mon Sep 17 00:00:00 2001 From: Yue Zhao Date: Fri, 22 Jul 2022 00:57:31 -0700 Subject: [PATCH 1/2] Update README.md --- README.md | 10 +++++----- 1 file changed, 5 insertions(+), 5 deletions(-) diff --git a/README.md b/README.md index 67deb7f..7f263bc 100644 --- a/README.md +++ b/README.md @@ -1,6 +1,6 @@ # **Disclaimer** -**All information is provided for educational purposes only. Follow these instructions at your own risk. Neither the authors nor their employer are responsible for any direct or consequential damage or loss arising from any person or organization acting or failing to act on the basis of information contained in this page.** +**All information is provided for educational purposes only. Follow these instructions at your own risk. Neither the authors nor their employers are responsible for any direct or consequential damage or loss arising from any person or organization acting or failing to act based on information contained on this page.** # Description At the beginning of 2020, we discovered the Red Unlock technique that allows extracting [Intel Atom Microcode](https://en.wikipedia.org/wiki/Intel_Microcode). We were able to research the internal structure of the microcode and then x86 instruction implementation. Also, we recovered a format of microcode updates, algorithm and the encryption key used to protect the microcode (see [RC4](https://en.wikipedia.org/wiki/RC4)). @@ -8,15 +8,15 @@ At the beginning of 2020, we discovered the Red Unlock technique that allows ext # FAQ 1. Can I make a custom microcode update? -No, you can't. Only decryption is supported, because microcode has an RSA signature for integrity protection. +No, you can't. Only decryption is supported because microcode has an RSA signature for integrity protection. 2. What kind CPUs are supported? -A microcode update decryption key depends from CPU generation. We've extracted keys for Intel Gemini Lake (Goldmont Plus microarchitecture) and Intel Apolo Lake (Goldmont microarchitecture) generation. See [List of Supported CPUs](#list-of-supported-cpus) +A microcode update decryption key depends on CPU generation. We've extracted keys for the generation of Intel Gemini Lake (Goldmont Plus microarchitecture) and Intel Apolo Lake (Goldmont microarchitecture). See [List of Supported CPUs](#list-of-supported-cpus) 3. How you had extracted the keys? -Using vulnerabilities in Intel TXE we had activated undocumented debugging mode called red unlock and extracted dumps of microcode directly from the CPU. We found the keys and algorithm inside. +Using vulnerabilities in Intel TXE, we had activated an undocumented debugging mode called red unlock and extracted dumps of microcode directly from the CPU. We found the keys and algorithm inside. 4. Where can I find more information about it? @@ -131,4 +131,4 @@ Dmitry Sklyarov ([@_Dmit][3]) [1]: https://twitter.com/_markel___ [2]: https://twitter.com/h0t_max -[3]: https://twitter.com/_Dmit \ No newline at end of file +[3]: https://twitter.com/_Dmit From 51b32e064e626c302bce2c791e98675037d132f3 Mon Sep 17 00:00:00 2001 From: Yue Zhao Date: Fri, 22 Jul 2022 00:59:18 -0700 Subject: [PATCH 2/2] Update README.md