dbcve.org
Edk2Application · Tianocore

CVE-2022-36763

HIGH · 7.8 CVSS v3.1 Published 2024-01-09
Fix available
A fix is available. Upgrade to after 202311 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
EDK2 is susceptible to a vulnerability in the Tcg2MeasureGptTable() function, allowing a user to trigger a heap buffer overflow via a local network. Successful exploitation of this vulnerability may result in a compromise of confidentiality, integrity, and/or availability.

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

EDK2 contains a heap buffer overflow vulnerability in the Tcg2MeasureGptTable() function, which is responsible for measuring GPT (GUID Partition Table) entries into the TPM (Trusted Platform Module). The overflow occurs during GPT table measurement, allowing an attacker with local access to corrupt heap memory and potentially execute arbitrary code within the UEFI firmware context.

MitigationApply vendor-supplied UEFI firmware updates that include the patched EDK2 version. If using custom EDK2 builds, locate and fix the heap buffer overflow in Tcg2MeasureGptTable() by adding proper bounds checking before copying GPT entries to the heap buffer, then rebuild and re-sign the firmware.

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
Edk2Application
Affected:<= 202311

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. Verify TPM is enabled in UEFI/BIOS
    Enter system UEFI/BIOS setup and navigate to Security or Trusted Computing settings. Check if 'TPM', 'TPM 2.0', or 'Trusted Platform Module' is enabled. Alternatively, run 'tpm2_getcap -c properties-fixed' on Linux if TPM is accessible at OS level.
    Affected if TPM is enabled - the vulnerable Tcg2MeasureGptTable() code path executes during boot when TPM measurement of GPT entries is active.
  2. Confirm GPT measurement feature is active
    Check if the system measures GPT partitions into TPM during boot. On Linux, inspect TPM event logs at /sys/kernel/security/tpm0/binary_bios_measurements (or tpm1) for GPT-related entries. Look for event types related to GPT or partition tables.
    Affected if GPT measurement events exist in TPM logs - this confirms the vulnerable code path was executed during boot.
  3. Identify installed UEFI firmware version
    Retrieve the UEFI/BIOS firmware version from system. On Linux, run 'dmidecode -s bios-version' or check /sys/class/dmi/id/bios_version. On Windows, run 'wmic bios get smbiosbiosversion'. Note that vendor firmware versions do not directly map to EDK2 versions.
    Affected if The installed UEFI firmware version is from a vendor that uses EDK2 and the version corresponds to Edk2 <= 202311.
  4. Determine if firmware uses EDK2 codebase
    Check vendor documentation or release notes for the system/firmware. Some vendors explicitly state they use Tianocore EDK2. If custom firmware is in use, inspect the firmware image for EDK2-specific modules or strings referencing 'Tcg2MeasureGptTable'.
    Affected if The system firmware is confirmed to be built from the Tianocore EDK2 codebase.

A system is affected if it uses EDK2-based UEFI firmware version 202311 or earlier, has TPM enabled, and has GPT measurement active - the overflow only occurs when Tcg2MeasureGptTable() executes during boot.

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.

From vendor data
Upgrade available Upgrade to a release after 202311
Interim mitigation

Apply vendor-supplied UEFI firmware updates that include the patched EDK2 version. If using custom EDK2 builds, locate and fix the heap buffer overflow in Tcg2MeasureGptTable() by adding proper bounds checking before copying GPT entries to the heap buffer, then rebuild and re-sign the firmware.

Fix this in Edk2 Scoped from the published advisory
  • Consultation8.0 h
  • Implementation16.0 h
  • Testing16.0 h
  • Review / QA8.0 h
48.0 hours of engineering $8,320
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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