CVE-2024-13745 is a flaw in EDK II’s GPT measurement and parsing logic that allows the GUID Partition Table layout or metadata actually used by firmware to differ from what is measured into TPM PCR[5]. According to the disclosure, affected versions include EDK II releases up to and including edk2-stable202411, and later versions may also be affected because no fix was known at disclosure time. The issue arises from inconsistencies between DxeTpm2MeasureBootLib, which measures GPT data for TPM event logging, and PartitionDxe, which parses, validates, and may recover GPT structures for actual use. DxeTpm2MeasureBootLib reads the GPT header from LBA 1, applies comparatively relaxed validation, does not validate CRC32 checksums, does not consult the backup GPT header, and omits unused GPT partition entries from the measured structure. PartitionDxe, by contrast, performs stricter validation, reads both primary and backup GPT headers, and includes recovery logic. The disclosure further describes error-handling flaws in PartitionRestoreGptTable() and PartitionValidGptTable() where failures can leave PrimaryHeader populated with untrusted invalid data while execution continues down a path treating both GPT tables as valid. An attacker can exploit these discrepancies by preserving the GPT data that DxeTpm2MeasureBootLib measures while causing PartitionDxe to recover or use a different GPT header and partition entry array, including via malformed backup GPT headers and attacker-controlled AlternateLBA values. The result is a data-only integrity failure in which PCR[5] and TPM event logs can indicate an expected GPT state while firmware and the operating system use attacker-influenced partition layout or metadata.
Mallory correlates every CVE against your assets, your vendors, and active adversary campaigns. Know which vulnerabilities matter for you, not just which ones are loud.
What it means. What to do now. Patch path, mitigations, and the assume-compromise checklist.
What an attacker gets, and what they’ve been doing with it.
If you can’t patch tonight, do this now.
Patch, then assume compromise.
No public exploits tracked yet. Mallory keeps watching.
No public exploit code observed for this vulnerability.
3 sources tracked across advisories and community write-ups. News coverage will land here when it surfaces.
No news coverage yet. Advisories and community discussion only.
Query your assets running an affected version, and investigate the blast radius.
Every observed campaign linking this CVE to a named adversary.
Malware families riding this exploit, with evidence and IOCs.
YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Cross-references every affected SKU, including bundled OEM variants.
Community discussion across Reddit, Mastodon, and other social sources.