CVE-2022-36764
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 · uneditedEDK2 is susceptible to a vulnerability in the Tcg2MeasurePeImage() 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 confidenceEDK2 contains a heap buffer overflow vulnerability in the Tcg2MeasurePeImage() function, which measures PE (Portable Executable) images into the Trusted Platform Module (TPM) during the boot process. The overflow allows writing beyond allocated heap buffer bounds, potentially enabling code execution or memory corruption.
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<= 202311CVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Check if TPM 2.0 is present and enabledOn Linux, run 'ls /dev/tpm*' or 'tpm2_getcap -l' to list available TPM devices. On Windows, check Device Manager under Security Devices for TPM 2.0 status.Affected if No TPM device is found - the vulnerability requires TPM 2.0 to be present and accessible for the Tcg2MeasurePeImage function to execute during boot.
-
Verify TCG2 measurement feature is activeOn Linux, check UEFI boot variables by running 'efivar -l' or inspecting /sys/firmware/efi/efivars/ for TCG2-related variables. Look for variables starting with 'Tcg2' or 'TCG2' that indicate active measurement.Affected if TCG2 measurement is disabled - the vulnerability only applies when the Tcg2MeasurePeImage function is called to measure PE images into TPM during the boot process.
-
Identify the EDK2-based firmware versionOn Linux, run 'dmidecode -s bios-version' or check '/sys/class/dmi/id/bios_version'. For UEFI systems, use 'efivar -d 8be4df61-93ca-11d2-aa0d-00e09832b8cd' to read the firmware vendor version if available.Affected if The installed firmware version corresponds to EDK2 build 202311 or earlier, as this is the vulnerable version range for the Tcg2MeasurePeImage heap overflow.
-
Confirm the system uses EDK2 firmwareCheck the firmware vendor string by running 'dmidecode -s bios-vendor' or inspecting '/sys/class/dmi/id/bios_vendor'. EDK2-based firmware may appear as 'EDK2', 'UEFI', 'American Megatrends', or other vendors using EDK2 as their UEFI foundation.Affected if The firmware is not based on EDK2 - the vulnerability is specific to the Tianocore EDK2 codebase and does not affect other UEFI implementations.
A system is affected if it uses EDK2-based firmware version 202311 or earlier, has TPM 2.0 enabled, and has TCG2 PE image measurement active during boot.
Generated from the published advisory. Verify against your own configuration.
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 dataApply vendor firmware updates containing the EDK2 patch; until then, restrict network access to affected systems and validate firmware integrity before deployment.
- Consultation6.0 h
- Implementation16.0 h
- Testing12.0 h
- Review / QA8.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $11,712.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-36764 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2022-36764 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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