Want to make your own persistent rootkit?
Just sign your native windows binary with one of Hacking Team's revoked code signing certificates and you are all set!
https://t.co/exqAYnxR4S
Certificate: https://t.co/h3rVU7hRt7
@CHIPSEC now exposes the common.smm_code_chk module that verifies MSR_SMM_FEATURE_CONTROL is configured properly to mitigate SMM callout vulnerabilities.
Now, cross your fingers and pass this address as an additional argument to the CHIPSEC command. If all goes well, CHIPSEC should now be able to scan the boot script for any potential call-out vulnerabilities.
Disclaimer: I only tried this on my own computer. Use at your own risk!
Great point. Can also think of improving s3bootscript module to dump NVRAM directly (rather than read from runtime) and look up the AcpiGlobalVariable in NVRAM
If you ever encountered a machine where @CHIPSEC fails to obtain and parse the S3 boot script, chances are the 'AcpiGlobalVariable' (which should contain the pointer to the boot script) simply doesn't have the 'Runtime' attribute, and therefore it can't be enumerated from the OS.
TrickBot Now Offers ‘TrickBoot' @VK_Intel @IntelAdvanced and @Eclypsium have discovered a new module in the TrickBot toolset aimed at detecting UEFI / BIOS firmware vulnerabilities, enabling #malware to persist, brick, and profit. #TrickBoot
https://t.co/rIBlotTwzN
The first part of @liba2k and mine research on UEFI just went online. This time it's merely a refresher on how to dump SPI flash memory, but the next posts in the series will be more innovative and discuss techniques to reverse, debug and fuzz UEFI drivers
https://t.co/NlUu4R2lhm
Eclypsium researchers discovered #BootHoleVulnerability in the GRUB2 bootloader that can be used to gain arbitrary code execution on majority of Linux and Windows based systems, even when they are not using GRUB and Secure Boot is enabled. https://t.co/9jc26InmfA