CVE-2024-21814
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 · uneditedUncontrolled search path for some Intel(R) Chipset Device 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 · high confidenceThis is an uncontrolled search path vulnerability in Intel Chipset Device Software where the application uses relative or incomplete paths when loading libraries or executables. An authenticated local attacker can place a malicious DLL or executable in a directory that gets searched before the legitimate location, causing the software (which runs with elevated privileges) to execute the attacker's code instead, achieving privilege escalation.
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< 10.1.19444.8378CVSS 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
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:L/AC:L/PR:L/UI:R/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 Chipset Device Software is installedOpen Windows Registry Editor and navigate to HKLM\SOFTWARE\Intel\Chipset Device Software (or check Program Files for Intel folder). Alternatively, open Programs and Features in Control Panel and look for Intel Chipset Device Software in the list.Affected if The software is not found in the registry, Program Files, or Programs and Features list.
-
Identify the installed versionIn Registry Editor, check the Version value under HKLM\SOFTWARE\Intel\Chipset Device Software. If using Programs and Features, the installed version is shown in the version column.Affected if The displayed version is blank or cannot be determined.
-
Compare version to the affected rangeCompare the installed version number to 10.1.19444.8378. Any version lower than 10.1.19444.8378 is within the affected range.Affected if The installed version is numerically lower than 10.1.19444.8378 (for example, 10.1.19444.8000 or earlier).
You are affected if Intel Chipset Device Software is installed and the version is lower than 10.1.19444.8378.
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.
dbcve · scoped10.1.19444.8378
Upgrade Intel Chipset Device Software to version 10.1.19444.8378 or later to eliminate the uncontrolled search path vector.
Intel Chipset Device Software version 10.1.19444.8378 or later
- Identify the current version of Intel(R) Chipset Device Software installed on the system
- Download the Intel(R) Chipset Device Software version 10.1.19444.8378 or later from the official Intel support website
- Run the installer with administrative privileges
- Follow the on-screen installation prompts to complete the upgrade
- Restart the system as required by the installer
- Verify the installed version matches or exceeds 10.1.19444.8378
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation3.0 h
- Testing2.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,200.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-21814 — 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-2024-21814 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