What is the vulnerability ID for this issue in Insyde InsydeH2O?

The vulnerability ID for this issue in Insyde InsydeH2O is CVE-2022-32477.

What is the severity level of CVE-2022-32477?

CVE-2022-32477 has a severity level of high.

What is the affected software version range for CVE-2022-32477?

CVE-2022-32477 affects Insyde InsydeH2O versions 5.0 through 5.5.

How can I mitigate the vulnerability in CVE-2022-32477?

To mitigate the vulnerability in CVE-2022-32477, it is recommended to follow the security guidelines provided by Insyde, including updating to the latest version of Insyde InsydeH2O.

Where can I find more information about CVE-2022-32477?

More information about CVE-2022-32477 can be found on the Insyde website: [https://www.insyde.com/security-pledge](https://www.insyde.com/security-pledge)

Vulnerability/
CVE-2022-32477

high

CWE

367

15/2/2023

3/8/2024

CVE-2022-32477

First published: Wed Feb 15 2023(Updated: )

An issue was discovered in Insyde InsydeH2O with kernel 5.0 through 5.5. DMA attacks on the FvbServicesRuntimeDxe shared buffer used by SMM and non-SMM code could cause TOCTOU race-condition issues that could lead to corruption of SMRAM and escalation of privileges. This attack can be mitigated using IOMMU protection for the ACPI runtime memory used for the command buffer. This attack can be mitigated by copying the firmware block services data to SMRAM before checking it.

Credit: cve@mitre.org

Affected Software	Affected Version	How to fix
Insyde InsydeH2O	>=5.0<5.2.05.27.27
Insyde InsydeH2O	>=5.3<5.3.05.36.27
Insyde InsydeH2O	>=5.4<5.4.05.44.27
Insyde InsydeH2O	>=5.5<5.5.05.52.27

Never miss a vulnerability like this again

Reference Links

Frequently Asked Questions

What is the vulnerability ID for this issue in Insyde InsydeH2O?
The vulnerability ID for this issue in Insyde InsydeH2O is CVE-2022-32477.
What is the severity level of CVE-2022-32477?
CVE-2022-32477 has a severity level of high.
What is the affected software version range for CVE-2022-32477?
CVE-2022-32477 affects Insyde InsydeH2O versions 5.0 through 5.5.
How can I mitigate the vulnerability in CVE-2022-32477?
To mitigate the vulnerability in CVE-2022-32477, it is recommended to follow the security guidelines provided by Insyde, including updating to the latest version of Insyde InsydeH2O.
Where can I find more information about CVE-2022-32477?
More information about CVE-2022-32477 can be found on the Insyde website: [https://www.insyde.com/security-pledge](https://www.insyde.com/security-pledge)

collector/nvd-index
agent/references
agent/weakness
agent/severity
agent/author
agent/type
agent/event
agent/description
agent/softwarecombine
agent/first-publish-date
agent/last-modified-date
agent/tags
collector/mitre-cve
source/MITRE
vendor/insyde
canonical/insyde insydeh2o
version/insyde insydeh2o/5.0
version/insyde insydeh2o/5.3
version/insyde insydeh2o/5.4
version/insyde insydeh2o/5.5

Company

Resources

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co

By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.