{"id":103242,"date":"2022-02-08T09:36:38","date_gmt":"2022-02-08T07:36:38","guid":{"rendered":"https:\/\/prohoster.info\/blog\/novosti-interneta\/uyazvimosti-v-uefi-proshivkah-na-baze-frejmvorka-insydeh2o-pozvolyayushhie-vypolnit-kod-na-urovne-smm"},"modified":"2022-02-08T09:36:38","modified_gmt":"2022-02-08T07:36:38","slug":"uyazvimosti-v-uefi-proshivkah-na-baze-frejmvorka-insydeh2o-pozvolyayushhie-vypolnit-kod-na-urovne-smm","status":"publish","type":"post","link":"https:\/\/prohoster.info\/en\/blog\/news\/uyazvimosti-v-uefi-proshivkah-na-baze-frejmvorka-insydeh2o-pozvolyayushhie-vypolnit-kod-na-urovne-smm","title":{"rendered":"Vulnerabilities in UEFI firmware based on the InsydeH2O framework allow code execution at the SMM level.","gt_translate_keys":[{"key":"rendered","format":"text"}]},"content":{"rendered":"
In the InsydeH2O framework, used by many manufacturers to create UEFI firmware for their hardware (the most common implementation of UEFI BIOS), 23 vulnerabilities have been identified that enable code execution at the SMM (System Management Mode) level, which is more privileged (Ring -2) than the hypervisor mode and the zero privilege ring, granting unrestricted access to all memory. This issue affects UEFI firmware used by manufacturers such as Fujitsu, Siemens, Dell, HP, HPE, Lenovo, Microsoft, Intel, and Bull Atos. <\/p>\n
Exploitation of the vulnerabilities requires local access with administrator rights, making these issues sought after as second-tier vulnerabilities, used after the exploitation of other vulnerabilities within the system or through social engineering methods. SMM-level access can be used to execute code at a level not controlled by the operating system, which could be utilized to modify firmware and leave hidden malware or rootkits in SPI Flash that are undetectable from the operating system, as well as to disable verification during the boot phase (UEFI Secure Boot, Intel BootGuard) and attack hypervisors to bypass integrity-check mechanisms of virtual environments.
<\/center> <\/p>\n
Exploitation of the vulnerabilities can be carried out from the operating system using unverified SMI handlers (System Management Interrupt), as well as during the boot process prior to the operating system execution or when resuming from sleep. All vulnerabilities are caused by memory handling issues and are divided into three categories: <\/p>\n
\n
SMM Callout \u2014 executing your code with SMM privileges by redirecting SWSMI interrupt handler execution to code outside of SMRAM;\n
Memory corruption allowing an attacker to write their data into SMRAM, a special isolated memory area where code with SMM privileges executes.\n
Memory corruption in code executed at the DXE (Driver eXecution Environment) level. <\/ul>\n
To demonstrate the principles of attack organization, an example exploit has been published that allows access to the DXE Runtime UEFI through an attack from the third or zero defense ring, enabling the execution of custom code. The exploit manipulates a stack overflow (CVE-2021-42059) in the UEFI DXE driver. During the attack, an attacker can place their code in the DXE driver, which remains active after the operating system is rebooted, or modify the NVRAM area in the SPI Flash. During execution, the attacker's code can alter privileged memory areas, modify EFI Runtime services, and influence the boot process. \n Source: opennet.ru<\/a> <\/p>","protected":false,"gt_translate_keys":[{"key":"rendered","format":"html"}]},"excerpt":{"rendered":"
![\"Vulnerabilities](\"\/wp-content\/uploads\/2022\/02\/dcf918bee3be0d2788f82d325cd671c7.jpg\")
<\/center> <\/p>\n