Safeguard
Vulnerability Analysis•

CVE-2022-36763: High Heap Overflow in EDK2 GPT Measuring

CVE-2022-36763 is a high (7.0) heap overflow in the EDK2 GPT measuring code, releases up to 202311. Apply the TianoCore patch or a vendor firmware update.

Safeguard Security Team
4 min read

CVE-2022-36763 is a high severity (CVSS 7.0) memory safety flaw in Tcg2MeasureGptTable() in TianoCore EDK2, the open source UEFI firmware base. EDK2 releases up to 202311 are affected and the advisory lists no patched release. Apply the vendor patch, or firmware updates from your hardware supplier.

What's affected

The TianoCore GitHub advisory lists the affected component as SecurityPkg in EDK2, affected versions up to and including 202311, and patched versions as None. It states that patch files are available through the TianoCore Bugzilla entry https://bugzilla.tianocore.org/show_bug.cgi?id=4117 and that the fix was planned for the February 2024 EDK2 release. I did not confirm that the release shipped, so check the current EDK2 tree and release notes.

The record scores the flaw 7.0 (High) with vector CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:C/C:L/I:L/A:H: local access, high complexity, low privileges, and a changed scope. The weakness classes are CWE-122 (Heap-based Buffer Overflow) and CWE-119 (Improper Restriction of Operations within the Bounds of a Memory Buffer).

EDK2 is a code base, not a product you install. It sits inside the firmware of many servers, laptops and virtual machine platforms, so the practical question is which firmware builds you run and whether your hardware vendor has merged the fix.

How to check if you're exposed

You will not find EDK2 in a package manager on most machines, so the check is about firmware and virtualization.

  1. List the hardware and virtual machine platforms in your fleet that boot through UEFI and use TPM measured boot.
  2. Ask each hardware vendor, or read its security bulletins, for the firmware version that includes the TianoCore fix for Bugzilla 4117.
  3. If you build your own firmware from EDK2, check whether your source tree includes the fix for Tcg2MeasureGptTable().

On a Linux host you can read the firmware version the machine reports, then compare it with your vendor's bulletin:

sudo dmidecode -s bios-version
sudo dmidecode -s bios-release-date

If you run virtual machines with OVMF, the EDK2 based firmware for QEMU and KVM, ask your distribution whether it has backported the fix. Distribution announcements for this CVE exist in the record's references, though I did not read them.

What to do now

  1. Inventory firmware and virtual machine firmware that is built on EDK2.
  2. Check vendor bulletins for a firmware update that includes the TianoCore fix referenced by Bugzilla 4117.
  3. If you maintain your own EDK2 build, apply the patch from the Bugzilla entry or move to an EDK2 release that includes it.
  4. Limit who can write to the EFI system partition and who can attach untrusted disks or images to machines that matter, since the input comes from disk.
  5. Re-check after your vendors publish firmware updates, and record the build you end up on.

Why it matters

The function reads a GPT partition table from disk and treats the contents as trustworthy. The advisory says the code does not check for integer overflow when it multiplies the number of partition entries by the size of each entry. A crafted table can make that multiplication wrap around, so the allocation comes out much smaller than the data later copied into it. The result is a heap buffer overflow.

The advisory is open about the stakes: it says the overflow could lead to arbitrary code execution during the DXE phase of boot, where memory is read, write and execute by default. That is firmware, below the operating system, which is why even a local, high complexity flaw gets a high score. The record's KEV flag is false and the advisory does not report exploitation. I will not describe the construction of such a table, since the advisory's level of detail is enough for defenders.

Quick check

Can this be exploited remotely?

The record's vector says local access with high complexity. The input is a partition table read from disk, so an attacker needs a way to present crafted storage to the machine.

Is there a patched release?

The advisory lists none, and points to patch files on Bugzilla with a planned February 2024 release. Confirm against current EDK2 releases.

Sources

Safeguard can help you see this across many sites or repositories at once. Paste a manifest into the free in-browser dependency scan at gold.safeguard.sh/scan or look the issue up in the Gold directory to see how the record is tracked.

Last reviewed: 19 October 2026.

Never miss an update

Weekly insights on software supply chain security, delivered to your inbox.

We email you a link to confirm, and only then add you to the list. Unsubscribe in one click. Privacy

Self-healing security runs on Safeguard.

Your first fix PR is minutes away.

No sales call required, even your agent can complete the purchase over MCP.