CVE-2020-12384
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 access control in some Intel(R) Graphics Drivers before version 26.20.100.8476 may allow an authenticated user to potentially enable an 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 confidenceImproper access control in Intel Graphics Drivers before version 26.20.100.8476 allows a local authenticated user to potentially escalate privileges due to missing access control validation in the driver components, enabling a local attacker to gain elevated system access.
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< 26.20.100.8476CVSS 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 Intel Graphics Driver installationCheck Windows Registry at HKLM\SYSTEM\CurrentControlSet\Services\igfx for the driver, or view Device Manager under Display adapters for Intel graphics devicesAffected if No Intel graphics device or driver is found in the system
-
Retrieve installed Intel Graphics Driver versionIn Device Manager, right-click the Intel graphics device, select Properties, go to the Driver tab and note the Driver Version. Alternatively, run 'dxdiag' from the command line and check the Display tab for the driver version.Affected if A version number is displayed that is lower than 26.20.100.8476
-
Compare version against vulnerability thresholdCompare the installed driver version number to the affected range: any version below 26.20.100.8476 is within the vulnerable rangeAffected if The installed version begins with numbers lower than 26.20.100 (for example, 26.20.100.8445, 25.20.100.6577, etc.)
-
Verify local user access contextConfirm the system allows local authenticated user sessions, as the vulnerability requires a local authenticated attackerAffected if Local user accounts exist on the system and the Intel graphics driver is loaded
The system is affected if Intel Graphics Drivers are installed with a version number lower than 26.20.100.8476 and the system permits local authenticated user access.
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 data26.20.100.8476
Update Intel Graphics Drivers to version 26.20.100.8476 or later across all affected systems to remediate the improper access control vulnerability.
- Consultation2.0 h
- Implementation2.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 $1,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2020-12384 — 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-12384 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