cve.bz

CVE-2022-37334 intel: Improper Initialization

7.8 highEPSS 0.2%Fix available

High (7.8) in intel. EPSS 0.2% estimated probability of exploitation activity in the next 30 days.

On this page
Improper initialization in BIOS firmware for some Intel(R) NUC 11 Pro Kits and Intel(R) NUC 11 Pro Boards before version TNTGL357.0064 may allow an authenticated user to potentially enable escalation of privilege via local access.

Severity

CVSS 3.1

7.8 high
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
EPSS
0.2% (unchanged from 0.2% a week ago; 0.2% 30 days ago) estimated probability of exploitation activity in the next 30 days; 7th percentile. Scored 2026-11-21. A forecast for this CVE across the internet, not for your own systems.
CISA's assessment (SSVC)
Exploitation: none · Automatable: no · Technical impact: total, assessed 2025-01-29. From CISA's Vulnrichment in the CVE List: whether it is exploited, whether exploiting it can be automated, and how much control it gives.
CWE
CWE-665 Improper Initialization
Published
Modified
NVD analysis
Analyzed, since modified
Record from
the NVD, synced

Fix and patched versions

Ask an AI about this CVE

Show the promptExplain CVE-2022-37334 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2022-37334?via=ask-ai-copy and https://cve.bz/cve/CVE-2022-37334?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2022-37334 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.

Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.

Affected

Versions

From the NVD's CPE matches.

ProductAffected
intel:nuc_11_pro_kit_nuc11tnhi70z_firmwarebefore tntgl357.0064
intel:nuc_11_pro_kit_nuc11tnki70z_firmwarebefore tntgl357.0064
intel:nuc_11_pro_kit_nuc11tnki30z_firmwarebefore tntgl357.0064
intel:nuc_11_pro_kit_nuc11tnhi30z_firmwarebefore tntgl357.0064
intel:nuc_11_pro_kit_nuc11tnki50z_firmwarebefore tntgl357.0064
intel:nuc_11_pro_kit_nuc11tnhi50z_firmwarebefore tntgl357.0064
intel:nuc_11_pro_board_nuc11tnbi30z_firmwarebefore tntgl357.0064
intel:nuc_11_pro_board_nuc11tnbi50z_firmwarebefore tntgl357.0064
intel:nuc_11_pro_board_nuc11tnbi70z_firmwarebefore tntgl357.0064
intel:nuc_11_pro_kit_nuc11tnhi3_firmwarebefore tntgl357.0064
intel:nuc_11_pro_kit_nuc11tnhi5_firmwarebefore tntgl357.0064

Attack patterns (CAPEC)

  • CAPEC-26 Leveraging Race Conditions Likelihood: High · Severity: High
  • CAPEC-29 Leveraging Time-of-Check and Time-of-Use (TOCTOU) Race Conditions Likelihood: High · Severity: High

The attack patterns MITRE's CAPEC relates to this record's weaknesses, as MITRE names them. Credits.

References

Check your stackJSON