dbcve.org
Aptio V Uefi Firmware Integrator ToolsApplication · Intel

CVE-2024-26022

HIGH · 7.8 CVSS v3.1 Published 2024-08-14
Fix available
A fix is available. Upgrade to 5.05.04.0008 / 5.13.00.2106 or later.
See remediation →
80/100
Remediation priority · High
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
Improper access control in some Intel(R) UEFI Integrator Tools on Aptio V for Intel(R) NUC may allow an authenticated user to potentially enable escalation of privilege via local access.

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 · moderate confidence

Improper access control vulnerability in Intel UEFI Integrator Tools on Aptio V firmware for Intel NUC allows an authenticated local user to potentially escalate privileges by exploiting insufficient permission controls in the UEFI environment.

MitigationApply available Intel firmware updates for the affected NUC systems; verify that only authorized personnel have access to UEFI configuration and that local user privileges are appropriately restricted.

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 V Uefi Firmware Integrator ToolsApplication
Affected:< 5.05.04.0008< 5.13.00.2106< 5.13.00.2109< 5.27.06.0019

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
Low
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:L/AC:L/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. Confirm Intel NUC system
    Check that the system is an Intel NUC (Next Unit of Computing) by examining system information via `lspci` on Linux or `systeminfo` on Windows, or physically inspecting the device label
    Affected if System is not an Intel NUC - this CVE applies specifically to Intel NUC devices with Aptio V firmware
  2. Identify UEFI firmware version
    Access UEFI/BIOS setup during boot (press F2) and navigate to the main or information page to read the firmware version, or use command-line tools: Linux: `sudo dmidecode -s bios-version`; Windows: `wmic bios get smbiosbiosversion`
    Affected if Unable to retrieve or confirm the UEFI firmware version
  3. Compare version against affected ranges
    Compare your installed firmware version to all four affected ranges: versions below 5.05.04.0008, 5.13.00.2106, 5.13.00.2109, or 5.27.06.0019 are vulnerable
    Affected if The installed firmware version falls below any of these four version thresholds (any version less than 5.27.06.0019 is affected if it does not meet the other three thresholds)
  4. Verify local user access exists
    Confirm that local user accounts exist on the system (Linux: `cat /etc/passwd`; Windows: `net user`) and that untrusted or low-privilege local users have access to the system
    Affected if Untrusted local users have access to the system - the vulnerability requires an authenticated local user to exploit the insufficient permission controls in the UEFI environment

You are affected if you are running an Intel NUC with Aptio V UEFI firmware version lower than 5.27.06.0018 (or any version below 5.05.04.0008, 5.13.00.2106, or 5.13.00.2109), and untrusted local users can access the system.

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.05.04.0008 / 5.13.00.2106 / 5.13.00.2109 or later
Fixed in 5.05.04.00085.13.00.21065.13.00.2109
Interim mitigation

Apply available Intel firmware updates for the affected NUC systems; verify that only authorized personnel have access to UEFI configuration and that local user privileges are appropriately restricted.

Recommended fix Moderate confidence

Upgrade to Intel Aptio V UEFI Firmware Integrator Tools version 5.05.04.0008 or later (for 5.05.x branch), 5.13.00.2106 or later (for 5.13.x branch), or 5.27.06.0019 or later (for 5.27.x branch)

  1. 1. Identify the current installed version of Intel(R) Aptio V UEFI Firmware Integrator Tools by checking the software documentation or program properties
  2. 2. Determine which version branch (5.05.x, 5.13.x, or 5.27.x) is currently in use
  3. 3. Navigate to the official Intel support website or Intel Security Advisory for CVE-2024-26022
  4. 4. Download the appropriate fixed version of the UEFI Integrator Tools for the identified branch: version 5.05.04.0008 or later for 5.05.x branch, version 5.13.00.2106 or later for 5.13.x branch, or version 5.27.06.0019 or later for 5.27.x branch
  5. 5. Back up all current UEFI configuration settings and firmware configurations before applying the update
  6. 6. Apply the update following the documented firmware update procedures specific to the Intel NUC platform
  7. 7. Verify the installed version matches the expected fixed version after update completion
Caveat UEFI firmware updates carry inherent risks; ensure proper backups and follow Intel's update procedures to avoid rendering the system non-functional

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

Fix this in Aptio V Uefi Firmware Integrator Tools Scoped from the published advisory
  • Consultation3.0 h
  • Implementation4.0 h
  • Testing2.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,980
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-26022 — 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-26022 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