cve.bz

CVE-2022-36789 intel: Improper Access Control

7.8 highEPSS 0.2%

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

On this page
Improper access control in BIOS firmware for some Intel(R) NUC 10 Performance Kits and Intel(R) NUC 10 Performance Mini PCs before version FNCML357.0053 may allow a privileged 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; 8th 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-284 Improper Access Control
OWASP Top 10
A01:2025 Broken Access Control
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-36789 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2022-36789?via=ask-ai-copy and https://cve.bz/cve/CVE-2022-36789?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-36789 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_10_performance_kit_nuc10i7fnhn_firmwarebefore fncml357.0053
intel:nuc_10_performance_kit_nuc10i5fnkn_firmwarebefore fncml357.0053
intel:nuc_10_performance_kit_nuc10i5fnhn_firmwarebefore fncml357.0053
intel:nuc_10_performance_kit_nuc10i7fnkn_firmwarebefore fncml357.0053
intel:nuc_10_performance_kit_nuc10i3fnhn_firmwarebefore fncml357.0053
intel:nuc_10_performance_kit_nuc10i3fnkn_firmwarebefore fncml357.0053
intel:nuc_10_performance_mini_pc_nuc10i5fnhja_firmwarebefore fncml357.0053
intel:nuc_10_performance_kit_nuc10i3fnhf_firmwarebefore fncml357.0053
intel:nuc_10_performance_mini_pc_nuc10i5fnhca_firmwarebefore fncml357.0053
intel:nuc_10_performance_mini_pc_nuc10i3fnhfa_firmwarebefore fncml357.0053
intel:nuc_10_performance_kit_nuc10i5fnhj_firmwarebefore fncml357.0053
intel:nuc_10_performance_kit_nuc10i7fnhc_firmwarebefore fncml357.0053
intel:nuc_10_performance_mini_pc_nuc10i7fnhja_firmwarebefore fncml357.0053
intel:nuc_10_performance_mini_pc_nuc10i3fnhja_firmwarebefore fncml357.0053
intel:nuc_10_performance_kit_nuc10i3fnk_firmwarebefore fncml357.0053
intel:nuc_10_performance_mini_pc_nuc10i7fnhaa_firmwarebefore fncml357.0053
intel:nuc_10_performance_kit_nuc10i5fnh_firmwarebefore fncml357.0053
intel:nuc_10_performance_kit_nuc10i5fnk_firmwarebefore fncml357.0053
intel:nuc_10_performance_kit_nuc10i7fnh_firmwarebefore fncml357.0053
intel:nuc_10_performance_kit_nuc10i5fnhf_firmwarebefore fncml357.0053
intel:nuc_10_performance_mini_pc_nuc10i7fnkpa_firmwarebefore fncml357.0053
intel:nuc_10_performance_mini_pc_nuc10i5fnkpa_firmwarebefore fncml357.0053
intel:nuc_10_performance_kit_nuc10i3fnh_firmwarebefore fncml357.0053
intel:nuc_10_performance_kit_nuc10i7fnk_firmwarebefore fncml357.0053
intel:nuc_10_performance_kit_nuc10i7fnkp_firmwarebefore fncml357.0053
intel:nuc_10_performance_kit_nuc10i5fnkp_firmwarebefore fncml357.0053

Attack patterns (CAPEC)

The attack patterns MITRE's CAPEC relates to this record's weaknesses, as MITRE names them. Credits. More on the page of CWE-284 (17).

References

Check your stackJSON