An issue was discovered in HddPassword in Insyde InsydeH2O with kernel 5.1 before 05.16.23, 5.2 before 05.26.23, 5.3 before 05.35.23, 5.4 before 05.43.22, and 5.5 before 05.51.22. An SMM memory corruption vulnerability allows an attacker to write fixed or predictable data to SMRAM. Exploiting this issue could lead to escalating privileges to SMM.
{"prion": [{"lastseen": "2023-08-16T07:54:09", "description": "An issue was discovered in HddPassword in Insyde InsydeH2O with kernel 5.1 before 05.16.23, 5.2 before 05.26.23, 5.3 before 05.35.23, 5.4 before 05.43.22, and 5.5 before 05.51.22. An SMM memory corruption vulnerability allows an attacker to write fixed or predictable data to SMRAM. Exploiting this issue could lead to escalating privileges to SMM.", "cvss3": {"exploitabilityScore": 1.5, "cvssV3": {"baseSeverity": "HIGH", "confidentialityImpact": "HIGH", "attackComplexity": "LOW", "scope": "CHANGED", "attackVector": "LOCAL", "availabilityImpact": "HIGH", "integrityImpact": "HIGH", "privilegesRequired": "HIGH", "baseScore": 8.2, "vectorString": "CVSS:3.1/AV:L/AC:L/PR:H/UI:N/S:C/C:H/I:H/A:H", "version": "3.1", "userInteraction": "NONE"}, "impactScore": 6.0}, "published": "2022-02-03T02:15:00", "type": "prion", "title": "CVE-2021-43615", "bulletinFamily": "NVD", "cvss2": {"severity": "HIGH", "exploitabilityScore": 3.9, "obtainAllPrivilege": false, "userInteractionRequired": false, "obtainOtherPrivilege": false, "cvssV2": {"accessComplexity": "LOW", "confidentialityImpact": "COMPLETE", "availabilityImpact": "COMPLETE", "integrityImpact": "COMPLETE", "baseScore": 7.2, "vectorString": "AV:L/AC:L/Au:N/C:C/I:C/A:C", "version": "2.0", "accessVector": "LOCAL", "authentication": "NONE"}, "impactScore": 10.0, "acInsufInfo": false, "obtainUserPrivilege": false}, "cvelist": ["CVE-2021-43615"], "modified": "2022-03-29T16:05:00", "id": "PRION:CVE-2021-43615", "href": "https://kb.prio-n.com/vulnerability/CVE-2021-43615", "cvss": {"score": 7.2, "vector": "AV:L/AC:L/Au:N/C:C/I:C/A:C"}}], "cnvd": [{"lastseen": "2022-08-27T05:11:24", "description": "Insyde InsydeH2O is a C source from Insyde Software (Taiwan, China) that implements the new technology \"EFI/UEFI\" specification, designed to replace the traditional BIOS (Basic Input/Output System). Operating System (H2O) UEFI firmware is vulnerable to permission and access control issues, which can be exploited to hijack the execution flow of code running in system management mode.", "cvss3": {"exploitabilityScore": 1.5, "cvssV3": {"baseSeverity": "HIGH", "confidentialityImpact": "HIGH", "attackComplexity": "LOW", "scope": "CHANGED", "attackVector": "LOCAL", "availabilityImpact": "HIGH", "integrityImpact": "HIGH", "privilegesRequired": "HIGH", "baseScore": 8.2, "vectorString": "CVSS:3.1/AV:L/AC:L/PR:H/UI:N/S:C/C:H/I:H/A:H", "version": "3.1", "userInteraction": "NONE"}, "impactScore": 6.0}, "published": "2022-02-09T00:00:00", "type": "cnvd", "title": "Insyde InsydeH2O permission permission and access control issues vulnerability (CNVD-2022-10274)", "bulletinFamily": "cnvd", "cvss2": {"severity": "HIGH", "exploitabilityScore": 3.9, "obtainAllPrivilege": false, "userInteractionRequired": false, "obtainOtherPrivilege": false, "cvssV2": {"accessComplexity": "LOW", "confidentialityImpact": "COMPLETE", "availabilityImpact": "COMPLETE", "integrityImpact": "COMPLETE", "baseScore": 7.2, "vectorString": "AV:L/AC:L/Au:N/C:C/I:C/A:C", "version": "2.0", "accessVector": "LOCAL", "authentication": "NONE"}, "impactScore": 10.0, "acInsufInfo": false, "obtainUserPrivilege": false}, "cvelist": ["CVE-2021-43615"], "modified": "2022-02-15T00:00:00", "id": "CNVD-2022-10274", "href": "https://www.cnvd.org.cn/flaw/show/CNVD-2022-10274", "cvss": {"score": 7.2, "vector": "AV:L/AC:L/Au:N/C:C/I:C/A:C"}}], "f5": [{"lastseen": "2023-06-14T16:55:39", "description": " * [CVE-2020-5953](<https://vulners.com/cve/CVE-2020-5953>)\n\nA vulnerability exists in System Management Interrupt (SWSMI) handler of InsydeH2O UEFI Firmware code located in SWSMI handler that dereferences gRT (EFI_RUNTIME_SERVICES) pointer to call a GetVariable service, which is located outside of SMRAM. This can result in code execution in SMM (escalating privilege from ring 0 to ring -2).\n\n * [CVE-2021-33625](<https://vulners.com/cve/CVE-2021-33625>)\n\nAn issue was discovered in Kernel 5.x in Insyde InsydeH2O, affecting HddPassword. Software SMI services that use the Communicate() function of the EFI_SMM_COMMUNICATION_PROTOCOL do not check whether the address of the buffer is valid, which allows use of SMRAM, MMIO, or OS kernel addresses.\n\n * [CVE-2021-33626](<https://vulners.com/cve/CVE-2021-33626>)\n\nA vulnerability exists in SMM (System Management Mode) branch that registers a SWSMI handler that does not sufficiently check or validate the allocated buffer pointer(QWORD values for CommBuffer). This can be used by an attacker to corrupt data in SMRAM memory and even lead to arbitrary code execution.\n\n * [CVE-2021-33627](<https://vulners.com/cve/CVE-2021-33627>)\n\nAn issue was discovered in Insyde InsydeH2O 5.x, affecting FwBlockServiceSmm. Software SMI services that use the Communicate() function of the EFI_SMM_COMMUNICATION_PROTOCOL do not check whether the address of the buffer is valid, which allows use of SMRAM, MMIO, or OS kernel addresses\n\n * [CVE-2021-41837](<https://vulners.com/cve/CVE-2021-41837>)\n\nAn issue was discovered in AhciBusDxe in the kernel 5.0 through 5.5 in Insyde InsydeH2O. Because of an Untrusted Pointer Dereference that causes SMM memory corruption, an attacker may be able to write fixed or predictable data to SMRAM. Exploiting this issue could lead to escalating privileges to SMM.\n\n * [CVE-2021-41838](<https://vulners.com/cve/CVE-2021-41838>)\n\nAn issue was discovered in SdHostDriver in the kernel 5.0 through 5.5 in Insyde InsydeH2O. There is an SMM callout that allows an attacker to access the System Management Mode and execute arbitrary code. This occurs because of a Numeric Range Comparison Without a Minimum Check.\n\n * [CVE-2021-41839](<https://vulners.com/cve/CVE-2021-41839>)\n\nAn issue was discovered in NvmExpressDxe in the kernel 5.0 through 5.5 in Insyde InsydeH2O. Because of an Untrusted Pointer Dereference that causes SMM memory corruption, an attacker may be able to write fixed or predictable data to SMRAM. Exploiting this issue could lead to escalating privileges to SMM.\n\n * [CVE-2021-41840](<https://vulners.com/cve/CVE-2021-41840>)\n\nAn issue was discovered in NvmExpressDxe in the kernel 5.0 through 5.5 in Insyde InsydeH2O. There is an SMM callout that allows an attacker to access the System Management Mode and execute arbitrary code. This occurs because of Inclusion of Functionality from an Untrusted Control Sphere.\n\n * [CVE-2021-41841](<https://vulners.com/cve/CVE-2021-41841>)\n\nAn issue was discovered in AhciBusDxe in the kernel 5.0 through 5.5 in Insyde InsydeH2O. There is an SMM callout that allows an attacker to access the System Management Mode and execute arbitrary code. This occurs because of Inclusion of Functionality from an Untrusted Control Sphere.\n\n * [CVE-2021-42059](<https://vulners.com/cve/CVE-2021-42059>)\n\nAn issue was discovered in Insyde InsydeH2O Kernel 5.0 before 05.08.41, Kernel 5.1 before 05.16.41, Kernel 5.2 before 05.26.41, Kernel 5.3 before 05.35.41, and Kernel 5.4 before 05.42.20. A stack-based buffer overflow leads to arbitrary code execution in UEFI DisplayTypeDxe DXE driver.\n\n * [CVE-2021-42060](<https://vulners.com/cve/CVE-2021-42060>)\n\nAn issue was discovered in Insyde InsydeH2O Kernel 5.0 through 05.08.41, Kernel 5.1 through 05.16.41, Kernel 5.2 before 05.23.22, and Kernel 5.3 before 05.32.22. An Int15ServiceSmm SMM callout vulnerability allows an attacker to hijack execution flow of code running in System Management Mode. Exploiting this issue could lead to escalating privileges to SMM.\n\n * [CVE-2021-42113](<https://vulners.com/cve/CVE-2021-42113>)\n\nAn issue was discovered in StorageSecurityCommandDxe in Insyde InsydeH2O with Kernel 5.1 before 05.14.28, Kernel 5.2 before 05.24.28, and Kernel 5.3 before 05.32.25. An SMM callout vulnerability allows an attacker to hijack execution flow of code running in System Management Mode. Exploiting this issue could lead to escalating privileges to SMM.\n\n * [CVE-2021-42554](<https://vulners.com/cve/CVE-2021-42554>)\n\nAn issue was discovered in Insyde InsydeH2O with Kernel 5.0 before 05.08.42, Kernel 5.1 before 05.16.42, Kernel 5.2 before 05.26.42, Kernel 5.3 before 05.35.42, Kernel 5.4 before 05.42.51, and Kernel 5.5 before 05.50.51. An SMM memory corruption vulnerability in FvbServicesRuntimeDxe allows a possible attacker to write fixed or predictable data to SMRAM. Exploiting this issue could lead to escalating privileges to SMM.\n\n * [CVE-2021-43323](<https://vulners.com/cve/CVE-2021-43323>)\n\nSMM callout vulnerability allowing a possible attacker to hijack execution flow of a code running in System Management Mode. Exploiting this issue could lead to escalating privileges to SMM.\n\n * [CVE-2021-43522](<https://vulners.com/cve/CVE-2021-43522>)\n\nSMM memory corruption vulnerability allowing a possible attacker to write fixed or predictable data to SMRAM. Exploiting this issue could lead to escalating privileges to SMM.\n\n * [CVE-2021-43615](<https://vulners.com/cve/CVE-2021-43615>)\n\nSMM callout vulnerability allowing a possible attacker to hijack execution flow of a code running in System Management Mode. Exploiting this issue could lead to escalating privileges to SMM.\n\n * [CVE-2022-24030](<https://vulners.com/cve/CVE-2022-24030>)\n\nSMM memory corruption vulnerability allowing a possible attacker to write fixed or predictable data to SMRAM. Exploiting this issue could lead to escalating privileges to SMM.\n\n * [CVE-2022-24031](<https://vulners.com/cve/CVE-2022-24031>)\n\nSMM memory corruption vulnerability allowing a possible attacker to write fixed or predictable data to SMRAM. Exploiting this issue could lead to escalating privileges to SMM.\n\n * [CVE-2022-24069](<https://vulners.com/cve/CVE-2022-24069>)\n\nSMM callout vulnerability allowing a possible attacker to hijack execution flow of a code running in System Management Mode. Exploiting this issue could lead to escalating privileges to SMM.\n\n * [CVE-2020-27339](<https://vulners.com/cve/CVE-2020-27339>)\n\nIn the kernel in Insyde InsydeH2O 5.x, certain SMM drivers did not correctly validate the CommBuffer and CommBufferSize parameters, allowing callers to corrupt either the firmware or the OS memory. The fixed versions for this issue in the AhciBusDxe, IdeBusDxe, NvmExpressDxe, SdHostDriverDxe, and SdMmcDeviceDxe drivers are 05.16.25, 05.26.25, 05.35.25, 05.43.25, and 05.51.25 (for Kernel 5.1 through 5.5).\n\n * [CVE-2021-45969](<https://vulners.com/cve/CVE-2021-45969>)\n\nAn issue was discovered in AhciBusDxe in Insyde InsydeH2O with kernel 5.1 before 05.16.25, 5.2 before 05.26.25, 5.3 before 05.35.25, 5.4 before 05.43.25, and 5.5 before 05.51.25. A vulnerability exists in the SMM (System Management Mode) branch that registers a SWSMI handler that does not sufficiently check or validate the allocated buffer pointer (the CommBuffer+8 location).\n\n * [CVE-2021-45970](<https://vulners.com/cve/CVE-2021-45970>)\n\nAn issue was discovered in IdeBusDxe in Insyde InsydeH2O with kernel 5.1 before 05.16.25, 5.2 before 05.26.25, 5.3 before 05.35.25, 5.4 before 05.43.25, and 5.5 before 05.51.25. A vulnerability exists in the SMM (System Management Mode) branch that registers a SWSMI handler that does not sufficiently check or validate the allocated buffer pointer (the status code saved at the CommBuffer+4 location).\n\n * [CVE-2021-45971](<https://vulners.com/cve/CVE-2021-45971>)\n\nAn issue was discovered in SdHostDriver in Insyde InsydeH2O with kernel 5.1 before 05.16.25, 5.2 before 05.26.25, 5.3 before 05.35.25, 5.4 before 05.43.25, and 5.5 before 05.51.25. A vulnerability exists in the SMM (System Management Mode) branch that registers a SWSMI handler that does not sufficiently check or validate the allocated buffer pointer (CommBufferData).\n\nImpact\n\nThere is no impact; F5 products are not affected by these vulnerabilities.\n", "cvss3": {"exploitabilityScore": 1.5, "cvssV3": {"baseSeverity": "HIGH", "confidentialityImpact": "HIGH", "attackComplexity": "LOW", "scope": "CHANGED", "attackVector": "LOCAL", "availabilityImpact": "HIGH", "integrityImpact": "HIGH", "privilegesRequired": "HIGH", "baseScore": 8.2, "vectorString": "CVSS:3.1/AV:L/AC:L/PR:H/UI:N/S:C/C:H/I:H/A:H", "version": "3.1", "userInteraction": "NONE"}, "impactScore": 6.0}, "published": "2022-02-15T23:23:00", "type": "f5", "title": "Multiple Insyde BIOS/EFI vulnerabilities", "bulletinFamily": "software", "cvss2": {"severity": "HIGH", "exploitabilityScore": 3.9, "obtainAllPrivilege": false, "userInteractionRequired": false, "obtainOtherPrivilege": false, "cvssV2": {"accessComplexity": "LOW", "confidentialityImpact": "COMPLETE", "availabilityImpact": "COMPLETE", "integrityImpact": "COMPLETE", "baseScore": 7.2, "vectorString": "AV:L/AC:L/Au:N/C:C/I:C/A:C", "version": "2.0", "accessVector": "LOCAL", "authentication": "NONE"}, "impactScore": 10.0, "acInsufInfo": false, "obtainUserPrivilege": false}, "cvelist": ["CVE-2020-27339", "CVE-2020-5953", "CVE-2021-33625", "CVE-2021-33626", "CVE-2021-33627", "CVE-2021-41837", "CVE-2021-41838", "CVE-2021-41839", "CVE-2021-41840", "CVE-2021-41841", "CVE-2021-42059", "CVE-2021-42060", "CVE-2021-42113", "CVE-2021-42554", "CVE-2021-43323", "CVE-2021-43522", "CVE-2021-43615", "CVE-2021-45969", "CVE-2021-45970", "CVE-2021-45971", "CVE-2022-24030", "CVE-2022-24031", "CVE-2022-24069"], "modified": "2022-03-01T06:08:00", "id": "F5:K45810018", "href": "https://support.f5.com/csp/article/K45810018", "cvss": {"score": 7.2, "vector": "AV:L/AC:L/Au:N/C:C/I:C/A:C"}}], "cert": [{"lastseen": "2023-07-17T17:14:49", "description": "### Overview\n\nThe InsydeH2O Hardware-2-Operating System (H2O) UEFI firmware contains multiple vulnerabilities related to memory management in System Management Mode (SMM). \n\n### Description\n\nUEFI software provides an extensible interface between an operating system and platform firmware. UEFI software uses a highly privileged processor execution mode called System Management Mode (SMM) for handling system-wide functions like power management, system hardware control, or proprietary OEM-designed code. SMM's privileges, also referred to as \"Ring -2,\" exceed the privileges of the operating system's kernel (\"Ring-0\"). For this reason, SMM is executed in a protected area of memory called the SMRAM. It is typically accessed via System Management Interrupt (SMI) Handlers using communication buffers, which are also known as \"SMM Comm Buffers.\" The SMM also provides protection against SPI flash modifications and performs boot time verifications similar to those performed by [SecureBoot](<https://wiki.ubuntu.com/UEFI/SecureBoot#What_is_UEFI_Secure_Boot.3F>).\n\nUEFI software requires both openness (for hardware drivers, pluggable devices and Driver eXecution Environment (DXE) updates) as well as very tight security controls (for e.g., [SMM Comm Buffer Security](<https://github.com/tianocore-docs/Docs/raw/master/White_Papers/A_Tour_Beyond_BIOS_Secure_SMM_Communication.pdf>)), making it a complex software that needs a thorough set of security controls that need validation throughout the software's lifecycle. UEFI also supports recent capabilities like Virtual Machine Manager (VMM) for virtualization and the increasing demand of virtual computing resources. \n\nInsyde's H2O UEFI firmware contains several (23) memory management vulnerabilities that were disclosed by [Binarly](<https://www.binarly.io>). While these vulnerabilities were discovered in [Fujitsu](<https://www.fujitsu.com/global/>) and [Bull Atos](<https://atos.net/en/>) implementations of Insyde H2O software, the same software is also present in many other vendor implementations due to the complex UEFI supply chain. The vulnerabilities can be classified by the following [UEFI vulnerability categories](<https://medium.com/firmware-threat-hunting/uefi-vulnerabilities-classification-4897596e60af>).\n\nVulnerability Category | Count \n---|--- \nSMM Privilege Escalation| 10 \nSMM Memory Corruption | 12 \nDXE Memory Corruption | 1 \n \n### Impact\n\nThe impacts of these vulnerabilities vary widely due to the nature of SMM capabilities. As an example, a local attacker with administrative privileges (or a remote attacker with administrative privileges) can exploit these vulnerabilities to elevate privileges above the operating system to execute arbitrary code in SMM mode. These attacks can be invoked from the operating system using the unverified or unsafe SMI Handlers, and in some cases these bugs can also be triggered in the UEFI early boot phases ( as well as sleep and recovery like [ACPI](<https://uefi.org/acpi>)) before the operating system is initialized. \n\nIn summary, a local attacker with administrative privileges (in some cases a remote attacker with administrative privileges) can use malicious software to perform any of the following:\n\n * Invalidate many hardware security features (SecureBoot, Intel [BootGuard](<https://edk2-docs.gitbook.io/understanding-the-uefi-secure-boot-chain/secure_boot_chain_in_uefi/intel_boot_guard>))\n * Install persistent software that cannot be easily erased\n * Create backdoors and back communications channels to exfiltrate sensitive data\n\n### Solution\n\nInstall the latest stable version of firmware provided by your PC vendor or your nearest reseller of your computing environments. See the links below to resources and updates provided by specific vendors. \n\nIf your operating system supports automatic or managed updates for firmware, such as [Linux Vendor Firmware Service](<https://fwupd.org/>) (LVFS), apply the related software security updates. Binarly has also provided a set of UEFI software detection rules called [FwHunt rules](<https://github.com/binarly-io/FwHunt/tree/main/rules>) to assist with identifying vulnerable software. LVFS applies these FwHunt rules to detect and support the fix of firmware updates that are impacted by this advisory.\n\n### Acknowledgements\n\nThe efiXplorer team of Binarly researched and reported these vulnerabilities to Insyde Software. Insyde Software worked closely with CERT/CC during the coordinated disclosure process for these vulnerabilities.\n\nThis document was written by Vijay Sarvepalli.\n\n### Vendor Information\n\n796611\n\nFilter by status: All Affected Not Affected Unknown\n\nFilter by content: __ Additional information available\n\n__ Sort by: Status Alphabetical\n\nExpand all\n\n### Aruba Networks __ Affected\n\nNotified: 2021-10-18 Updated: 2023-07-17\n\n**Statement Date: July 17, 2023**\n\n**CVE-2020-27339**| Affected \n---|--- \n**CVE-2020-5953**| Affected \n**CVE-2021-33625**| Affected \n**CVE-2021-33626**| Affected \n**CVE-2021-33627**| Affected \n**CVE-2021-41837**| Affected \n**CVE-2021-41838**| Affected \n**CVE-2021-41839**| Affected \n**CVE-2021-41840**| Affected \n**CVE-2021-41841**| Affected \n**CVE-2021-42059**| Affected \n**CVE-2021-42060**| Not Affected \n**CVE-2021-42113**| Affected \n**CVE-2021-42554**| Affected \n**CVE-2021-43323**| Affected \n**CVE-2021-43522**| Affected \n**CVE-2021-43615**| Not Affected \n**CVE-2021-45969**| Not Affected \n**CVE-2021-45970**| Not Affected \n**CVE-2021-45971**| Not Affected \n**CVE-2022-24030**| Not Affected \n**CVE-2022-24031**| Not Affected \n**CVE-2022-24069**| Not Affected \n**CVE-2022-28806**| Not Affected \n \n#### Vendor Statement\n\nAruba has published information about products affected by these vulnerabilities at https://www.arubanetworks.com/support-services/security-bulletins/ with the specific URLs listed as references.\n\n#### References\n\n * <https://www.arubanetworks.com/assets/alert/ARUBA-PSA-2022-001.txt>\n * <https://www.arubanetworks.com/assets/alert/ARUBA-PSA-2022-002.txt>\n\n### Atos SE __ Affected\n\nNotified: 2022-02-04 Updated: 2022-02-04\n\n**Statement Date: February 04, 2022**\n\n**CVE-2020-27339**| Unknown \n---|--- \n**CVE-2020-5953**| Affected \n**CVE-2021-33625**| Affected \n**CVE-2021-33626**| Unknown \n**CVE-2021-33627**| Unknown \n**CVE-2021-41837**| Unknown \n**CVE-2021-41838**| Unknown \n**CVE-2021-41839**| Unknown \n**CVE-2021-41840**| Unknown \n**CVE-2021-41841**| Unknown \n**CVE-2021-42059**| Affected \n**CVE-2021-42060**| Affected \n**CVE-2021-42113**| Affected \n**CVE-2021-42554**| Affected \n**CVE-2021-43323**| Affected \n**CVE-2021-43522**| Affected \n**CVE-2021-43615**| Affected \n**CVE-2021-45969**| Affected \n**CVE-2021-45970**| Affected \n**CVE-2021-45971**| Affected \n**CVE-2022-24030**| Affected \n**CVE-2022-24031**| Affected \n**CVE-2022-24069**| Affected \n**CVE-2022-28806**| Unknown \n \n#### Vendor Statement\n\nOn February 1st, 2022, CERT-CC, Insyde Inc., and Binarly Inc. collectively disclosed a set of vulnerabilities affecting InsydeH2O Hardware-2-Operating System (H2O) UEFI Bios. These vulnerabilities generalize to all Intel configurations a 2020 vulnerability affecting a version of InsydeH2O that supported a specific Intel chipset (CVE-2020-5953). They affect any product using UEFI Bios based on InsydeH2O, including some BullSequana products. Atos is liaising closely with its suppliers and investigating the exact nature of these vulnerabilities to provide validated remediation.\n\n### Fujitsu __ Affected\n\nNotified: 2021-09-21 Updated: 2022-11-09\n\n**Statement Date: June 03, 2022**\n\n**CVE-2020-27339**| Not Affected \n---|--- \n**Vendor Statement:** \nInsyde Security Advisory INSYDE-SA-2021001 (CVE-2020-27339) on InsydeH2O is not part of this 2022/Q2 Insyde Security Advisory (ISA). The Fujitsu PSIRT already addressed the Insyde Security Advisory internally and released dedicated Fujitsu PSIRT Security Notice FCCL-IS-2021-061600. \n**CVE-2020-5953**| Affected \n**CVE-2021-33625**| Affected \n**CVE-2021-33626**| Affected \n**CVE-2021-33627**| Affected \n**CVE-2021-41837**| Affected \n**CVE-2021-41838**| Affected \n**CVE-2021-41839**| Affected \n**CVE-2021-41840**| Affected \n**CVE-2021-41841**| Affected \n**CVE-2021-42059**| Affected \n**CVE-2021-42060**| Affected \n**CVE-2021-42113**| Affected \n**CVE-2021-42554**| Affected \n**CVE-2021-43323**| Affected \n**CVE-2021-43522**| Affected \n**CVE-2021-43615**| Affected \n**CVE-2021-45969**| Affected \n**CVE-2021-45970**| Not Affected \n**Vendor Statement:** \nInsyde Security Advisory INSYDE-SA-2022002 (CVE-2021-45970) on InsydeH2O, as part of this 2022/Q2 Insyde Security Advisory (ISA), does not affect any Fujitsu product. \n**CVE-2021-45971**| Affected \n**CVE-2022-24030**| Affected \n**CVE-2022-24031**| Affected \n**CVE-2022-24069**| Affected \n**CVE-2022-28806**| Affected \n \n#### Vendor Statement\n\nFujitsu is aware of the security vulnerabilities in Insyde firmware (InsydeH2O UEFI-BIOS).\n\nAffected products are Fujitsu CCD (Client Computing Device) mobile devices.\n\nThe Fujitsu PSIRT released FCCL-IS-2021-090903 on https://security.ts.fujitsu.com (Security Advisories) accordingly.\n\nIn case of questions regarding this Fujitsu PSIRT Security Notice, please contact the Fujitsu PSIRT (Fujitsu-PSIRT@ts.fujitsu.com).\n\n#### References\n\n * <https://support.ts.fujitsu.com/ProductSecurity/content/Fujitsu-PSIRT-FCCL-IS-2021-090903-Security-Advisory.asp?lng=com>\n\n### Insyde Software Corporation __ Affected\n\nNotified: 2021-09-17 Updated: 2022-11-09\n\n**Statement Date: June 02, 2022**\n\n**CVE-2020-27339**| Affected \n---|--- \n**Vendor Statement:** \nThis corresponds to CVE-2020-27339. It affects the driver IdeBusDxe. It was discovered by an external security researcher and entered as an incident on 14 October 2020. It was independently reported by Binarly as BRLY-2021-020 in September 2021. The code that resolved the issue can be found in the following kernel versions: Kernel 5.1: 05.16.25, Kernel 5.2: 05.26.25, Kernel 5.3: 05.35.25, Kernel 5.4: 05.43.25, Kernel 5.5: Unaffected \n**CVE-2020-5953**| Affected \n**Vendor Statement:** \nThis corresponds to CVE-2020-5953. It affects the driver AsfSecureBootSmm. This issue was discovered by a 3rd party security researcher on a version of InsydeH2O that supported a specific Intel chipset. Insyde engineers subsequently discovered that drivers with the same name on versions of InsydeH2O supporting other Intel chipsets were similarly vulnerable. Prior to disclosure, this issue was independently discovered by the Binarly efiXplorer team. The fixed versions were as follows (using the Intel code name): Intel Kaby Lake - 05.12.09.0074, Intel Cannon Lake - 05.34.03.0029, Intel Coffee Lake - 05.34.03.0029, Intel Whiskey Lake (on Cannon Lake) - 05.34.03.0029, Intel Whiskey Lake - 05.23.45.0023, Intel Whiskey Lake (Server/Embedded) - TBD, Intel Comet Lake - 05.23.04.0045, Intel Comet Lake (Server/Embedded) - 05.34.03.0029, Intel Mehlow - TBD, Intel Greenlow/Greenlow-R - TBD, Intel Ice Lake - 05.33.15.0034, Intel Rocket Lake - Unaffected, Intel Tiger Lake - 05.42.03.0010, Intel Alder Lake - Unaffected \n**CVE-2021-33625**| Affected \n**Vendor Statement:** \nThis affects the HddPassword driver. It was reported by the Binarly efiXplorer team. Fixes are available in the InsydeH2O kernel: Kernel 5.1: 05.16.23, Kernel 5.2: 05.26.23, Kernel 5.3: 05.35.23, Kernel 5.4: 05.43.22, Kernel 5.5: 05.51.22 \n**CVE-2021-33626**| Affected \n**Vendor Statement:** \nThis corresponds to CVE-2021-33626. It affects the driver SmmResourceCheckDxe. This issue was discovered by Insyde engineering during an internal security review of several Insyde drivers and entered as a security incident on May 28, 2021. It was independently reported by Binaryly (BRLY-2021-013) in September 2021. It was fixed in the following Insyde kernel versions on June 1, 2021. Kernel 5.1: 05.16.23 Kernel 5.2: 05.26.23 Kernel 5.3: 05.35.23 Kernel 5.4: 05.43.23 Kernel 5.5: 05.51.23 \n**CVE-2021-33627**| Affected \n**Vendor Statement:** \nThis corresponds fo CVE-2021-33627. It affects the driver FwBlockServiceSmm. This issue was discovered by Insyde engineering during an internal security review and reported on 25 May 2021. It was independently reported by Binarly (BRLY-2021-011) in September 2021. It was fixed in the following Insyde kernel versions. Kernel 5.0: 05.08.29. Kernel 5.1: 05.16.29. Kernel 5.2: 05.26.29. Kernel 5.3: 05.35.29. Kernel 5.4: Unaffected. Kernel 5.5: Unaffected. \n**CVE-2021-41837**| Affected \n**Vendor Statement:** \nThis corresponds to CVE-2021-41837. It affects the AhciBusDxe driver. This issue was discovered by the Binarly efiXplorer team. The fixed versions of Kernel 5.0: 05.08.41, Kernel 5.1: 05.16.41, Kernel 5.2: 05.26.41, Kernel 5.3: 05.35.41, Kernel 5.4: 05.43.41, Kernel 5.5: 05.51.41 \n**CVE-2021-41838**| Affected \n**Vendor Statement:** \nThis corresponds to CVE-2021-41838. It affects the driver NvmExpressDxe driver. This issue was discovered by the Binarly efiXplorer team. The fixed versions are Kernel 5.1: 05.16.42, Kernel 5.2: 05.26.42, Kernel 5.3: 05.35.42, Kernel 5.4: 05.43.42, Kernel 5.5: 05.51.42 \n**CVE-2021-41839**| Affected \n**Vendor Statement:** \nThis corresponds to CVE-2021-41839. It affects the driver NvmExpressDxe. This issue was discovered by Insyde engineering during an internal security review of several Insyde drivers and entered as a security incident on May 28, 2021. It was independently reported by Binarly (BRLY-2021-017) in September 2021. It was fixed in the following Insyde kernel versions on June 18, 2021. Kernel 5.0: Unaffected. Kernel 5.1: 05.16.25 Kernel 5.2: 05.26.25 Kernel 5.3: 05.35.25 Kernel 5.4: 05.43.25 Kernel 5.5: 05.51.25 \n**CVE-2021-41840**| Affected \n**Vendor Statement:** \nThis corresponds to CVE-2021-41840. It affects the driver SdHostDriver. This issue was discovered internally by during an Insyde code review but was not classified as a security incident until September 17, 2021. It was independently reported by Binarly (BRLY-2021-019) in September 2021. The code that fixed the issue can be found in the following Insyde kernel versions, starting on August 28, 2020. Kernel 5.0: not present. Kernel 5.1: not present. Kernel 5.2: 05.23.35 Kernel 5.3: 05.32.35 Kernel 5.4: 05.40.35 Kernel 5.5: not present. \n**CVE-2021-41841**| Affected \n**Vendor Statement:** \nThis corresponds to CVE-2021-41841. It affects the driver AhciBusDxe. This issue was discovered by a 3rd party security researcher and entered as a security incident on May 26, 2021. It was independently reported by Binarly (BRLY-2021-018) in September 2021. It was fixed in the following Insyde kernel versions on July 26, 2021. Kernel 5.0: 05.08.29 Kernel 5.1: 05.16.29 Kernel 5.2: 05.26.29 Kernel 5.3: 05.35.29 Kernel 5.4: 05.43.29 Kernel 5.5: 05.51.29 \n**CVE-2021-42059**| Affected \n**Vendor Statement:** \nThis affects the DisplayTypeDxe driver. It was reported by the Binarly efiXplorer team. It was fixed in the InsydeH2O kernel: Kernel 5.0 05.08.41, Kernel 5.1: 05.16.41, Kernel 5.2: 05.26.41, Kernel 5.3: 05.35.41, Kernel 5.4: 05.42.20, Kernel 5.5: unaffected. \n**CVE-2021-42060**| Affected \n**Vendor Statement:** \nThis affects the Int15ServiceSmm driver. It was reported by the Binarly efiXplorer team. It was fixed in InsydeH2O versions kernel 5.0: 05.08.49, kernel 5.1: 05.16.49, kernel 5.2: 05.23.22, Kernel 5.3: 05.32.22, Kernel 5.4: unaffected, kernel 5.5: unaffected. \n**CVE-2021-42113**| Affected \n**Vendor Statement:** \nThis corresponds to CVE-2021-42113. It affects the StorageSecurityCommandDxe driver. It was discovered by the Binarly efiXplorer team. It is fixed in the InsydeH2O kernel: Kernel 5.1: 05.14.34, Kernel 5.2: 05.24.34, Kernel 5.3: 05.33.34, Kernel 5.4: unaffected. Kernel 5.5: unaffected. \n**CVE-2021-42554**| Affected \n**Vendor Statement:** \nThis affects the FvbServicesRuntimeDxe driver. It was reported by the Binarly efiXplorer team. It is fixed in the following InsydeH2O kernel versions: Kernel 5.0: 05.08.42, Kernel 5.1: 05.16.42, Kernel 5.2: 05.26.42, Kernel 5.3: 05.35.42, Kernel 5.4: 05.42.51, Kernel 5.5: 05.50.51 \n**CVE-2021-43323**| Affected \n**Vendor Statement:** \nThis affects the UsbCoreDxe driver. It was reported by the Binarly efiXplorer team. The fixes are available for the Insyde kernel: Kernel 5.0: 05.08.45, Kernel 5.1: 05.16.45, Kernel 5.2: 05.26.45, Kernel 5.3: 05.35.45, Kernel 5.4: 05.43.45, Kernel 5.5: 05.51.45. \n**CVE-2021-43522**| Affected \n**CVE-2021-43615**| Affected \n**Vendor Statement:** \nThis affects the HddPassword driver. It was reported by the Binarly efiXplorer team. It was fixed in the InsydeH2O kernel: Kernel 5.1: 05.16.23, Kernel 5.2: 05.23.22, Kernel 5.3: 05.32.22, Kernel 5.4: Unaffected, Kernel 5.5: Unaffected \n**CVE-2021-45969**| Affected \n**Vendor Statement:** \nThis corresponds to CVE-2021-45969. It affects the driver AhciBusDxe. This issue was discovered by Insyde engineering during an internal security review of several Insyde drivers and entered as a security incident on May 28, 2021. It was independently reported by Binaryly (BRLY-2021-016) in September 2021. It was fixed in the following Insyde kernel versions on June 18, 2021. It was fixed in the following versions: Kernel 5.1: 05.16.25 Kernel 5.2: 05.26.25 Kernel 5.3: 05.35.25 Kernel 5.4: 05.43.25 Kernel 5.5: 05.51.25. This issue was previously reported incorrectly as part of CVE-2020-27339. \n**CVE-2021-45970**| Affected \n**Vendor Statement:** \nThis corresponds to CVE-2021-45970. It affects the driver IdeBusDxe. This issue was discovered by Insyde engineering during an internal security review of several Insyde drivers and entered as a security incident on May 28, 2021. It was independently reported by Binarly (BRLY-2021-015) in September 2021. It was fixed in the following Insyde kernel versions on June 18, 2021. It was fixed in the following Insyde kernel versions: Kernel 5.1: 05.16.25 Kernel 5.2: 05.26.25 Kernel 5.3: 05.35.25 Kernel 5.4: 05.43.25 Kernel 5.5: 05.51.25. This issue was previously reported incorrectly as part of CVE-2020-27339. \n**CVE-2021-45971**| Affected \n**Vendor Statement:** \nThis corresponds to CVE-2021-45971. It affects the driver SdHostDriver. This issue was discovered by Insyde engineering during an internal security review of several Insyde drivers and entered as a security incident on May 28, 2021. It was independently reported by Binarly (BRLY-2021-012) in September 2021 It was fixed in the following Insyde kernel versions on June 18, 2021. Kernel 5.1: 05.16.25 Kernel 5.2: 05.26.25 Kernel 5.3: 05.35.25 Kernel 5.4: 05.43.25 Kernel 5.5: 05.51.25. It was previously reported incorrectly as part of CVE-2020-27339. \n**CVE-2022-24030**| Affected \n**Vendor Statement:** \nThis affects the AhciBusDxe driver. This issue was discovered by the Binarly efiXplorer team. The fixed versions of Kernel 5.0: 05.08.41, Kernel 5.1: 05.16.41, Kernel 5.2: 05.26.41, Kernel 5.3: 05.35.41, Kernel 5.4: 05.43.41, Kernel 5.5: 05.51.41 \n**CVE-2022-24031**| Affected \n**Vendor Statement:** \nThis affects the NvmExpressDxe driver. This issue was discovered by the Binarly efiXplorer team. The fixed versions are Kernel 5.1: 05.16.42, Kernel 5.2: 05.26.42, Kernel 5.3: 05.35.42, Kernel 5.4: 05.43.42, Kernel 5.5: 05.51.42 \n**CVE-2022-24069**| Affected \n**Vendor Statement:** \nThis issue corresponds to CVE-2022-24069. It affects the driver AhciBusDxe. This issue was discovered by the Binarly efiXplorer team. It was fixed in the following Insyde kernel versions on July 26, 2021. Kernel 5.0: 05.08.29 Kernel 5.1: 05.16.29 Kernel 5.2: 05.26.29 Kernel 5.3: 05.35.29 Kernel 5.4: 05.43.29 Kernel 5.5: 05.51.29 \n**CVE-2022-28806**| Not Affected \n \n#### Vendor Statement\n\nThese issues affect a broad range of Insyde's InsydeH2O products. They are not chipset specific, but they are specific to kernel versions, which are listed with each statement. We have disclosed these to all affected customers.\n\n### AMD Not Affected\n\nNotified: 2022-01-26 Updated: 2022-04-26\n\n**Statement Date: March 28, 2022**\n\n**CVE-2020-27339**| Not Affected \n---|--- \n**CVE-2020-5953**| Not Affected \n**CVE-2021-33625**| Not Affected \n**CVE-2021-33626**| Not Affected \n**CVE-2021-33627**| Not Affected \n**CVE-2021-41837**| Not Affected \n**CVE-2021-41838**| Not Affected \n**CVE-2021-41839**| Not Affected \n**CVE-2021-41840**| Not Affected \n**CVE-2021-41841**| Not Affected \n**CVE-2021-42059**| Not Affected \n**CVE-2021-42060**| Not Affected \n**CVE-2021-42113**| Not Affected \n**CVE-2021-42554**| Not Affected \n**CVE-2021-43323**| Not Affected \n**CVE-2021-43522**| Not Affected \n**CVE-2021-43615**| Not Affected \n**CVE-2021-45969**| Not Affected \n**CVE-2021-45970**| Not Affected \n**CVE-2021-45971**| Not Affected \n**CVE-2022-24030**| Not Affected \n**CVE-2022-24031**| Not Affected \n**CVE-2022-24069**| Not Affected \n**CVE-2022-28806**| Not Affected \n \n#### Vendor Statement\n\nWe have not received a statement from the vendor.\n\n### American Megatrends Incorporated (AMI) Not Affected\n\nNotified: 2022-01-18 Updated: 2022-04-26\n\n**Statement Date: February 10, 2022**\n\n**CVE-2020-27339**| Not Affected \n---|--- \n**CVE-2020-5953**| Not Affected \n**CVE-2021-33625**| Not Affected \n**CVE-2021-33626**| Not Affected \n**CVE-2021-33627**| Not Affected \n**CVE-2021-41837**| Not Affected \n**CVE-2021-41838**| Not Affected \n**CVE-2021-41839**| Not Affected \n**CVE-2021-41840**| Not Affected \n**CVE-2021-41841**| Not Affected \n**CVE-2021-42059**| Not Affected \n**CVE-2021-42060**| Not Affected \n**CVE-2021-42113**| Not Affected \n**CVE-2021-42554**| Not Affected \n**CVE-2021-43323**| Not Affected \n**CVE-2021-43522**| Not Affected \n**CVE-2021-43615**| Not Affected \n**CVE-2021-45969**| Not Affected \n**CVE-2021-45970**| Not Affected \n**CVE-2021-45971**| Not Affected \n**CVE-2022-24030**| Not Affected \n**CVE-2022-24031**| Not Affected \n**CVE-2022-24069**| Not Affected \n**CVE-2022-28806**| Not Affected \n \n#### Vendor Statement\n\nWe have not received a statement from the vendor.\n\n### Hewlett Packard Enterprise __ Not Affected\n\nNotified: 2021-10-05 Updated: 2022-04-26\n\n**Statement Date: March 02, 2022**\n\n**CVE-2020-27339**| Not Affected \n---|--- \n**CVE-2020-5953**| Not Affected \n**CVE-2021-33625**| Not Affected \n**CVE-2021-33626**| Not Affected \n**CVE-2021-33627**| Not Affected \n**CVE-2021-41837**| Not Affected \n**CVE-2021-41838**| Not Affected \n**CVE-2021-41839**| Not Affected \n**CVE-2021-41840**| Not Affected \n**CVE-2021-41841**| Not Affected \n**CVE-2021-42059**| Not Affected \n**CVE-2021-42060**| Not Affected \n**CVE-2021-42113**| Not Affected \n**CVE-2021-42554**| Not Affected \n**CVE-2021-43323**| Not Affected \n**CVE-2021-43522**| Not Affected \n**CVE-2021-43615**| Not Affected \n**CVE-2021-45969**| Not Affected \n**CVE-2021-45970**| Not Affected \n**CVE-2021-45971**| Not Affected \n**CVE-2022-24030**| Not Affected \n**CVE-2022-24031**| Not Affected \n**CVE-2022-24069**| Not Affected \n**CVE-2022-28806**| Not Affected \n \n#### Vendor Statement\n\nHPE has evaluated the integration of the InsydeH20 UEFI BIOS in HPE products. Most HPE products do not integrate, include, or use the InsydeH20 UEFI BIOS and are therefore not affected by these vulnerabilities. A small number of HPE products do include the InsydeH20 UEFI BIOS, but are not affected by these vulnerabilities due to the way the InsydeH20 UEFI BIOS is implemented. Some HPE Aruba products use the InsydeH20 UEFI BIOS and they are affected by some of these vulnerabilities.\n\nDETAILS For more information about the HPE Aruba products affected by the InsydeH20 UEFI BIOS vulnerabilities, see the following Aruba Product Security Advisories:\n\nhttps://www.arubanetworks.com/assets/alert/ARUBA-PSA-2022-001.txt Non-HPE site\n\nhttps://www.arubanetworks.com/assets/alert/ARUBA-PSA-2022-002.txt Non-HPE site\n\n### Intel Not Affected\n\nNotified: 2021-10-05 Updated: 2022-04-26\n\n**Statement Date: February 04, 2022**\n\n**CVE-2020-27339**| Not Affected \n---|--- \n**CVE-2020-5953**| Not Affected \n**CVE-2021-33625**| Not Affected \n**CVE-2021-33626**| Not Affected \n**CVE-2021-33627**| Not Affected \n**CVE-2021-41837**| Not Affected \n**CVE-2021-41838**| Not Affected \n**CVE-2021-41839**| Not Affected \n**CVE-2021-41840**| Not Affected \n**CVE-2021-41841**| Not Affected \n**CVE-2021-42059**| Not Affected \n**CVE-2021-42060**| Not Affected \n**CVE-2021-42113**| Not Affected \n**CVE-2021-42554**| Not Affected \n**CVE-2021-43323**| Not Affected \n**CVE-2021-43522**| Not Affected \n**CVE-2021-43615**| Not Affected \n**CVE-2021-45969**| Not Affected \n**CVE-2021-45970**| Not Affected \n**CVE-2021-45971**| Not Affected \n**CVE-2022-24030**| Not Affected \n**CVE-2022-24031**| Not Affected \n**CVE-2022-24069**| Not Affected \n**CVE-2022-28806**| Not Affected \n \n#### Vendor Statement\n\nWe have not received a statement from the vendor.\n\n### NetApp __ Not Affected\n\nNotified: 2022-02-25 Updated: 2022-02-25\n\n**Statement Date: February 24, 2022**\n\n**CVE-2020-27339**| Not Affected \n---|--- \n**CVE-2020-5953**| Unknown \n**CVE-2021-33625**| Unknown \n**CVE-2021-33626**| Unknown \n**CVE-2021-33627**| Unknown \n**CVE-2021-41837**| Unknown \n**CVE-2021-41838**| Unknown \n**CVE-2021-41839**| Unknown \n**CVE-2021-41840**| Not Affected \n**CVE-2021-41841**| Unknown \n**CVE-2021-42059**| Not Affected \n**CVE-2021-42060**| Unknown \n**CVE-2021-42113**| Not Affected \n**CVE-2021-42554**| Unknown \n**CVE-2021-43323**| Unknown \n**CVE-2021-43522**| Not Affected \n**CVE-2021-43615**| Not Affected \n**CVE-2021-45969**| Unknown \n**CVE-2021-45970**| Unknown \n**CVE-2021-45971**| Unknown \n**CVE-2022-24030**| Unknown \n**CVE-2022-24031**| Unknown \n**CVE-2022-24069**| Unknown \n**CVE-2022-28806**| Not Affected \n \n#### Vendor Statement\n\nWe have not received a statement from the vendor.\n\n#### References\n\n * <https://security.netapp.com/advisory/ntap-20220217-0014/>\n * <https://security.netapp.com/advisory/ntap-20220216-0004/>\n * <https://security.netapp.com/advisory/ntap-20220217-0014/>\n\n#### CERT Addendum\n\nNetApp is still investigating some vulnerabilities disclosed. Visit NetApp Advisory page for details. https://security.netapp.com/advisory/\n\n### Phoenix Technologies __ Not Affected\n\nNotified: 2022-03-24 Updated: 2022-04-26\n\n**Statement Date: March 24, 2022**\n\n**CVE-2020-27339**| Not Affected \n---|--- \n**CVE-2020-5953**| Not Affected \n**CVE-2021-33625**| Not Affected \n**CVE-2021-33626**| Not Affected \n**CVE-2021-33627**| Not Affected \n**CVE-2021-41837**| Not Affected \n**CVE-2021-41838**| Not Affected \n**CVE-2021-41839**| Not Affected \n**CVE-2021-41840**| Not Affected \n**CVE-2021-41841**| Not Affected \n**CVE-2021-42059**| Not Affected \n**CVE-2021-42060**| Not Affected \n**CVE-2021-42113**| Not Affected \n**CVE-2021-42554**| Not Affected \n**CVE-2021-43323**| Not Affected \n**CVE-2021-43522**| Not Affected \n**CVE-2021-43615**| Not Affected \n**CVE-2021-45969**| Not Affected \n**CVE-2021-45970**| Not Affected \n**CVE-2021-45971**| Not Affected \n**CVE-2022-24030**| Not Affected \n**CVE-2022-24031**| Not Affected \n**CVE-2022-24069**| Not Affected \n**CVE-2022-28806**| Not Affected \n \n#### Vendor Statement\n\nOur review indicates that our firmware code is Not Affected by these vulnerabilities.\n\n### Rockwell Automation __ Not Affected\n\nNotified: 2022-01-26 Updated: 2022-04-26\n\n**Statement Date: January 28, 2022**\n\n**CVE-2020-27339**| Not Affected \n---|--- \n**CVE-2020-5953**| Not Affected \n**CVE-2021-33625**| Not Affected \n**CVE-2021-33626**| Not Affected \n**CVE-2021-33627**| Not Affected \n**CVE-2021-41837**| Not Affected \n**CVE-2021-41838**| Not Affected \n**CVE-2021-41839**| Not Affected \n**CVE-2021-41840**| Not Affected \n**CVE-2021-41841**| Not Affected \n**CVE-2021-42059**| Not Affected \n**CVE-2021-42060**| Not Affected \n**CVE-2021-42113**| Not Affected \n**CVE-2021-42554**| Not Affected \n**CVE-2021-43323**| Not Affected \n**CVE-2021-43522**| Not Affected \n**CVE-2021-43615**| Not Affected \n**CVE-2021-45969**| Not Affected \n**CVE-2021-45970**| Not Affected \n**CVE-2021-45971**| Not Affected \n**CVE-2022-24030**| Not Affected \n**CVE-2022-24031**| Not Affected \n**CVE-2022-24069**| Not Affected \n**CVE-2022-28806**| Not Affected \n \n#### Vendor Statement\n\nNot affected\n\n#### References\n\n * Not affected\n\n### Supermicro Not Affected\n\nNotified: 2022-01-26 Updated: 2022-04-26\n\n**Statement Date: January 28, 2022**\n\n**CVE-2020-27339**| Not Affected \n---|--- \n**CVE-2020-5953**| Not Affected \n**CVE-2021-33625**| Not Affected \n**CVE-2021-33626**| Not Affected \n**CVE-2021-33627**| Not Affected \n**CVE-2021-41837**| Not Affected \n**CVE-2021-41838**| Not Affected \n**CVE-2021-41839**| Not Affected \n**CVE-2021-41840**| Not Affected \n**CVE-2021-41841**| Not Affected \n**CVE-2021-42059**| Not Affected \n**CVE-2021-42060**| Not Affected \n**CVE-2021-42113**| Not Affected \n**CVE-2021-42554**| Not Affected \n**CVE-2021-43323**| Not Affected \n**CVE-2021-43522**| Not Affected \n**CVE-2021-43615**| Not Affected \n**CVE-2021-45969**| Not Affected \n**CVE-2021-45970**| Not Affected \n**CVE-2021-45971**| Not Affected \n**CVE-2022-24030**| Not Affected \n**CVE-2022-24031**| Not Affected \n**CVE-2022-24069**| Not Affected \n**CVE-2022-28806**| Not Affected \n \n#### Vendor Statement\n\nWe have not received a statement from the vendor.\n\n### Toshiba Corporation Not Affected\n\nNotified: 2021-10-05 Updated: 2022-02-01\n\n**Statement Date: October 06, 2021**\n\n**CVE-2020-27339**| Not Affected \n---|--- \n**CVE-2020-5953**| Not Affected \n**CVE-2021-33625**| Not Affected \n**CVE-2021-33626**| Not Affected \n**CVE-2021-33627**| Not Affected \n**CVE-2021-41837**| Not Affected \n**CVE-2021-41838**| Not Affected \n**CVE-2021-41839**| Not Affected \n**CVE-2021-41840**| Not Affected \n**CVE-2021-41841**| Not Affected \n**CVE-2021-42059**| Not Affected \n**CVE-2021-42060**| Not Affected \n**CVE-2021-42113**| Not Affected \n**CVE-2021-42554**| Not Affected \n**CVE-2021-43323**| Not Affected \n**CVE-2021-43522**| Not Affected \n**CVE-2021-43615**| Not Affected \n**CVE-2021-45969**| Not Affected \n**CVE-2021-45970**| Not Affected \n**CVE-2021-45971**| Not Affected \n**CVE-2022-24030**| Not Affected \n**CVE-2022-24031**| Not Affected \n**CVE-2022-24069**| Not Affected \n**CVE-2022-28806**| Not Affected \n \n#### Vendor Statement\n\nWe have not received a statement from the vendor.\n\n### Acer Unknown\n\nNotified: 2022-01-26 Updated: 2022-02-01 **CVE-2020-27339**| Unknown \n---|--- \n**CVE-2020-5953**| Unknown \n**CVE-2021-33625**| Unknown \n**CVE-2021-33626**| Unknown \n**CVE-2021-33627**| Unknown \n**CVE-2021-41837**| Unknown \n**CVE-2021-41838**| Unknown \n**CVE-2021-41839**| Unknown \n**CVE-2021-41840**| Unknown \n**CVE-2021-41841**| Unknown \n**CVE-2021-42059**| Unknown \n**CVE-2021-42060**| Unknown \n**CVE-2021-42113**| Unknown \n**CVE-2021-42554**| Unknown \n**CVE-2021-43323**| Unknown \n**CVE-2021-43522**| Unknown \n**CVE-2021-43615**| Unknown \n**CVE-2021-45969**| Unknown \n**CVE-2021-45970**| Unknown \n**CVE-2021-45971**| Unknown \n**CVE-2022-24030**| Unknown \n**CVE-2022-24031**| Unknown \n**CVE-2022-24069**| Unknown \n**CVE-2022-28806**| Unknown \n \n#### Vendor Statement\n\nWe have not received a statement from the vendor.\n\n### ASUSTeK Computer Inc. Unknown\n\nNotified: 2021-10-05 Updated: 2022-02-01 **CVE-2020-27339**| Unknown \n---|--- \n**CVE-2020-5953**| Unknown \n**CVE-2021-33625**| Unknown \n**CVE-2021-33626**| Unknown \n**CVE-2021-33627**| Unknown \n**CVE-2021-41837**| Unknown \n**CVE-2021-41838**| Unknown \n**CVE-2021-41839**| Unknown \n**CVE-2021-41840**| Unknown \n**CVE-2021-41841**| Unknown \n**CVE-2021-42059**| Unknown \n**CVE-2021-42060**| Unknown \n**CVE-2021-42113**| Unknown \n**CVE-2021-42554**| Unknown \n**CVE-2021-43323**| Unknown \n**CVE-2021-43522**| Unknown \n**CVE-2021-43615**| Unknown \n**CVE-2021-45969**| Unknown \n**CVE-2021-45970**| Unknown \n**CVE-2021-45971**| Unknown \n**CVE-2022-24030**| Unknown \n**CVE-2022-24031**| Unknown \n**CVE-2022-24069**| Unknown \n**CVE-2022-28806**| Unknown \n \n#### Vendor Statement\n\nWe have not received a statement from the vendor.\n\n### Dell Unknown\n\nNotified: 2021-10-05 Updated: 2022-02-01 **CVE-2020-27339**| Unknown \n---|--- \n**CVE-2020-5953**| Unknown \n**CVE-2021-33625**| Unknown \n**CVE-2021-33626**| Unknown \n**CVE-2021-33627**| Unknown \n**CVE-2021-41837**| Unknown \n**CVE-2021-41838**| Unknown \n**CVE-2021-41839**| Unknown \n**CVE-2021-41840**| Unknown \n**CVE-2021-41841**| Unknown \n**CVE-2021-42059**| Unknown \n**CVE-2021-42060**| Unknown \n**CVE-2021-42113**| Unknown \n**CVE-2021-42554**| Unknown \n**CVE-2021-43323**| Unknown \n**CVE-2021-43522**| Unknown \n**CVE-2021-43615**| Unknown \n**CVE-2021-45969**| Unknown \n**CVE-2021-45970**| Unknown \n**CVE-2021-45971**| Unknown \n**CVE-2022-24030**| Unknown \n**CVE-2022-24031**| Unknown \n**CVE-2022-24069**| Unknown \n**CVE-2022-28806**| Unknown \n \n#### Vendor Statement\n\nWe have not received a statement from the vendor.\n\n### Dynabook Inc. Unknown\n\nNotified: 2021-10-06 Updated: 2022-02-01 **CVE-2020-27339**| Unknown \n---|--- \n**CVE-2020-5953**| Unknown \n**CVE-2021-33625**| Unknown \n**CVE-2021-33626**| Unknown \n**CVE-2021-33627**| Unknown \n**CVE-2021-41837**| Unknown \n**CVE-2021-41838**| Unknown \n**CVE-2021-41839**| Unknown \n**CVE-2021-41840**| Unknown \n**CVE-2021-41841**| Unknown \n**CVE-2021-42059**| Unknown \n**CVE-2021-42060**| Unknown \n**CVE-2021-42113**| Unknown \n**CVE-2021-42554**| Unknown \n**CVE-2021-43323**| Unknown \n**CVE-2021-43522**| Unknown \n**CVE-2021-43615**| Unknown \n**CVE-2021-45969**| Unknown \n**CVE-2021-45970**| Unknown \n**CVE-2021-45971**| Unknown \n**CVE-2022-24030**| Unknown \n**CVE-2022-24031**| Unknown \n**CVE-2022-24069**| Unknown \n**CVE-2022-28806**| Unknown \n \n#### Vendor Statement\n\nWe have not received a statement from the vendor.\n\n### Gamma Tech Computer Corp. Unknown\n\nNotified: 2022-01-26 Updated: 2022-02-01 **CVE-2020-27339**| Unknown \n---|--- \n**CVE-2020-5953**| Unknown \n**CVE-2021-33625**| Unknown \n**CVE-2021-33626**| Unknown \n**CVE-2021-33627**| Unknown \n**CVE-2021-41837**| Unknown \n**CVE-2021-41838**| Unknown \n**CVE-2021-41839**| Unknown \n**CVE-2021-41840**| Unknown \n**CVE-2021-41841**| Unknown \n**CVE-2021-42059**| Unknown \n**CVE-2021-42060**| Unknown \n**CVE-2021-42113**| Unknown \n**CVE-2021-42554**| Unknown \n**CVE-2021-43323**| Unknown \n**CVE-2021-43522**| Unknown \n**CVE-2021-43615**| Unknown \n**CVE-2021-45969**| Unknown \n**CVE-2021-45970**| Unknown \n**CVE-2021-45971**| Unknown \n**CVE-2022-24030**| Unknown \n**CVE-2022-24031**| Unknown \n**CVE-2022-24069**| Unknown \n**CVE-2022-28806**| Unknown \n \n#### Vendor Statement\n\nWe have not received a statement from the vendor.\n\n### GETAC Inc. Unknown\n\nNotified: 2022-01-26 Updated: 2022-02-01 **CVE-2020-27339**| Unknown \n---|--- \n**CVE-2020-5953**| Unknown \n**CVE-2021-33625**| Unknown \n**CVE-2021-33626**| Unknown \n**CVE-2021-33627**| Unknown \n**CVE-2021-41837**| Unknown \n**CVE-2021-41838**| Unknown \n**CVE-2021-41839**| Unknown \n**CVE-2021-41840**| Unknown \n**CVE-2021-41841**| Unknown \n**CVE-2021-42059**| Unknown \n**CVE-2021-42060**| Unknown \n**CVE-2021-42113**| Unknown \n**CVE-2021-42554**| Unknown \n**CVE-2021-43323**| Unknown \n**CVE-2021-43522**| Unknown \n**CVE-2021-43615**| Unknown \n**CVE-2021-45969**| Unknown \n**CVE-2021-45970**| Unknown \n**CVE-2021-45971**| Unknown \n**CVE-2022-24030**| Unknown \n**CVE-2022-24031**| Unknown \n**CVE-2022-24069**| Unknown \n**CVE-2022-28806**| Unknown \n \n#### Vendor Statement\n\nWe have not received a statement from the vendor.\n\n### HP Inc. Unknown\n\nNotified: 2021-10-05 Updated: 2022-02-01 **CVE-2020-27339**| Unknown \n---|--- \n**CVE-2020-5953**| Unknown \n**CVE-2021-33625**| Unknown \n**CVE-2021-33626**| Unknown \n**CVE-2021-33627**| Unknown \n**CVE-2021-41837**| Unknown \n**CVE-2021-41838**| Unknown \n**CVE-2021-41839**| Unknown \n**CVE-2021-41840**| Unknown \n**CVE-2021-41841**| Unknown \n**CVE-2021-42059**| Unknown \n**CVE-2021-42060**| Unknown \n**CVE-2021-42113**| Unknown \n**CVE-2021-42554**| Unknown \n**CVE-2021-43323**| Unknown \n**CVE-2021-43522**| Unknown \n**CVE-2021-43615**| Unknown \n**CVE-2021-45969**| Unknown \n**CVE-2021-45970**| Unknown \n**CVE-2021-45971**| Unknown \n**CVE-2022-24030**| Unknown \n**CVE-2022-24031**| Unknown \n**CVE-2022-24069**| Unknown \n**CVE-2022-28806**| Unknown \n \n#### Vendor Statement\n\nWe have not received a statement from the vendor.\n\n### Juniper Networks Unknown\n\nNotified: 2022-01-26 Updated: 2022-02-01 **CVE-2020-27339**| Unknown \n---|--- \n**CVE-2020-5953**| Unknown \n**CVE-2021-33625**| Unknown \n**CVE-2021-33626**| Unknown \n**CVE-2021-33627**| Unknown \n**CVE-2021-41837**| Unknown \n**CVE-2021-41838**| Unknown \n**CVE-2021-41839**| Unknown \n**CVE-2021-41840**| Unknown \n**CVE-2021-41841**| Unknown \n**CVE-2021-42059**| Unknown \n**CVE-2021-42060**| Unknown \n**CVE-2021-42113**| Unknown \n**CVE-2021-42554**| Unknown \n**CVE-2021-43323**| Unknown \n**CVE-2021-43522**| Unknown \n**CVE-2021-43615**| Unknown \n**CVE-2021-45969**| Unknown \n**CVE-2021-45970**| Unknown \n**CVE-2021-45971**| Unknown \n**CVE-2022-24030**| Unknown \n**CVE-2022-24031**| Unknown \n**CVE-2022-24069**| Unknown \n**CVE-2022-28806**| Unknown \n \n#### Vendor Statement\n\nWe have not received a statement from the vendor.\n\n### Lenovo Unknown\n\nNotified: 2021-10-05 Updated: 2022-02-01 **CVE-2020-27339**| Unknown \n---|--- \n**CVE-2020-5953**| Unknown \n**CVE-2021-33625**| Unknown \n**CVE-2021-33626**| Unknown \n**CVE-2021-33627**| Unknown \n**CVE-2021-41837**| Unknown \n**CVE-2021-41838**| Unknown \n**CVE-2021-41839**| Unknown \n**CVE-2021-41840**| Unknown \n**CVE-2021-41841**| Unknown \n**CVE-2021-42059**| Unknown \n**CVE-2021-42060**| Unknown \n**CVE-2021-42113**| Unknown \n**CVE-2021-42554**| Unknown \n**CVE-2021-43323**| Unknown \n**CVE-2021-43522**| Unknown \n**CVE-2021-43615**| Unknown \n**CVE-2021-45969**| Unknown \n**CVE-2021-45970**| Unknown \n**CVE-2021-45971**| Unknown \n**CVE-2022-24030**| Unknown \n**CVE-2022-24031**| Unknown \n**CVE-2022-24069**| Unknown \n**CVE-2022-28806**| Unknown \n \n#### Vendor Statement\n\nWe have not received a statement from the vendor.\n\n### Microsoft Unknown\n\nNotified: 2021-10-05 Updated: 2022-02-01 **CVE-2020-27339**| Unknown \n---|--- \n**CVE-2020-5953**| Unknown \n**CVE-2021-33625**| Unknown \n**CVE-2021-33626**| Unknown \n**CVE-2021-33627**| Unknown \n**CVE-2021-41837**| Unknown \n**CVE-2021-41838**| Unknown \n**CVE-2021-41839**| Unknown \n**CVE-2021-41840**| Unknown \n**CVE-2021-41841**| Unknown \n**CVE-2021-42059**| Unknown \n**CVE-2021-42060**| Unknown \n**CVE-2021-42113**| Unknown \n**CVE-2021-42554**| Unknown \n**CVE-2021-43323**| Unknown \n**CVE-2021-43522**| Unknown \n**CVE-2021-43615**| Unknown \n**CVE-2021-45969**| Unknown \n**CVE-2021-45970**| Unknown \n**CVE-2021-45971**| Unknown \n**CVE-2022-24030**| Unknown \n**CVE-2022-24031**| Unknown \n**CVE-2022-24069**| Unknown \n**CVE-2022-28806**| Unknown \n \n#### Vendor Statement\n\nWe have not received a statement from the vendor.\n\n### Microsoft Vulnerability Research Unknown\n\nNotified: 2021-10-06 Updated: 2022-02-01 **CVE-2020-27339**| Unknown \n---|--- \n**CVE-2020-5953**| Unknown \n**CVE-2021-33625**| Unknown \n**CVE-2021-33626**| Unknown \n**CVE-2021-33627**| Unknown \n**CVE-2021-41837**| Unknown \n**CVE-2021-41838**| Unknown \n**CVE-2021-41839**| Unknown \n**CVE-2021-41840**| Unknown \n**CVE-2021-41841**| Unknown \n**CVE-2021-42059**| Unknown \n**CVE-2021-42060**| Unknown \n**CVE-2021-42113**| Unknown \n**CVE-2021-42554**| Unknown \n**CVE-2021-43323**| Unknown \n**CVE-2021-43522**| Unknown \n**CVE-2021-43615**| Unknown \n**CVE-2021-45969**| Unknown \n**CVE-2021-45970**| Unknown \n**CVE-2021-45971**| Unknown \n**CVE-2022-24030**| Unknown \n**CVE-2022-24031**| Unknown \n**CVE-2022-24069**| Unknown \n**CVE-2022-28806**| Unknown \n \n#### Vendor Statement\n\nWe have not received a statement from the vendor.\n\n### ReactOS Unknown\n\nNotified: 2022-01-26 Updated: 2022-02-01 **CVE-2020-27339**| Unknown \n---|--- \n**CVE-2020-5953**| Unknown \n**CVE-2021-33625**| Unknown \n**CVE-2021-33626**| Unknown \n**CVE-2021-33627**| Unknown \n**CVE-2021-41837**| Unknown \n**CVE-2021-41838**| Unknown \n**CVE-2021-41839**| Unknown \n**CVE-2021-41840**| Unknown \n**CVE-2021-41841**| Unknown \n**CVE-2021-42059**| Unknown \n**CVE-2021-42060**| Unknown \n**CVE-2021-42113**| Unknown \n**CVE-2021-42554**| Unknown \n**CVE-2021-43323**| Unknown \n**CVE-2021-43522**| Unknown \n**CVE-2021-43615**| Unknown \n**CVE-2021-45969**| Unknown \n**CVE-2021-45970**| Unknown \n**CVE-2021-45971**| Unknown \n**CVE-2022-24030**| Unknown \n**CVE-2022-24031**| Unknown \n**CVE-2022-24069**| Unknown \n**CVE-2022-28806**| Unknown \n \n#### Vendor Statement\n\nWe have not received a statement from the vendor.\n\n### Siemens Unknown\n\nNotified: 2022-01-26 Updated: 2022-02-01 **CVE-2020-27339**| Unknown \n---|--- \n**CVE-2020-5953**| Unknown \n**CVE-2021-33625**| Unknown \n**CVE-2021-33626**| Unknown \n**CVE-2021-33627**| Unknown \n**CVE-2021-41837**| Unknown \n**CVE-2021-41838**| Unknown \n**CVE-2021-41839**| Unknown \n**CVE-2021-41840**| Unknown \n**CVE-2021-41841**| Unknown \n**CVE-2021-42059**| Unknown \n**CVE-2021-42060**| Unknown \n**CVE-2021-42113**| Unknown \n**CVE-2021-42554**| Unknown \n**CVE-2021-43323**| Unknown \n**CVE-2021-43522**| Unknown \n**CVE-2021-43615**| Unknown \n**CVE-2021-45969**| Unknown \n**CVE-2021-45970**| Unknown \n**CVE-2021-45971**| Unknown \n**CVE-2022-24030**| Unknown \n**CVE-2022-24031**| Unknown \n**CVE-2022-24069**| Unknown \n**CVE-2022-28806**| Unknown \n \n#### Vendor Statement\n\nWe have not received a statement from the vendor.\n\n### Siemens Nixdorf AG Unknown\n\nUpdated: 2022-02-01 **CVE-2020-27339**| Unknown \n---|--- \n**CVE-2020-5953**| Unknown \n**CVE-2021-33625**| Unknown \n**CVE-2021-33626**| Unknown \n**CVE-2021-33627**| Unknown \n**CVE-2021-41837**| Unknown \n**CVE-2021-41838**| Unknown \n**CVE-2021-41839**| Unknown \n**CVE-2021-41840**| Unknown \n**CVE-2021-41841**| Unknown \n**CVE-2021-42059**| Unknown \n**CVE-2021-42060**| Unknown \n**CVE-2021-42113**| Unknown \n**CVE-2021-42554**| Unknown \n**CVE-2021-43323**| Unknown \n**CVE-2021-43522**| Unknown \n**CVE-2021-43615**| Unknown \n**CVE-2021-45969**| Unknown \n**CVE-2021-45970**| Unknown \n**CVE-2021-45971**| Unknown \n**CVE-2022-24030**| Unknown \n**CVE-2022-24031**| Unknown \n**CVE-2022-24069**| Unknown \n**CVE-2022-28806**| Unknown \n \n#### Vendor Statement\n\nWe have not received a statement from the vendor.\n\n### VAIO Corporation Unknown\n\nNotified: 2022-01-26 Updated: 2022-02-01 **CVE-2020-27339**| Unknown \n---|--- \n**CVE-2020-5953**| Unknown \n**CVE-2021-33625**| Unknown \n**CVE-2021-33626**| Unknown \n**CVE-2021-33627**| Unknown \n**CVE-2021-41837**| Unknown \n**CVE-2021-41838**| Unknown \n**CVE-2021-41839**| Unknown \n**CVE-2021-41840**| Unknown \n**CVE-2021-41841**| Unknown \n**CVE-2021-42059**| Unknown \n**CVE-2021-42060**| Unknown \n**CVE-2021-42113**| Unknown \n**CVE-2021-42554**| Unknown \n**CVE-2021-43323**| Unknown \n**CVE-2021-43522**| Unknown \n**CVE-2021-43615**| Unknown \n**CVE-2021-45969**| Unknown \n**CVE-2021-45970**| Unknown \n**CVE-2021-45971**| Unknown \n**CVE-2022-24030**| Unknown \n**CVE-2022-24031**| Unknown \n**CVE-2022-24069**| Unknown \n**CVE-2022-28806**| Unknown \n \n#### Vendor Statement\n\nWe have not received a statement from the vendor.\n\n### Xerox Unknown\n\nNotified: 2022-01-26 Updated: 2022-02-01 **CVE-2020-27339**| Unknown \n---|--- \n**CVE-2020-5953**| Unknown \n**CVE-2021-33625**| Unknown \n**CVE-2021-33626**| Unknown \n**CVE-2021-33627**| Unknown \n**CVE-2021-41837**| Unknown \n**CVE-2021-41838**| Unknown \n**CVE-2021-41839**| Unknown \n**CVE-2021-41840**| Unknown \n**CVE-2021-41841**| Unknown \n**CVE-2021-42059**| Unknown \n**CVE-2021-42060**| Unknown \n**CVE-2021-42113**| Unknown \n**CVE-2021-42554**| Unknown \n**CVE-2021-43323**| Unknown \n**CVE-2021-43522**| Unknown \n**CVE-2021-43615**| Unknown \n**CVE-2021-45969**| Unknown \n**CVE-2021-45970**| Unknown \n**CVE-2021-45971**| Unknown \n**CVE-2022-24030**| Unknown \n**CVE-2022-24031**| Unknown \n**CVE-2022-24069**| Unknown \n**CVE-2022-28806**| Unknown \n \n#### Vendor Statement\n\nWe have not received a statement from the vendor.\n\nView all 29 vendors __View less vendors __\n\n \n\n\n### References\n\n * <https://www.insyde.com/security-pledge>\n * <https://github.com/binarly-io/Vulnerability-REsearch/tree/main/Insyde>\n * <https://github.com/binarly-io/Research_Publications/blob/main/OSFC_2021/The%20firmware%20supply-chain%20security%20is%20broken!%20Can%20we%20fix%20it%3F.pdf>\n * <https://www.microsoft.com/security/blog/2020/11/12/system-management-mode-deep-dive-how-smm-isolation-hardens-the-platform/>\n * <https://www.intel.com/content/www/us/en/developer/articles/technical/intel-sdm.html>\n\n### Other Information\n\n**CVE IDs:** | [CVE-2020-27339 ](<http://web.nvd.nist.gov/vuln/detail/CVE-2020-27339>) [CVE-2020-5953 ](<http://web.nvd.nist.gov/vuln/detail/CVE-2020-5953>) [CVE-2021-33625 ](<http://web.nvd.nist.gov/vuln/detail/CVE-2021-33625>) [CVE-2021-33626 ](<http://web.nvd.nist.gov/vuln/detail/CVE-2021-33626>) [CVE-2021-33627 ](<http://web.nvd.nist.gov/vuln/detail/CVE-2021-33627>) [CVE-2021-41837 ](<http://web.nvd.nist.gov/vuln/detail/CVE-2021-41837>) [CVE-2021-41838 ](<http://web.nvd.nist.gov/vuln/detail/CVE-2021-41838>) [CVE-2021-41839 ](<http://web.nvd.nist.gov/vuln/detail/CVE-2021-41839>) [CVE-2021-41840 ](<http://web.nvd.nist.gov/vuln/detail/CVE-2021-41840>) [CVE-2021-41841 ](<http://web.nvd.nist.gov/vuln/detail/CVE-2021-41841>) [CVE-2021-42059 ](<http://web.nvd.nist.gov/vuln/detail/CVE-2021-42059>) [CVE-2021-42060 ](<http://web.nvd.nist.gov/vuln/detail/CVE-2021-42060>) [CVE-2021-42113 ](<http://web.nvd.nist.gov/vuln/detail/CVE-2021-42113>) [CVE-2021-42554 ](<http://web.nvd.nist.gov/vuln/detail/CVE-2021-42554>) [CVE-2021-43323 ](<http://web.nvd.nist.gov/vuln/detail/CVE-2021-43323>) [CVE-2021-43522 ](<http://web.nvd.nist.gov/vuln/detail/CVE-2021-43522>) [CVE-2021-43615 ](<http://web.nvd.nist.gov/vuln/detail/CVE-2021-43615>) [CVE-2021-45969 ](<http://web.nvd.nist.gov/vuln/detail/CVE-2021-45969>) [CVE-2021-45970 ](<http://web.nvd.nist.gov/vuln/detail/CVE-2021-45970>) [CVE-2021-45971 ](<http://web.nvd.nist.gov/vuln/detail/CVE-2021-45971>) [CVE-2022-24030 ](<http://web.nvd.nist.gov/vuln/detail/CVE-2022-24030>) [CVE-2022-24031 ](<http://web.nvd.nist.gov/vuln/detail/CVE-2022-24031>) [CVE-2022-24069 ](<http://web.nvd.nist.gov/vuln/detail/CVE-2022-24069>) [CVE-2022-28806 ](<http://web.nvd.nist.gov/vuln/detail/CVE-2022-28806>) \n---|--- \n**API URL: ** | VINCE JSON | CSAF \n**Date Public:** | 2022-02-01 \n**Date First Published:** | 2022-02-01 \n**Date Last Updated: ** | 2023-07-17 14:56 UTC \n**Document Revision: ** | 15 \n", "cvss3": {"exploitabilityScore": 1.5, "cvssV3": {"baseSeverity": "HIGH", "confidentialityImpact": "HIGH", "attackComplexity": "LOW", "scope": "CHANGED", "attackVector": "LOCAL", "availabilityImpact": "HIGH", "integrityImpact": "HIGH", "privilegesRequired": "HIGH", "baseScore": 8.2, "vectorString": "CVSS:3.1/AV:L/AC:L/PR:H/UI:N/S:C/C:H/I:H/A:H", "version": "3.1", "userInteraction": "NONE"}, "impactScore": 6.0}, "published": "2022-02-01T00:00:00", "type": "cert", "title": "InsydeH2O UEFI software impacted by multiple vulnerabilities in SMM", "bulletinFamily": "info", "cvss2": {"severity": "HIGH", "exploitabilityScore": 3.9, "obtainAllPrivilege": false, "userInteractionRequired": false, "obtainOtherPrivilege": false, "cvssV2": {"accessComplexity": "LOW", "confidentialityImpact": "COMPLETE", "availabilityImpact": "COMPLETE", "integrityImpact": "COMPLETE", "baseScore": 7.2, "vectorString": "AV:L/AC:L/Au:N/C:C/I:C/A:C", "version": "2.0", "accessVector": "LOCAL", "authentication": "NONE"}, "impactScore": 10.0, "acInsufInfo": false, "obtainUserPrivilege": false}, "cvelist": ["CVE-2020-27339", "CVE-2020-5953", "CVE-2021-33625", "CVE-2021-33626", "CVE-2021-33627", "CVE-2021-41837", "CVE-2021-41838", "CVE-2021-41839", "CVE-2021-41840", "CVE-2021-41841", "CVE-2021-42059", "CVE-2021-42060", "CVE-2021-42113", "CVE-2021-42554", "CVE-2021-43323", "CVE-2021-43522", "CVE-2021-43615", "CVE-2021-45969", "CVE-2021-45970", "CVE-2021-45971", "CVE-2022-24030", "CVE-2022-24031", "CVE-2022-24069", "CVE-2022-28806"], "modified": "2023-07-17T14:56:00", "id": "VU:796611", "href": "https://www.kb.cert.org/vuls/id/796611", "cvss": {"score": 7.2, "vector": "AV:L/AC:L/Au:N/C:C/I:C/A:C"}}]}
CVE-2021-43615
