CVE-2024-21861
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 in some Intel(R) GPA Framework software before version 2023.4 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 confidenceUncontrolled search path vulnerability in Intel(R) GPA Framework software before version 2023.4 allows an authenticated local user to potentially escalate privileges by manipulating the application's file search path, likely enabling arbitrary code execution with elevated permissions.
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< 2023.4CVSS 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.
-
Locate Intel GPA Framework installationSearch for 'Intel GPA Framework' folder in common installation directories such as C:\Program Files\Intel\ or C:\Program Files (x86)\Intel\. Also check the Windows registry under HKLM\SOFTWARE\Intel\ or HKLM\SOFTWARE\WOW6432Node\Intel\ for GPA Framework entries.Affected if The software is installed in any location on the system.
-
Identify installed versionOnce the installation directory is found, look for a version file, or right-click on the main executable (typically gpa.exe or similar GPA binaries) and select Properties > Details to view the File Version. Intel typically embeds version information in the executable properties.Affected if The installed version is lower than 2023.4 (for example, 2023.3, 2023.2, or earlier).
-
Check Windows Programs and FeaturesOpen Control Panel > Programs and Features (or Settings > Apps > Installed Apps on Windows 10/11) and locate 'Intel Graphics Performance Analyzers' or similar entry. Note the version number displayed in the installed programs list.Affected if The version shown is earlier than 2023.4.
-
Verify presence of vulnerable binaryUse the Windows command 'where gpa.exe' or search for 'gpa' executables in the Intel GPA installation directory. Confirm the executable exists and note its file version using 'dir /a' and examining properties.Affected if The gpa executable exists and its version information indicates a build before the 2023.4 release.
The system is affected if Intel GPA Framework is installed with any version prior to 2023.4, as this allows a local authenticated user to manipulate the search path for privilege escalation.
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 · scoped2023.4
Upgrade to Intel GPA Framework version 2023.4 or later to obtain the patched binaries with proper path validation controls.
2023.4
- Download Intel Graphics Performance Analyzers Framework version 2023.4 or later from the official Intel website
- Uninstall the current (vulnerable) version of Intel GPA Framework
- Install the downloaded version 2023.4 or later
- Restart any running Intel GPA applications to ensure the updated framework is loaded
- Verify the installed version matches or exceeds 2023.4
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation4.0 h
- Testing3.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,088.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-21861 — 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-21861 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