CVE-2022-36339
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 · uneditedImproper input validation in firmware for Intel(R) NUC 8 Compute Element, Intel(R) NUC 11 Compute Element, Intel(R) NUC 12 Compute Element may allow a privileged user to enable escalation of privilege via local access.
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 confidenceThis is a firmware vulnerability in Intel NUC Compute Elements (8th, 11th, and 12th generations) caused by improper input validation. A privileged user with local access can exploit this to escalate their privileges on the affected system. The vulnerability exists in the firmware layer, making it a serious concern as firmware-level compromises can be difficult to detect and remediate.
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< cbwhl357.0101< cbwhl357.0101< cbwhl357.0101< cbwhl357.0101< cbwhl357.0101< ebtgl357.0071< ebtgl357.0071< ebtgl357.0071CVSS 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 the Intel NUC Compute Element modelLocate the model number printed on the physical device or check system documentation. The affected models are: Cm8i3cb4n, Cm8i5cb8n, Cm8i7cb8n, Cm8ccb4r, Cm8pcb4r, Cm11ebi38w, Cm11ebi58w, and Cm11ebi716w.Affected if The device is one of these eight Compute Element models.
-
Check the installed firmware versionEnter the BIOS/UEFI setup during boot (press F2) and navigate to the main or information page to view the firmware version. Alternatively, use Intel System Support Utility or the BIOS update utility to retrieve the current firmware version.Affected if The firmware version cannot be determined or is below the fixed versions.
-
Compare firmware version against affected rangesFor Cm8i3cb4n, Cm8i5cb8n, Cm8i7cb8n, Cm8ccb4r, Cm8pcb4r: compare your version to cbwhl357.0101. For Cm11ebi38w, Cm11ebi58w, Cm11ebi716w: compare your version to ebtgl357.0071. Note that version comparisons must account for the full version string.Affected if The firmware version is lower than cbwhl357.0101 (for cbwhl models) or lower than ebtgl357.0071 (for ebtgl models).
-
Verify local privileged access existsConfirm whether any local user accounts with administrative or elevated privileges exist on the system, as the vulnerability requires a privileged user to exploit it.Affected if Local privileged user accounts are present on the system.
You are affected if you own an Intel NUC Compute Element from the list and your installed firmware version is lower than cbwhl357.0101 or ebtgl357.0071 depending on the model.
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.
dbcve · scopedApply the latest Intel firmware updates for the affected NUC Compute Element models. Intel has released firmware updates to address this improper input validation vulnerability.
cbwhl357.0101 for Cm8 series (Cm8i3cb4n, Cm8i5cb8n, Cm8i7cb8n, Cm8ccb4r, Cm8pcb4r) and ebtgl357.0071 for Cm11 series (Cm11ebi38w, Cm11ebi58w, Cm11ebi716w)
- Identify the specific compute element model from the affected list (Cm8i3cb4n, Cm8i5cb8n, Cm8i7cb8n, Cm8ccb4r, Cm8pcb4r, Cm11ebi38w, Cm11ebi58w, or Cm11ebi716w)
- Visit the Intel support website (www.intel.com) and navigate to the drivers and support page for your specific NUC Compute Element
- Download the firmware update: For Cm8i3cb4n, Cm8i5cb8n, Cm8i7cb8n, Cm8ccb4r, Cm8pcb4r - download version cbwhl357.0101 or later
- Download the firmware update: For Cm11ebi38w, Cm11ebi58w, Cm11ebi716w - download version ebtgl357.0071 or later
- Follow Intel's documented firmware update procedure, which typically requires booting into the BIOS/UEFI or using Intel's firmware update utilities
- Apply the firmware update ensuring stable power throughout the process
- Reboot the system and verify the firmware version has been updated to the fixed release
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation8.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,880.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-36339 — 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-36339 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