Nuc 11 Compute Element Cm11ebi38w FirmwareOperating system · Intel

CVE-2022-38099

HIGH · 7.8 CVSS v3.1 Published 2022-11-11
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
80/100
Remediation priority · High
Zero-click

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 · unedited
Improper input validation in BIOS firmware for some Intel(R) NUC 11 Compute Elements before version EBTGL357.0065 may allow a privileged user to potentially 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 · high confidence

Improper input validation in the BIOS firmware of Intel NUC 11 Compute Elements allows a privileged local user to potentially escalate privileges. The vulnerability exists in versions prior to EBTGL357.0065 and stems from insufficient validation of input within the BIOS environment.

MitigationUpdate BIOS firmware to version EBTGL357.0065 or later on all affected Intel NUC 11 Compute Elements.

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
Nuc 11 Compute Element Cm11ebi38w FirmwareOperating system
Affected:< ebtgl357.0065
Nuc 11 Compute Element Cm11ebc4w FirmwareOperating system
Affected:< ebtgl357.0065
Nuc 11 Compute Element Cm11ebi58w FirmwareOperating system
Affected:< ebtgl357.0065
Nuc 11 Compute Element Cm11ebv58w FirmwareOperating system
Affected:< ebtgl357.0065
Nuc 11 Compute Element Cm11ebi716w FirmwareOperating system
Affected:< ebtgl357.0065
Nuc 11 Compute Element Cm11ebv716w FirmwareOperating system
Affected:< ebtgl357.0065
Nuc11dbbi9 FirmwareOperating system
Affected:< ebtgl357.0065
Nuc11dbbi7 FirmwareOperating system
Affected:< ebtgl357.0065

CVSS 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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify the NUC model
    Check the product label on the device or use system information tools (such as dmidecode -s system-product-name or Intel System Discovery) to determine the exact model number
    Affected if The model is not one of the listed affected products (Cm11ebi38w, Cm11ebc4w, Cm11ebi58w, Cm11ebv58w, Cm11ebi716w, Cm11ebv716w, Nuc11dbbi9, Nuc11dbbi7)
  2. Retrieve the current BIOS version
    Enter the BIOS setup (press F2 during boot) and navigate to the Main or Information page, or use the command 'dmidecode -s bios-version' in Linux, or check via Intel Platform Flash Tool or Intel NUC Software Studio
    Affected if Unable to retrieve a BIOS version (firmware may be corrupted or inaccessible)
  3. Compare the BIOS version against the fixed version
    Check if the installed BIOS version string is lower than EBTGL357.0065. Note that version strings may appear as ebtgl357.0065 or similar formats
    Affected if The installed BIOS version is any version prior to EBTGL357.0065 (for example, ebtgl357.0042, ebtgl357.0050, or earlier)
  4. Verify the BIOS is the original vendor firmware
    Confirm the BIOS was not modified or downgraded from a later patched version. Check the BIOS build date in the BIOS setup Information page
    Affected if The BIOS has been rolled back to a version earlier than EBTGL357.0065 after a patch was applied

The system is affected if it is an Intel NUC 11 Compute Element (Cm11ebi38w, Cm11ebc4w, Cm11ebi58w, Cm11ebv58w, Cm11ebi716w, Cm11ebv716w) or NUC11dbbi9/7 and the installed BIOS version is earlier than EBTGL357.0065

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Update BIOS firmware to version EBTGL357.0065 or later on all affected Intel NUC 11 Compute Elements.

Recommended fix High confidence

EBTGL357.0065

  1. Identify your exact NUC 11 model number (e.g., Cm11ebi38w, Nuc11dbbi9, etc.)
  2. Visit Intel's support website and search for your specific NUC model
  3. Download the BIOS firmware update package version EBTGL357.0065 or later
  4. Extract the downloaded BIOS update files to a USB flash drive
  5. Connect the USB drive to the NUC 11 device
  6. Restart the NUC and enter the BIOS setup (typically by pressing F2 during boot)
  7. Navigate to the BIOS update/flash utility (often under 'Security' or 'Advanced' menu)
  8. Select the BIOS update file from the USB drive and initiate the update
Caveat BIOS firmware updates carry risk of permanent damage if interrupted; ensure stable power and do not interrupt the flashing process

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Nuc 11 Compute Element Cm11ebi38w Firmware Scoped from the published advisory
  • Consultation4.0 h
  • Implementation6.0 h
  • Testing4.0 h
  • Review / QA2.0 h
16.0 hours of engineering $2,840
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,544.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2022-38099 — 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 sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2022-38099 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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