CVE-2020-24450
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 some Intel(R) Graphics Drivers before versions 26.20.100.8141, 15.45.32.5145 and 15.40.46.5144 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 confidenceAn improper conditions check in Intel(R) Graphics Drivers before versions 26.20.100.8141, 15.45.32.5145 and 15.40.46.5144 may allow an authenticated local user to potentially escalate privileges via local 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>= 15.40.0.0, < 15.40.46.5144>= 15.45, < 15.45.32.5145>= 26.20, < 26.20.100.8141CVSS 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.
-
Check if Intel Graphics Drivers are installedOpen Device Manager, expand 'Display adapters', and look for Intel GPU entries (e.g., Intel UHD Graphics, Intel Iris Xe). Alternatively, run 'dxdiag' from command prompt and check the 'Display' tab for Intel graphics information.Affected if No Intel GPU drivers are present, then the system is not affected.
-
Retrieve the installed Intel Graphics Driver versionIn Device Manager, right-click the Intel GPU, select 'Properties', go to the 'Driver' tab, and note the 'Driver Version'. Alternatively, check the registry key: HKLM\SYSTEM\CurrentControlSet\Control\Class\{4d36e968-e325-11ce-bfc1-08002be10318}\DriverVersionAffected if The driver version field is empty or missing, indicating no Intel graphics driver installed.
-
Compare the installed version against affected rangesIf the version starts with 26.20.x.x, ensure it is >= 26.20.100.8141. If 15.45.x.x, ensure >= 15.45.32.5145. If 15.40.x.x, ensure >= 15.40.46.5144. Any version in the ranges 15.40.0.0 to 15.40.46.5143, 15.45.0.0 to 15.45.32.5144, or 26.20.0.0 to 26.20.100.8140 is vulnerable.Affected if The installed version falls within any of these ranges: >= 15.40.0.0 and < 15.40.46.5144; >= 15.45 and < 15.45.32.5145; >= 26.20 and < 26.20.100.8141.
A system is affected if it has an Intel Graphics Driver installed with a version that falls within the affected ranges and the user has local access to the machine.
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.40.46.514415.45.32.514526.20.100.8141
Update Intel Graphics Drivers to version 26.20.100.8141, 15.45.32.5145, or 15.40.46.5144 or later through Intel's driver update utilities or enterprise deployment tools.
- Consultation2.0 h
- Implementation2.0 h
- Testing3.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,224.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2020-24450 — 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-24450 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