dbcve.org
Aptio V Uefi Firmware Integrator ToolsApplication · Intel

CVE-2022-36374

MEDIUM · 6.7 CVSS v3.1 Published 2023-11-14
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
69/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
Improper access control in some Intel(R) Aptio* V UEFI Firmware Integrator Tools before version iDmi Windows 5.27.03.0003 may allow a privileged 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 in Intel Aptio V UEFI Firmware Integrator Tools allows a privileged local user to escalate privileges further. The vulnerability exists in versions prior to iDmi Windows 5.27.03.0003 and requires local access to the system.

MitigationUpdate Intel Aptio V UEFI Firmware Integrator Tools to version iDmi Windows 5.27.03.0003 or later. Apply through standard Intel firmware update processes after testing in a controlled environment.

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.27.03.0003= 5.27.06.0017

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

CVSS:3.1/AV:L/AC:L/PR:H/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 installed Intel Aptio V Firmware Integrator Tools version
    Check the program's version information through the Windows Add/Remove Programs list, or locate the iDmi executable (typically in C:\Program Files\Intel\ or the installation directory) and view its file properties for the version number
    Affected if The installed version is 5.27.03.0003 or 5.27.06.0017, or falls between these versions (prior to the fixed release)
  2. Confirm iDmi Windows component is present
    Look for the iDmi executable or Windows service component that is part of the Intel Aptio V UEFI Firmware Integrator Tools installation
    Affected if The iDmi Windows component is installed on the system
  3. Verify local user access level
    Check if the user checking the system has privileged local access (administrator or elevated privileges)
    Affected if The user has privileged local access to the system where the affected software is installed

A system is affected if it has Intel Aptio V UEFI Firmware Integrator Tools with iDmi Windows component installed at versions 5.27.03.0003 or 5.27.06.0017 (or any version prior to the fixed release), and the user has local privileged access to that 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
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Update Intel Aptio V UEFI Firmware Integrator Tools to version iDmi Windows 5.27.03.0003 or later. Apply through standard Intel firmware update processes after testing in a controlled environment.

Recommended fix Moderate confidence

iDmi Windows version later than 5.27.03.0003 (consult Intel for exact latest fixed version)

  1. 1. Visit Intel's official security advisory page for Intel Aptio V UEFI Firmware Integrator Tools to obtain the latest fixed version.
  2. 2. Identify the current version of Intel Aptio V UEFI Firmware Integrator Tools installed in your environment.
  3. 3. If the current version is 5.27.03.0003 or earlier, or 5.27.06.0017, download and install the fixed version from Intel's support website.
  4. 4. After installation, verify the version to confirm the patch was successfully applied.
  5. 5. Review Intel's release notes for any additional configuration or post-installation steps required.
Caveat Review Intel's documentation for any firmware compatibility or configuration changes required after the update

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
  • Consultation6.0 h
  • Implementation12.0 h
  • Testing8.0 h
  • Review / QA4.0 h
30.0 hours of engineering $5,280
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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