CVE-2022-36765
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 CreateHob() function, allowing a user to trigger a integer overflow to 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 UEFI firmware contains an integer overflow vulnerability in the CreateHob() function that can be triggered via a local network attack, leading to a buffer overflow. Successful exploitation allows an attacker to compromise confidentiality, integrity, and availability of the affected system.
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.
-
Identify EDK2-based UEFI firmwareCheck your system's BIOS/UEFI version information. EDK2 (Tianocore) is a UEFI firmware foundation used by many motherboard vendors. Access this via system setup (press Del/F2 during boot), dmidecode output (type 0), or vendor-specific tools like flashrom. Look for references to EDK2, Tianocore, or the vendor's UEFI version string.Affected if The system runs on UEFI firmware built using EDK2 as the underlying framework
-
Determine the firmware versionLocate the UEFI/BIOS version string in the firmware setup utility or system information tools. The version format varies by vendor but is typically displayed on the main BIOS screen or in the 'About' section of the UEFI setup.Affected if The installed firmware version is 202311 or earlier, or the version string cannot be determined but the firmware predates the CVE publication (2022)
-
Check for CreateHob function usageThis is an internal UEFI API function that creates Hand-Off Blocks (HOBs) during the DXE phase. In typical enterprise environments, this would require examining the firmware binary or contacting the vendor for specific vulnerability status. The function is invoked during early boot when the firmware constructs memory descriptors.Affected if The firmware uses EDK2 and executes the CreateHob function, which is standard in most EDK2-based implementations during the DXE boot phase
-
Verify network accessibility to the vulnerability vectorThe CVE description indicates the vulnerability can be triggered via local network attack. Check if the UEFI firmware has network stack components enabled (such as PXE boot, UEFI HTTP boot, or network management features) that could process network traffic during boot.Affected if UEFI network boot protocols or remote management features (like Intel AMT, PXE, or UEFI HTTP) are enabled and accessible on the local network
A system is affected if it uses EDK2-based UEFI firmware version 202311 or earlier, particularly with network boot or remote management features enabled, since the integer overflow in CreateHob() can be triggered during boot via network attack vectors.
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 patches or updates to EDK2 firmware that address the integer overflow vulnerability in CreateHob(); if no patch available, consider compensating controls such as network segmentation and restricting local access to trusted personnel.
- Consultation8.0 h
- Implementation24.0 h
- Testing16.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 $15,616.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-36765 — 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-36765 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