CVE-2020-0571
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 · uneditedImproper conditions check in BIOS firmware for 8th Generation Intel(R) Core(TM) Processors and Intel(R) Pentium(R) Silver Processor Series may allow an authenticated user to potentially enable 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 confidenceThis is a BIOS firmware vulnerability in 8th Generation Intel Core and Intel Pentium Silver processors where an improper conditions check could allow an authenticated local user to potentially enable information disclosure. The vulnerability requires local access and user authentication, making it a local privilege escalation or information disclosure issue in the BIOS/UEFI firmware.
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
- Local
- Complexity
- Low
- Privileges
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- None
- Availability
- None
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N
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 processor generationUse system information tools (such as 'wmic cpu get name' on Windows or 'cat /proc/cpuinfo' on Linux) to identify the CPU model. Look for 8th Generation Intel Core processors (i3-8xxx, i5-8xxx, i7-8xxx, i9-8xxx series) or Intel Pentium Silver processors (J5xxx, J7xxx, N5xxx, N7xxx series).Affected if The processor is an 8th Generation Intel Core or Intel Pentium Silver processor.
-
Check BIOS versionRetrieve the installed BIOS version using system utilities: on Windows, use 'wmic bios get smbiosbiosversion' or check in System Information; on Linux, use 'dmidecode -s bios-version' or check /sys/class/dmi/id/bios_version.Affected if The system has an affected processor AND any BIOS version is installed (all versions are affected per the advisory).
-
Verify OEM and platformConfirm the system manufacturer and model to ensure it uses an affected Intel processor. Use 'wmic computersystem get model,manufacturer' on Windows or 'dmidecode -s system-product-name' on Linux.Affected if The system is a platform using an affected 8th Generation Intel processor.
The system is affected if it runs on an 8th Generation Intel Core or Intel Pentium Silver processor with any BIOS version installed.
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 relevant BIOS/firmware update from the system OEM. Check Intel's website or contact the original equipment manufacturer (OEM) for the specific BIOS version that addresses CVE-2020-0571, and follow the OEM's recommended firmware update procedure.
- Consultation4.0 h
- Implementation3.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,912.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2020-0571 — 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-2020-0571 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