dbcve.org
Chipset Device SoftwareApplication · Intel

CVE-2023-25174

HIGH · 7.8 CVSS v3.1 Published 2024-02-14
Fix available
A fix is available. Upgrade to 10.1.19444.8378 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 access control in some Intel(R) Chipset Driver Software before version 10.1.19444.8378 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 vulnerability in Intel Chipset Driver Software allows an authenticated local user to escalate privileges to a higher level (likely system/administrator). The driver fails to properly restrict operations that authenticated users can perform, enabling local privilege escalation.

MitigationUpdate Intel Chipset Driver Software to version 10.1.19444.8378 or later via Intel's official driver update channels.

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
Chipset Device SoftwareApplication
Affected:< 10.1.19444.8378

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. Verify Intel Chipset Device Software is installed
    Check installed programs for Intel Chipset Device Software or Intel Driver & Support Assistant, or check Device Manager under System devices for Intel chipset drivers
    Affected if The software or chipset driver is present on the system
  2. Identify the installed driver version
    Open Device Manager, locate Intel chipset-related devices (typically under System devices), right-click and select Properties, then view the Driver version field. Alternatively, use 'wmic product get name,version' or check Intel's driver update utility if installed
    Affected if A version number is found in the Driver version field
  3. Compare installed version to affected range
    Compare the discovered version number against the affected range: any version below 10.1.19444.8378 is vulnerable
    Affected if The installed version is numerically less than 10.1.19444.8378 (e.g., 10.1.19444.8377 or earlier)
  4. Confirm driver is loaded and active
    Open Device Manager and verify the Intel chipset driver shows as 'This device is working properly' or check Windows Services for Intel-related services. The vulnerability requires the driver to be present and accessible
    Affected if The driver is loaded and the device shows as functional

If Intel Chipset Device Software version is below 10.1.19444.8378 and the chipset driver is loaded and functional, the system is affected by this local privilege escalation vulnerability.

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 10.1.19444.8378 or later
Fixed in 10.1.19444.8378
Interim mitigation

Update Intel Chipset Driver Software to version 10.1.19444.8378 or later via Intel's official driver update channels.

Recommended fix High confidence

10.1.19444.8378 or later

  1. Identify the currently installed Intel Chipset Driver Software version on the system
  2. Navigate to Intel's official support or download page for chipset drivers
  3. Download Intel Chipset Driver Software version 10.1.19444.8378 or later
  4. Follow Intel's standard installation procedure to update the chipset driver, which typically requires administrator privileges and may necessitate a system restart

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

Fix this in Chipset Device Software Scoped from the published advisory
  • Consultation2.0 h
  • Implementation6.0 h
  • Testing3.0 h
  • Review / QA2.0 h
13.0 hours of engineering $2,290
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,664.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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