CVE-2020-24462
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 · uneditedOut of bounds write in the Intel(R) Graphics Driver before version 15.33.53.5161, 15.36.40.5162, 15.40.47.5166, 15.45.33.5164 and 27.20.100.8336 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 confidenceOut-of-bounds write vulnerability in Intel(R) Graphics Driver allows an authenticated user to potentially escalate privileges via local access. The flaw exists in driver versions prior to 15.33.53.5161, 15.36.40.5162, 15.40.47.5166, 15.45.33.5164, or 27.20.100.8336.
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.33.53.5161>= 15.36, < 15.36.40.5162>= 15.40.0.0, < 15.40.47.5166>= 15.45.0.0, < 15.45.33.5164>= 27.20, < 27.20.100.8336CVSS 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 version on WindowsOpen Device Manager, expand 'Display adapters', right-click on Intel graphics device, select Properties, go to Driver tab, note the Driver Version fieldAffected if The displayed version falls within any of these ranges: < 15.33.53.5161, >= 15.36 and < 15.36.40.5162, >= 15.40.0.0 and < 15.40.47.5166, >= 15.45.0.0 and < 15.45.33.5164, >= 27.20 and < 27.20.100.8336
-
Verify driver is actively loadedConfirm the Intel graphics driver is present and enabled in Device Manager under Display adaptersAffected if The Intel graphics driver is installed and shows as 'This device is working properly' while the version matches the affected ranges from step 1
-
Confirm local authenticated accessVerify the user account checking this system has local login capabilityAffected if The system allows local user authentication and the driver version matches affected ranges - the privilege escalation requires local access to exploit
If the Intel Graphics Driver version is less than 15.33.53.5161, or falls between 15.36-15.36.40.5161, 15.40.0.0-15.40.47.5165, 15.45.0.0-15.45.33.5163, or 27.20.0.0-27.20.100.8335, the system is affected by this vulnerability.
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.33.53.516115.36.40.516215.40.47.5166
Update Intel graphics drivers to version 15.33.53.5161/15.36.40.5162/15.40.47.5166/15.45.33.5164/27.20.100.8336 or later. Prior to deployment, validate driver compatibility in a test environment.
- 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-24462 — 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-24462 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