dbcve.org
Aptio VOperating system · Ami

CVE-2024-42446

HIGH · 7.0 CVSS v3.1 Published 2025-05-13
Fix available
A fix is available. Upgrade to 5.039 or later.
See remediation →
72/100
Remediation priority · Elevated
Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

APTIOV BIOS firmware contains a Time-of-check Time-of-use (TOCTOU) race condition vulnerability that can be exploited by a local attacker. The race condition allows manipulation of system state between a security check and the use of that check's result, enabling arbitrary code execution with the privileges of the BIOS context.

MitigationApply vendor-supplied BIOS/firmware updates from AMI/APTIOV. This is a firmware-level vulnerability requiring a patch and subsequent BIOS update deployment across affected systems.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Aptio VOperating system
Affected:>= 5.0, < 5.039

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Local
Complexity
High
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify BIOS vendor and firmware version
    On Linux, run 'dmidecode -s bios-version' or 'dmidecode | grep -A3 "BIOS Information"'. On Windows, run 'wmic bios get smbiosbiosversion' or check in System Information (msinfo32). On UEFI systems, check 'fwupdtool get-devices' if available.
    Affected if The BIOS vendor is AMI/AptioV and the version is 5.0 or higher but below 5.039
  2. Confirm BIOS is Ami Aptio V product line
    Check BIOS vendor string: On Linux 'dmidecode -s bios-vendor', on Windows 'wmic bios get manufacturer'. Look for 'American Megatrends' (AMI) or 'AMI' in the vendor information.
    Affected if Vendor string shows American Megatrends (AMI) or specifically mentions AptioV
  3. Compare installed version to affected range
    Parse the version number obtained in step 1. The affected range is versions >= 5.0.0 and < 5.039.0. For example, versions 5.0, 5.01, 5.02, 5.030, 5.038 would all be vulnerable. Versions 5.039 and above are patched.
    Affected if Installed version starts with 5.0, 5.01, 5.02, 5.03x (where x < 9), or any 5.0.x version less than 5.039

If the system uses Ami Aptio V BIOS firmware version 5.0 through 5.038.x, it is vulnerable to this TOCTOU race condition that could allow arbitrary code execution in BIOS context.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 5.039 or later
Fixed in 5.039
Interim mitigation

Apply vendor-supplied BIOS/firmware updates from AMI/APTIOV. This is a firmware-level vulnerability requiring a patch and subsequent BIOS update deployment across affected systems.

Recommended fix Moderate confidence

Aptio V version 5.039 or later

  1. Obtain the fixed Aptio V BIOS/firmware version 5.039 or later from the motherboard or system vendor (go.ami.com references AMI's security advisories)
  2. Verify the integrity of the downloaded firmware image using checksums provided by the vendor
  3. Follow the vendor's standard BIOS/UEFI firmware update procedure - typically requires booting into the firmware update utility or using vendor-specific flashing tools
  4. Restart the system to complete the firmware update process
  5. After update, verify the BIOS version reflects 5.039 or later to confirm the patch was applied
Caveat BIOS firmware updates carry inherent risks; ensure power stability during flashing and have a backup recovery plan

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Aptio V Scoped from the published advisory
  • Consultation8.0 h
  • Implementation24.0 h
  • Testing12.0 h
  • Review / QA8.0 h
52.0 hours of engineering $9,160
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $14,656.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-42446 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2024-42446 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data