dbcve.org
Graphics DriversApplication · Intel

CVE-2021-0062

HIGH · 7.8 CVSS v3.1 Published 2021-08-11
Fix available
A fix is available. Upgrade to 27.20.100.8935 or later.
See remediation →
80/100
Remediation priority · High
Zero-click

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 · unedited
Improper input validation in some Intel(R) Graphics Drivers before version 27.20.100.8935 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 confidence

Improper input validation in Intel(R) Graphics Drivers before version 27.20.100.8935 allows an authenticated local user to potentially escalate privileges. The vulnerability stems from insufficient validation of input data within the graphics driver component, which could be exploited to gain elevated system access.

MitigationUpdate Intel Graphics Drivers to version 27.20.100.8935 or later. Apply via Intel's driver update utilities or enterprise deployment tools, and verify functionality post-update.

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
Graphics DriversApplication
Affected:>= 27.20, < 27.20.100.8935

CVSS 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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify Intel Graphics Driver installation
    Open Device Manager, expand 'Display adapters', and look for Intel integrated graphics devices (e.g., Intel UHD Graphics, Intel Iris Xe). Alternatively, run 'wmic path win32_VideoController get name' in Command Prompt.
    Affected if No Intel GPU device is found in the system.
  2. Retrieve installed driver version
    In Device Manager, right-click the Intel GPU, select 'Properties', go to the 'Driver' tab, and note the Driver Version field. Alternatively, run 'wmic path win32_VideoController get driverversion' in Command Prompt.
    Affected if Unable to retrieve a driver version number.
  3. Parse the driver version number
    Extract the full version string from the Driver tab or wmic output. Intel driver versions follow the format XX.XX.XXXXX.XXXX (for example, 27.20.100.8934). Compare the first two segments against the vulnerable range.
    Affected if The version starts with 27.20 (meaning version 27.20.x.x.x).
  4. Compare against vulnerable version range
    Check if the installed version is greater than or equal to 27.20.0.0 AND less than 27.20.100.8935. Any version from 27.20.0.0 through 27.20.100.8934 is vulnerable.
    Affected if The version falls within >= 27.20.0.0 and < 27.20.100.8935.

A user is affected if their system has an Intel Graphics Driver installed with a version number in the range 27.20.0.0 to 27.20.100.8934 inclusive.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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.

dbcve · scoped
Upgrade available Upgrade to 27.20.100.8935 or later
Fixed in 27.20.100.8935
Interim mitigation

Update Intel Graphics Drivers to version 27.20.100.8935 or later. Apply via Intel's driver update utilities or enterprise deployment tools, and verify functionality post-update.

Recommended fix High confidence

27.20.100.8935 or later

  1. Open Device Manager on the Windows system
  2. Expand 'Display adapters' to locate the Intel graphics driver
  3. Right-click the Intel graphics device and select 'Properties'
  4. Go to the 'Driver' tab to check the current driver version
  5. If the version is below 27.20.100.8935, navigate to Intel's official support website at www.intel.com
  6. Use Intel's Driver & Support Assistant or manually search for the appropriate Intel Graphics Driver for your specific GPU model
  7. Download the latest Intel Graphics Driver version 27.20.100.8935 or later
  8. Run the downloaded installer and follow the on-screen prompts to update the driver

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Graphics Drivers Scoped from the published advisory
  • Consultation3.0 h
  • Implementation4.0 h
  • Testing2.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,980
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,168.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2021-0062 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2021-0062 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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