dbcve.org
Improper Access ControlWeakness · CWE-284

CVE-2024-38310

HIGH · 8.2 CVSS v3.1 Published 2025-02-12
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
82/100
Remediation priority · High

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 access control in some Intel(R) Graphics Driver software installers 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 · moderate confidence

Improper access control in Intel Graphics Driver software installers allows an authenticated local user to escalate privileges. The vulnerability exists in the installer components rather than the driver runtime, enabling a standard user to potentially gain elevated system access through local exploitation.

MitigationApply the patched Intel Graphics Driver installer from Intel's official support channels after validating compatibility with production systems. Prior to deployment, test in a non-production environment to verify driver functionality.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

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
Required
Scope
Changed
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:L/AC:L/PR:L/UI:R/S:C/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 installed Intel Graphics Driver version
    Open Windows Device Manager, expand 'Display adapters', right-click the Intel graphics device, select Properties, then look at the Driver tab for the version number. Alternatively, run 'driverquery /v | findstr -i video' or check Intel Driver & Support Assistant.
    Affected if The installed driver version falls within an affected version range published by Intel, or the version is unknown/unpatched.
  2. Verify file permissions on driver installation directories
    Navigate to the Intel graphics driver install directory (typically C:\Program Files\Intel\Graphics* or C:\Windows\System32\DriverStore\FileRepository\i*.inf), right-click the folder, go to Properties > Security, and verify that standard users do not have Write or Full Control permissions to system driver files.
    Affected if Standard authenticated users have Write or Full Control permissions to driver files or directories, indicating improper ACLs from the installer.
  3. Check for unauthorized service modifications
    Open Services (services.msc) and look for any new or modified services with elevated privileges related to Intel graphics (such as igfx* services). Also run 'sc query' and 'sc qc <servicename>' to inspect service configurations and binary paths.
    Affected if Unexpected services exist with elevated privileges or point to user-controlled binary paths.
  4. Review installation logs for permission anomalies
    Check Windows Installer logs in %TEMP% (look for MSI*.log files around the time of driver installation) or Intel installer logs in ProgramData\Intel\Logs for entries indicating permission setting failures or warnings.
    Affected if Logs show permission-related errors or warnings during installation, suggesting the vulnerability was present.
  5. Audit for signs of local privilege escalation
    Review Windows Security Event Logs (Event Viewer > Windows Logs > Security) for Event ID 4624/4625 (logon success/failure) and 4672 (special privileges assigned) around the time of driver installation, looking for unauthorized admin account creation or use.
    Affected if Unusual privilege escalation events or new administrative accounts appeared after the driver was installed.

A system is affected if it was installed using a vulnerable Intel Graphics Driver installer that left improper permissions on driver files or services, allowing standard users to escalate to elevated privileges.

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.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Apply the patched Intel Graphics Driver installer from Intel's official support channels after validating compatibility with production systems. Prior to deployment, test in a non-production environment to verify driver functionality.

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing6.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,380
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-38310 — 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-2024-38310 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