AptioV: Time-of-check Time-of-use (TOCTOU) Race Condition
CVE-2024-42446 is a high-severity time-of-check time-of-use (TOCTOU) race condition vulnerability in AptioV from AMI, 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. Affected AptioV versions: BKS_5.0 through BKS_5.39. The record does not name a fixed version, so check the vendor advisory. There is no confirmed exploitation so far. EPSS estimates a 0.14% chance of exploitation within 30 days, which is low compared with other CVEs.
High severity with no evidence of exploitation so far.
What to do
- Update Aptio V to 5.039 or a later version.
- Read the advisory on go.ami.com for workarounds and exact fixed builds.
Affected products and versions
| Vendor | Product | Affected versions | Fixed in |
|---|---|---|---|
| AMI | AptioV | BKS_5.0 through BKS_5.39 | Not stated |
| Ami | Aptio V | 5.0 up to, but not including, 5.039 | 5.039 |
Version data comes from the organisation that assigned the CVE. 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 system | Score | Severity | Scored by |
|---|---|---|---|
| CVSS 3.1 | 7.5 | High | CNA (ami.com) |
| CVSS 3.1 | 7.0 | High | NVD |
Official description
APTIOV contains a vulnerability in BIOS where an attacker may cause a Time-of-check Time-of-use (TOCTOU) Race Condition by local means. Successful exploitation of this vulnerability may lead to arbitrary code execution.
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
- CVE record published.
- CISA published its SSVC assessment (exploitation: none, automatable: no, technical impact: total).
- Record last changed materially (score, affected products, status or references).
References
Other vulnerabilities in AptioV
- 8.3 High severity
- 7.1 High severity
- 8.2 High severity
- 7.1 High severity
- 8.7 High severity
- 8.8 High severity
Recent Time-of-check Time-of-use (TOCTOU) Race Condition vulnerabilities
- 7.5 High severity
- 7.5 High severity
- 7.0 High severity
- 7.0 High severity
- 7.0 High severity
- 7.5 High severity
Spotted an error? Tell us.