Graphics Performance AnalyzersApplication · Intel

CVE-2023-41961

HIGH · 7.8 CVSS v3.1 Published 2024-05-16
Fix available
A fix is available. Upgrade to 2023.3 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
Uncontrolled search path in some Intel(R) GPA software before version 2023.3 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 confidence

This is an uncontrolled search path vulnerability (DLL planting/hijacking) in Intel GPA software versions prior to 2023.3. An authenticated local user can place malicious files in directories the application searches when loading resources, potentially executing arbitrary code at elevated privileges.

MitigationUpgrade Intel GPA software to version 2023.3 or later which contains the security fix. If immediate upgrade is not feasible, implement application control policies to restrict the software from loading unsigned libraries from untrusted locations.

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
Graphics Performance AnalyzersApplication
Affected:< 2023.3

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. Locate Intel GPA installation directory
    Check common installation paths such as C:\Program Files\Intel\GPA or C:\Program Files (x86)\Intel\GPA, or use the Windows Registry key HKEY_LOCAL_MACHINE\SOFTWARE\Intel\GPA to find the installation path.
    Affected if Intel GPA is installed in any directory on the system.
  2. Identify installed Intel GPA version
    Open the Intel GPA installation directory and locate a version file (such as version.txt, or right-click the main executable like gpa.exe and select Properties > Details to view the File Version).
    Affected if The installed version number is lower than 2023.3.
  3. Check for vulnerable DLL loading behavior
    Run Intel GPA with a debugging or monitoring tool (such as Process Monitor from Sysinternals) filtered to the gpa.exe process. Look for DLL load attempts from directories writable by standard users (for example, the application directory itself or the user's Temp folder).
    Affected if The application loads DLLs from directories where an authenticated local user has write permissions.
  4. Verify current process privilege level
    Open Task Manager, locate any running Intel GPA processes (such as gpa.exe or related components), and check if they are running with elevated privileges (higher integrity level).
    Affected if Intel GPA components are executing with elevated privileges while also loading DLLs from user-writable locations.

The system is affected if Intel Graphics Performance Analyzers version 2023.3 or later is not installed, AND the application loads DLLs from directories writable by non-privileged users while running with 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.

dbcve · scoped
Upgrade available Upgrade to 2023.3 or later
Fixed in 2023.3
Interim mitigation

Upgrade Intel GPA software to version 2023.3 or later which contains the security fix. If immediate upgrade is not feasible, implement application control policies to restrict the software from loading unsigned libraries from untrusted locations.

Recommended fix High confidence

2023.3

  1. Download Intel Graphics Performance Analyzers version 2023.3 or later from the official Intel website
  2. Close any running GPA applications and related processes
  3. Uninstall the current (vulnerable) version of Intel GPA through Windows Control Panel or the uninstaller
  4. Run the installer for version 2023.3
  5. Follow the installation wizard prompts to complete the upgrade
  6. Restart the system if prompted
  7. Verify the installed version is 2023.3 or later

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

Fix this in Graphics Performance Analyzers Scoped from the published advisory
  • Consultation3.0 h
  • Implementation4.0 h
  • Testing2.0 h
  • Review / QA1.0 h
10.0 hours of engineering $1,800
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2023-41961 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