CyberSecBulletin
CVE-2022-32471NVD status: Modified

Insydeh2o: Time-of-check Time-of-use (TOCTOU) Race Condition

Published Updated By the CyberSecBulletin desk

CVE-2022-32471 is a high-severity time-of-check time-of-use (TOCTOU) race condition vulnerability in Insydeh2o from Insyde, with a CVSS 3.1 base score of 7.0 out of 10. It can be exploited with local access to the system by an attacker with a low-privileged account, without any action from a user. The record lists versions 5.2.05.27.37, 5.3.05.36.37, 5.4.05.44.45 as the first without the flaw, so updating Insydeh2o to one of those releases or later removes the exposure. There is no confirmed exploitation so far. EPSS estimates a 0.13% chance of exploitation within 30 days, which is low compared with other CVEs.

Next patch cycle

High severity with no evidence of exploitation so far.

What to do

  1. Update Insydeh2o to 5.2.05.27.37 or 5.3.05.36.37 or 5.4.05.44.45 or 5.5.05.52.45, whichever matches your release line, or a later version.
  2. Read the advisory on insyde.com for workarounds and exact fixed builds.

Affected products and versions

VendorProductAffected versionsFixed in
InsydeInsydeh2o5.0 up to, but not including, 5.2.05.27.37; 5.3 up to, but not including, 5.3.05.36.37; 5.4 up to, but not including, 5.4.05.44.45; 5.5 up to, but not including, 5.5.05.52.455.2.05.27.37, 5.3.05.36.37, 5.4.05.44.45, 5.5.05.52.45

Version data comes from NVD's product matching. Confirm against the vendor advisory before deciding you are unaffected.

How the severity score breaks down

Attack vector
LocalThe attacker needs local access or must trick a user into running something.
Attack complexity
HighSuccess depends on conditions outside the attacker's control.
Privileges required
LowA basic user account is enough.
User interaction
NoneNo action by a victim is required.
Scope
UnchangedImpact stays within the vulnerable component.
Confidentiality
HighAll data handled by the component can be read.
Integrity
HighData or code can be modified at will.
Availability
HighThe component can be taken down completely.

Vector: CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H. Scored by NVD.

Scoring systemScoreSeverityScored by
CVSS 3.17.0HighNVD
CVSS 3.17.0HighCISA (ADP)

Official description

An issue was discovered in IhisiSmm in Insyde InsydeH2O with kernel 5.0 through 5.5. The IhisiDxe driver uses the command buffer to pass input and output data. By modifying the command buffer contents with DMA after the input parameters have been checked but before they are used, the IHISI SMM code may be convinced to modify SMRAM or OS, leading to possible data corruption or escalation of privileges.

Source: the CVE record as published by its numbering authority, via NVD and CVE.org.

The underlying weakness: Time-of-check Time-of-use (TOCTOU) Race Condition

The product checks the state of a resource before using that resource, but the resource's state can change between the check and the use in a way that invalidates the results of the check.

How developers prevent this class of flaw

  • The most basic advice for TOCTOU vulnerabilities is to not perform a check before the use. This does not resolve the underlying issue of the execution of a function on a resource whose state and identity cannot be assured, but it does help to limit the false sense of security given by the check.
  • When the file being altered is owned by the current user and group, set the effective gid and uid to that of the current user and group when executing this statement.
  • Limit the interleaving of operations on files from multiple processes.

More Time-of-check Time-of-use (TOCTOU) Race Condition vulnerabilities (CWE-367)

Timeline

  1. CVE record published.
  2. CISA published its SSVC assessment (exploitation: none, automatable: no, technical impact: total).
  3. Record last changed materially (score, affected products, status or references).

References

Other vulnerabilities in Insydeh2o

All Insydeh2o vulnerabilities

Recent Time-of-check Time-of-use (TOCTOU) Race Condition vulnerabilities

Spotted an error? Tell us.