CVE-2019-14569
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 · uneditedPointer 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 · moderate confidencePointer corruption in Intel NUC system firmware allows a privileged user with local access to potentially escalate privileges, cause denial of service, or obtain information disclosure via corrupted pointers in the firmware layer.
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 your NUC modelLocate the product name label on the device or check your system documentation. Common identifiers include: Nuc 8 Mainstream Game Kit, Nuc 8 Mainstream Game Mini Computer, Nuc Board De3815tybe, Nuc Kit De3815tykhe, or Nuc Kit Dn2820fykh.Affected if The model matches one of the affected products listed in the CVE.
-
Check the current firmware versionEnter the BIOS/UEFI setup during boot (press F2 or Del key), navigate to the Main or Information section, and record the firmware version string. Alternatively, use Intel's System Support Utility or the specific firmware update tool for your NUC model to retrieve the installed version.Affected if The firmware version cannot be read or is not displayed.
-
Compare version against affected rangesFor Nuc 8 Mainstream Game Kit/Mini Computer: ensure version is inwhl357 or higher. For De3815tybe/De3815tykhe: ensure version is ty0022 or higher for one branch, or ty0067 or higher for the other. For Dn2820fykh: ensure version is fy0069 or higher. Any version below these thresholds is vulnerable.Affected if Your installed version is lower than the specified threshold for your model.
-
Verify physical access and privilege settingsConfirm whether the system permits unrestricted local physical access and check if multiple privileged user accounts exist with administrative firmware configuration rights.Affected if The system has uncontrolled physical access or multiple privileged local accounts, increasing exploitability.
You are affected if your NUC model matches one of the listed products and the installed firmware version is below the safe threshold for that model.
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 Intel's firmware update for affected NUC products. Restrict physical access and limit privileged user accounts as a compensating control until patching is complete.
- Consultation2.0 h
- Implementation4.0 h
- Testing2.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,848.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2019-14569 — 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-14569 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