Improper access control in firmware for some Intel(R) NUC Boards, Intel(R) NUC 11 Performance Kit, Intel(R) NUC 11 Performance Mini PC, Inte
Noroxi assessment
Priority: Monitor (action score 17/100)
- The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
- Probability of exploitation in the next 30 days: 0.15% (FIRST EPSS).
- Someone with local access to the system can trigger it. Administrator privileges are required. No user action is required. No special conditions are required; it is repeatable.
- According to the record, no fixed version is available yet.
Low priority for now. Update when a fix is released; follow the vendor's advisory.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
Primary sources: NVD · CVE.org · FIRST EPSS
Improper access control in firmware for some Intel(R) NUC Boards, Intel(R) NUC 11 Performance Kit, Intel(R) NUC 11 Performance Mini PC, Intel(R) NUC Pro Compute Element may allow a privileged user to potentially enable denial of service via local access.
- Published
- May 10, 2023
- Updated
- Jun 17, 2026
- EPSS
- 0.1% · 4th percentile
- CWE
- CWE-284
Report tools
Action score
17
Monitor
Low priority for now.
- CVSS
- 17 / 40 · 4.4 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.1%
CISA SSVC decision
- Exploitation
- none
- Automatable
- no
- Technical impact
- partial
Vulnrichment: CISA's decision-tree inputs.
CNA vs NVD score
- NVD
- 4.4
- CNA · intel
- 5.3
- 0.9 point gap
CVSS:3.1/AV:L/AC:H/PR:H/UI:N/S:C/C:N/I:N/A:H
The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- No public exploit code on record
- No fixed version yet
If any of these changes, we'll tell you in the daily email digest.
Running WordPress? Scan your site free with WP Lens
Noroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
| Vendor | Product | CPE |
|---|---|---|
| intel | nuc 11 performance kit nuc11pahi70z firmware | cpe:2.3:o:intel:nuc_11_performance_kit_nuc11pahi70z_firmware |
| intel | nuc 11 performance kit nuc11pahi70z | cpe:2.3:h:intel:nuc_11_performance_kit_nuc11pahi70z |
| intel | nuc 11 performance kit nuc11pahi50z firmware | cpe:2.3:o:intel:nuc_11_performance_kit_nuc11pahi50z_firmware |
| intel | nuc 11 performance kit nuc11pahi50z | cpe:2.3:h:intel:nuc_11_performance_kit_nuc11pahi50z |
| intel | nuc 11 performance kit nuc11pahi30z firmware | cpe:2.3:o:intel:nuc_11_performance_kit_nuc11pahi30z_firmware |
| intel | nuc 11 performance kit nuc11pahi30z | cpe:2.3:h:intel:nuc_11_performance_kit_nuc11pahi30z |
| intel | nuc 11 performance kit nuc11pahi3 firmware | cpe:2.3:o:intel:nuc_11_performance_kit_nuc11pahi3_firmware |
| intel | nuc 11 performance kit nuc11pahi3 | cpe:2.3:h:intel:nuc_11_performance_kit_nuc11pahi3 |
| intel | nuc 11 performance kit nuc11pahi5 firmware | cpe:2.3:o:intel:nuc_11_performance_kit_nuc11pahi5_firmware |
| intel | nuc 11 performance kit nuc11pahi5 | cpe:2.3:h:intel:nuc_11_performance_kit_nuc11pahi5 |
| intel | nuc 11 performance kit nuc11pahi7 firmware | cpe:2.3:o:intel:nuc_11_performance_kit_nuc11pahi7_firmware |
| intel | nuc 11 performance kit nuc11pahi7 | cpe:2.3:h:intel:nuc_11_performance_kit_nuc11pahi7 |
and 66 more
Affected versions
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- intel nuc 11 performance kit nuc11pahi3 firmwarebefore patgl357.0050
- intel nuc 11 performance kit nuc11pahi30z firmwarebefore patgl357.0050
- intel nuc 11 performance kit nuc11pahi5 firmwarebefore patgl357.0050
- intel nuc 11 performance kit nuc11pahi50z firmwarebefore patgl357.0050
- intel nuc 11 performance kit nuc11pahi7 firmwarebefore patgl357.0050
- intel nuc 11 performance kit nuc11pahi70z firmwarebefore patgl357.0050
- intel nuc 11 performance kit nuc11paki3 firmwarebefore patgl357.0050
- intel nuc 11 performance kit nuc11paki5 firmwarebefore patgl357.0050
- intel nuc 11 performance kit nuc11paki7 firmwarebefore patgl357.0050
- intel nuc 11 performance mini pc nuc11paqi50wa firmwarebefore patgl357.0050
- intel nuc 11 performance mini pc nuc11paqi70qa firmwarebefore patgl357.0050
- intel nuc 11 pro board nuc11tnbi3 firmwarebefore tntgl357.0070
- intel nuc 11 pro board nuc11tnbi30z firmwarebefore tntgl357.0070
- intel nuc 11 pro board nuc11tnbi5 firmwarebefore tntgl357.0070
- intel nuc 11 pro board nuc11tnbi50z firmwarebefore tntgl357.0070
- intel nuc 11 pro board nuc11tnbi7 firmwarebefore tntgl357.0070
- intel nuc 11 pro board nuc11tnbi70z firmwarebefore tntgl357.0070
- intel nuc 11 pro kit nuc11tnhi3 firmwarebefore tntgl357.0070
- intel nuc 11 pro kit nuc11tnhi30l firmwarebefore tntgl357.0070
- intel nuc 11 pro kit nuc11tnhi30p firmwarebefore tntgl357.0070
Versions reported by the vendor
Affected version ranges reported by the assigning authority (intel). Independent of NVD's CPE analysis and usually ahead of it.
n/a Intel(R) NUC Boards, Intel(R) NUC 11 Performance Kit, Intel(R) NUC 11 Performance Mini PC, Intel(R) NUC Pro Compute Element
- See referencesaffected
Same product
intel: all recordsOther highest-scoring records for the same primary product.
- CVE-2023-22312Improper access control for some Intel(R) NUC BIOS firmware may allow a privileged user to potentially enable escalation of privilege via lo31Monitor
- CVE-2023-29500Exposure of sensitive information to an unauthorized actor in BIOS firmware for some Intel(R) NUCs may allow a privilege user to potentially17Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
No fix version is recorded for this entry. Check the references for vendor advisories.
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
No dated events beyond publication.
FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).
Patch and commit links
Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.
No commit or PR link among the references.
Credits
All researchersFinders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.
No credits in the CNA record.
Variant candidates
Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.
No nightly-computed relations.
Chain candidates
An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.
—
Bug bounty scope
The product’s vendor appears in a public program. Matched by name; verify the scope text in the program.
Technical details
Attack conditions
- Someone with local access to the system can trigger it.
- Administrator privileges are required.
- No user action is required.
- No special conditions are required; it is repeatable.
If successful
- Confidentiality
- none
- Integrity
- none
- Availability
- high · the service can be disrupted
- Attack vector
- Local
- Attack complexity
- Low
- Privileges required
- High
- User interaction
- None
- Scope
- Unchanged
- Confidentiality impact
- None
- Integrity impact
- None
- Availability impact
- High
Weakness class (CWE)
CWE-284 · Improper Access ControlCVSS vector
CVSS:3.1/AV:L/AC:L/PR:H/UI:N/S:U/C:N/I:N/A:H
nvd-primary
Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
Attack patterns (CAPEC)
- Embedding Scripts within ScriptsCAPEC-19likelihood: High · High
- Malicious Logic InsertionCAPEC-441likelihood: Medium · High
- Modification of Windows Service ConfigurationCAPEC-478likelihood: Low · High
- Malicious Root CertificateCAPEC-479likelihood: Low · Low
- Intent SpoofCAPEC-502
- WebView ExposureCAPEC-503
- Data Injected During ConfigurationCAPEC-536likelihood: Low · High
- Incomplete Data Deletion in a Multi-Tenant EnvironmentCAPEC-546likelihood: Low · Medium
ATT&CK techniques
- RootkitT1014
- Obfuscated Files or Information: Embedded PayloadsT1027.009
- Boot or Logon Initialization ScriptsT1037
- Taint shared contentT1080
- Server Software Component: Terminal Services DLLT1505.005
- Pre-OS Boot:BootkitT1542.003
- Create or Modify System ProcessT1543
- Create or Modify System Process: Launch AgentT1543.001
- Create or Modify System Process:Windows ServiceT1543.003
- Create or Modify System Process: Launch DaemonT1543.004
- Event Triggered Execution:Change Default File AssociationT1546.001
- Event Triggered Execution:.bash_profile and .bashrcT1546.004
- Event Triggered Execution: Accessibility FeaturesT1546.008
- Event Triggered Execution: Installer PackagesT1546.016
- Boot or Logon Autostart ExecutionT1547
- Boot or Logon Autostart Execution:Kernel Modules and ExtensionsT1547.006
Change log
No changes recorded on tracked fields yet. Score, KEV, exploit maturity and fix status changes appear here.
References
Vendor advisories and official records. Exploit/PoC links are deliberately left out.