CVE-2019-14557
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 · uneditedBuffer overflow in BIOS firmware for 8th, 9th, 10th Generation Intel(R) Core(TM), Intel(R) Celeron(R) Processor 4000 & 5000 Series Processors may allow an authenticated user to potentially enable elevation of privilege or denial of service via adjacent 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 confidenceBuffer overflow vulnerability in BIOS firmware affecting 8th, 9th, and 10th Generation Intel Core processors and Celeron 4000/5000 series. An authenticated user with adjacent network or physical access can exploit the overflow to escalate privileges or cause denial of service.
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 dataall versionsCVSS 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
- Adjacent
- Complexity
- Low
- Privileges
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:A/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 Intel processor generationRun 'wmic cpu get name,processorid' or check /proc/cpuinfo on Linux to identify the CPU model. Look for 8th, 9th, or 10th Generation Intel Core processors, or Celeron 4000/5000 series.Affected if The CPU is an 8th, 9th, or 10th Generation Intel Core or a Celeron 4000/5000 series processor.
-
Determine BIOS vendor and versionOn Windows, run 'wmic bios get name,version,manufacturer' or check System Information (msinfo32). On Linux, run 'dmidecode -s bios-version' or check /sys/class/dmi/id/bios_version.Affected if The system uses Intel BIOS firmware (Intel is the BIOS manufacturer).
-
Check for Intel Management Engine interfaceOn Windows, open Intel Driver & Support Assistant or check Device Manager under System Devices for Intel Management Engine Interface. On Linux, run 'lsmod | grep megasr' or check if /dev/mei exists.Affected if Intel Management Engine interface is present and enabled, as this provides the attack vector for adjacent network exploitation.
-
Verify network-accessible firmware update servicesCheck if Intel Software Guard Extensions (SGX) is enabled in BIOS/UEFI settings, or if Intel vPro/AMT network management features are active. Run 'powercfg /devicequery all_devices' on Windows to list firmware-related devices.Affected if Network-accessible Intel firmware services (vPro, AMT, SENTER) are enabled, allowing adjacent network attack vector.
You are affected if your system uses an Intel processor from 8th, 9th, or 10th Generation Core or Celeron 4000/5000 series with Intel BIOS firmware, especially if Intel Management Engine or network-accessible firmware services are enabled.
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-provided BIOS firmware updates for affected processors. This requires downloading firmware from Intel's support site and flashing the BIOS, typically through vendor tools or in-band update mechanisms.
- Consultation8.0 h
- Implementation16.0 h
- Testing8.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 $10,240.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2019-14557 — 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-14557 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