CVE-2020-0514
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 default permissions in the installer for Intel(R) Graphics Drivers before versions 26.20.100.7463 and 15.45.30.5103 may allow an authenticated user to potentially enable escalation of privilege 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 confidenceThe Intel Graphics Drivers installer before versions 26.20.100.7463 and 15.45.30.5103 contains improper default permissions that allow an authenticated local user to exploit misconfigured file or directory permissions left by the installer, potentially achieving privilege escalation to higher system privileges.
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>= 15.45, < 15.45.30.5103>= 26.20, < 26.20.100.7463CVSS 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 installed Intel Graphics Driver versionOpen Device Manager, expand 'Display adapters', right-click the Intel graphics device, select 'Properties', go to the 'Driver' tab and note the Driver Version field. Alternatively, run 'dxdiag' from command prompt, go to the 'Display' tab, and check the Driver Version under the Intel device.Affected if The displayed version number is within the range 15.45.0.0 to 15.45.30.5102, or 26.20.0.0 to 26.20.100.7462
-
Confirm the driver vendor and platform typeIn Device Manager under 'Display adapters', verify the device is an Intel graphics adapter (Intel UHD Graphics, Intel Iris Xe, Intel HD Graphics, etc.). Note whether the system uses a legacy (6th-8th gen) or newer (9th gen+) Intel processor platform.Affected if The system has an Intel graphics driver installed and matches either the legacy 15.x.x.x branch or the newer 26.x.x.x branch
-
Cross-reference with Intel's version documentationVisit Intel's support pages or release notes for Intel Graphics Drivers and compare your installed version against the fixed releases 15.45.30.5103 and 26.20.100.7463.Affected if Your installed version is earlier than 15.45.30.5103 (for legacy platforms) or earlier than 26.20.100.7463 (for newer platforms)
You are affected if the Intel Graphics Driver version installed on your system is 15.45.0.0 through 15.45.30.5102, or 26.20.0.0 through 26.20.100.7462.
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 data15.45.30.510326.20.100.7463
Update Intel Graphics Drivers to version 26.20.100.7463 or later (for newer platforms) or 15.45.30.5103 or later (for legacy platforms) to remediate the improper permissions in the installer.
- Consultation2.0 h
- Implementation2.0 h
- Testing4.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,464.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2020-0514 — 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-0514 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