CVE-2024-28046
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 software before version 2024.1 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 confidenceIntel GPA software before version 2024.1 contains an uncontrolled search path vulnerability where an authenticated local user can manipulate the search path to cause the application to load malicious executable files or DLLs, potentially 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< 2024.1CVSS 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.
-
Verify Intel GPA installationCheck if Intel Graphics Performance Analyzers is installed on the system. On Windows, review the list of installed programs in Settings > Apps & Features, or check for Intel GPA executable files in common installation directories such as C:\Program Files\Intel\GPA or C:\Program Files (x86)\Intel\GPA.Affected if Intel GPA software is found installed on the system
-
Locate Intel GPA executableSearch for Intel GPA application executables such as gpa.exe, intelgpa.exe, or similar binaries in the installation directory identified in the previous step.Affected if An Intel GPA executable is present on the system
-
Determine installed versionRight-click the Intel GPA executable, select Properties, and review the Details tab for the Product Version. Alternatively, use the command line to query version information from the executable file.Affected if Version information cannot be obtained or shows a version number
-
Compare version against affected rangeCompare the installed version number to the affected range. The vulnerability affects all versions prior to 2024.1. Note that version numbers may appear in formats like 2023.x, 23.x, or similar notation.Affected if The installed version is earlier than 2024.1 (for example, 2023.3, 2023.2, 22.x, etc.)
A user is affected if Intel Graphics Performance Analyzers is installed and the installed version is any release prior to version 2024.1.
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 · scoped2024.1
Upgrade to Intel GPA version 2024.1 or later which addresses the uncontrolled search path issue.
Intel Graphics Performance Analyzers 2024.1
- 1. Navigate to the Intel Graphics Performance Analyzers download page at www.intel.com
- 2. Locate the Intel GPA version 2024.1 or later
- 3. Download the installer for your operating system
- 4. Close any running Intel GPA applications
- 5. Run the installer and follow the on-screen prompts to complete the upgrade
- 6. Verify the installation by checking the installed version in the application or system settings
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation2.0 h
- Testing4.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,464.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-28046 — 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-28046 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