CVE-2021-0145
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 initialization of shared resources in some Intel(R) Processors 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 hardware-level vulnerability in certain Intel processors where shared resources (likely cache, registers, or memory structures) are not properly initialized before use. An authenticated local attacker could potentially read residual data left in these uninitialized shared resources, leading to information disclosure.
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 versionsall versionsall versionsall versionsall versionsall versionsall versionsall 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 the processor modelRun 'wmic cpu get name' on Windows or 'cat /proc/cpuinfo | grep "model name"' on Linux to retrieve the processor modelAffected if The processor model matches any of these: Intel Celeron 6305, Celeron 6305e, Celeron 6600he, Core I3 1000g1, Core I3 1000g4, Core I3 1005g1, or Core I3 11100he
-
Check if this is a NetApp FAS/AFF systemRun 'sysconfig -a' on NetApp systems or check the system inventory for NetApp storage array model informationAffected if The system is a NetApp FAS or AFF storage array with BIOS (all versions affected)
-
Verify BIOS/UEFI firmware versionRun 'dmidecode -s bios-version' on Linux or check via the system's BIOS/UEFI setup utility, or for NetApp check the firmware version via system CLIAffected if The firmware version has not been updated to include the Intel microcode patch addressing this vulnerability
-
Check system logs for microcode update indicatorsReview system event logs or dmesg output for messages containing 'microcode' or 'Intel ME' firmware update entriesAffected if No microcode update has been applied post-boot, indicating the processor may still be running vulnerable microcode
-
Determine if local authenticated access is possibleVerify that local user accounts exist or can be created on the system (for NetApp, check for administrator accounts)Affected if An authenticated local attacker could potentially exploit this vulnerability to read residual data from uninitialized shared processor resources
You are affected if your system uses any of the listed Intel processor models (Celeron 6305/6305e/6600he, Core I3 1000g1/1000g4/1005g1/11100he) or is a NetApp FAS/AFF array, and the BIOS/UEFI firmware has not been updated with the Intel microcode patch for CVE-2021-0145.
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 processor microcode updates and corresponding BIOS/UEFI firmware updates from the system manufacturer. Verify that shared processor resources are properly cleared during initialization.
- 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-2021-0145 — 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-2021-0145 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