CVE-2019-14570
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 · uneditedMemory corruption in system firmware for Intel(R) NUC may allow a privileged user to potentially enable escalation of privilege, denial of service and/or information disclosure 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 confidenceMemory corruption vulnerability in Intel NUC system firmware allows a privileged local attacker to potentially escalate privileges, cause denial of service, or obtain information disclosure by exploiting the memory corruption in the firmware via local access.
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< inwhl357< inwhl357< ty0022< ty0067< ty0022< ty0067< fy0069CVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Identify the exact Intel NUC model numberCheck the physical system label, packaging, or boot into BIOS (press F2 during startup) to view the product name under Main or Information sectionAffected if The model matches one of the affected products: NUC 8 Mainstream Game Kit, NUC 8 Mainstream Game Mini Computer, NUC Board De3815tybe, NUC Kit De3815tykhe, or NUC Kit Dn2820fykh
-
Check the installed firmware versionBoot into BIOS/UEFI setup (press F2) and locate the firmware or BIOS version under the Main or Information page; alternatively, use Intel NUC firmware update utilities if availableAffected if The firmware version shown is lower than the affected version thresholds for your specific model
-
Compare firmware version against affected rangesFor NUC 8 Mainstream Game Kit or Mini Computer: compare version to inwhl357. For De3815tybe or De3815tykhe: compare to ty0022 and ty0067. For Dn2820fykh: compare to fy0069Affected if Your installed version is lower than the stated threshold for your model (e.g., below inwhl357, below ty0022/ty0067, or below fy0069)
If your Intel NUC model matches one of the affected products AND your current firmware version is lower than the specified version threshold for that model, your system is vulnerable to CVE-2019-14570.
Generated from the published advisory. Verify against your own configuration.
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.
From vendor dataApply the Intel firmware update for affected NUC models. Verify the firmware version through Intel's product security advisories and update BIOS/UEFI firmware following vendor deployment guidelines.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,176.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2019-14570 — 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 sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2019-14570 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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