cve.bz

CVE-2017-5700 intel: Insufficiently Protected Credentials

8.4 highEPSS 0.4%Fix available

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

On this page
Insufficient protection of password storage in system firmware for Intel NUC7i3BNK, NUC7i3BNH, NUC7i5BNK, NUC7i5BNH, NUC7i7BNH versions BN0049 and below allows local attackers to bypass Administrator and User passwords via access to password storage.

Severity

CVSS 3.0

8.4 high
CVSS:3.0/AV:L/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
EPSS
0.4% (unchanged from 0.4% a week ago; 0.4% 30 days ago) estimated probability of exploitation activity in the next 30 days; 33rd percentile. Scored 2026-11-21. A forecast for this CVE across the internet, not for your own systems.
CWE
CWE-522 Insufficiently Protected Credentials
OWASP Top 10
A06:2025 Insecure Design
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-2017-5700 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2017-5700?via=ask-ai-copy and https://cve.bz/cve/CVE-2017-5700?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-2017-5700 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:nuc7i7bnh_firmwareayaplcel.86a.0041
intel:nuc7i7bnh_firmwarebnkbl357.86a.0052
intel:nuc7i7bnh_firmwareccsklm5v.86a.0052
intel:nuc7i7bnh_firmwareccsklm30.86a.0052
intel:nuc7i7bnh_firmwarednkbli5v.86a.0026
intel:nuc7i7bnh_firmwarednkbli30.86a.0026
intel:nuc7i7bnh_firmwarekyskli70.86a.0050
intel:nuc7i7bnh_firmwarerybdwi35.86a.0366
intel:nuc7i7bnh_firmwaresyskli35.86a.0062
intel:nuc7i7bnh_firmwaretybyt20h.86a.0015
intel:nuc7i5bnh_firmwareayaplcel.86a.0041
intel:nuc7i5bnh_firmwarebnkbl357.86a.0052
intel:nuc7i5bnh_firmwareccsklm5v.86a.0052
intel:nuc7i5bnh_firmwareccsklm30.86a.0052
intel:nuc7i5bnh_firmwarednkbli5v.86a.0026
intel:nuc7i5bnh_firmwarednkbli30.86a.0026
intel:nuc7i5bnh_firmwarekyskli70.86a.0050
intel:nuc7i5bnh_firmwarerybdwi35.86a.0366
intel:nuc7i5bnh_firmwaresyskli35.86a.0062
intel:nuc7i5bnh_firmwaretybyt20h.86a.0015
intel:nuc7i5bnk_firmwareayaplcel.86a.0041
intel:nuc7i5bnk_firmwarebnkbl357.86a.0052
intel:nuc7i5bnk_firmwareccsklm5v.86a.0052
intel:nuc7i5bnk_firmwareccsklm30.86a.0052
intel:nuc7i5bnk_firmwarednkbli5v.86a.0026
intel:nuc7i5bnk_firmwarednkbli30.86a.0026
intel:nuc7i5bnk_firmwarekyskli70.86a.0050
intel:nuc7i5bnk_firmwarerybdwi35.86a.0366
intel:nuc7i5bnk_firmwaresyskli35.86a.0062
intel:nuc7i5bnk_firmwaretybyt20h.86a.0015
intel:nuc7i3bnh_firmwareayaplcel.86a.0041
intel:nuc7i3bnh_firmwarebnkbl357.86a.0052
intel:nuc7i3bnh_firmwareccsklm5v.86a.0052
intel:nuc7i3bnh_firmwareccsklm30.86a.0052
intel:nuc7i3bnh_firmwarednkbli5v.86a.0026
intel:nuc7i3bnh_firmwarednkbli30.86a.0026
intel:nuc7i3bnh_firmwarekyskli70.86a.0050
intel:nuc7i3bnh_firmwarerybdwi35.86a.0366
intel:nuc7i3bnh_firmwaresyskli35.86a.0062
intel:nuc7i3bnh_firmwaretybyt20h.86a.0015
intel:nuc7i3bnk_firmwareayaplcel.86a.0041
intel:nuc7i3bnk_firmwarebnkbl357.86a.0052
intel:nuc7i3bnk_firmwareccsklm5v.86a.0052
intel:nuc7i3bnk_firmwareccsklm30.86a.0052
intel:nuc7i3bnk_firmwarednkbli5v.86a.0026
intel:nuc7i3bnk_firmwarednkbli30.86a.0026
intel:nuc7i3bnk_firmwarekyskli70.86a.0050
intel:nuc7i3bnk_firmwarerybdwi35.86a.0366
intel:nuc7i3bnk_firmwaresyskli35.86a.0062
intel:nuc7i3bnk_firmwaretybyt20h.86a.0015

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-522 (13).

References

Check your stackJSON