dbcve.org
Improper Access ControlWeakness · CWE-284

CVE-2024-41934

MEDIUM · 5.9 CVSS v3.1 Published 2025-02-12
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
59/100
Remediation priority · Elevated

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) GPA software before version 2024.3 may allow an authenticated user to potentially enable denial of service 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

Intel Graphics Performance Analyzers (GPA) versions before 2024.3 contain an improper access control vulnerability that allows an authenticated local user to potentially cause a denial of service condition. This is a local privilege escalation/authorization flaw where proper access restrictions are not enforced, enabling a legitimate but potentially unprivileged authenticated user to trigger a crash or resource exhaustion.

MitigationUpgrade Intel GPA software to version 2024.3 or later. As this is a local access vulnerability requiring authentication, ensure least-privilege principles are applied to user accounts with access to the affected systems.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

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
Required
Scope
Changed
Confidentiality
None
Integrity
None
Availability
High

CVSS:3.1/AV:L/AC:L/PR:L/UI:R/S:C/C:N/I:N/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. Confirm Intel GPA installation exists
    Search for Intel GPA installation directories (typically under C:\Program Files\Intel\ or C:\Program Files (x86)\Intel\) or check Windows Registry under HKLM\SOFTWARE\Intel\GPA for installation evidence
    Affected if Intel GPA software is found installed on the system
  2. Determine installed Intel GPA version
    Locate the version information in the installation directory (often in version.dll, GPAinfo.txt, or the main executable properties) or query the Windows Registry key HKLM\SOFTWARE\Intel\GPA\Version
    Affected if A version number is returned that is lower than 2024.3 (e.g., 2024.2, 2024.1, 2023.x, etc.)
  3. Verify local user access to GPA binaries
    Check file system permissions on the Intel GPA installation folder and verify that standard authenticated users (non-administrators) have read/execute access to the GPA executables
    Affected if Authenticated local users without administrative privileges can access and execute Intel GPA binaries
  4. Confirm GPA components are accessible to standard users
    Attempt to launch Intel GPA applications (such as Graphics Monitor, System Analyzer, or Frame Analyzer) using a non-privileged authenticated user account
    Affected if The software launches successfully for a standard (non-admin) user account, indicating the vulnerable access control condition exists

A system is affected if Intel GPA version 2024.x before 2024.3 (or any earlier version) is installed and standard authenticated users can access or execute the software components.

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
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Upgrade Intel GPA software to version 2024.3 or later. As this is a local access vulnerability requiring authentication, ensure least-privilege principles are applied to user accounts with access to the affected systems.

Recommended fix High confidence

Intel GPA 2024.3

  1. 1. Identify the current version of Intel(R) GPA software installed on the system
  2. 2. Navigate to the official Intel website or Intel Developer Zone to download Intel GPA version 2024.3 or later
  3. 3. Install the updated Intel GPA software version following Intel's standard installation procedures
  4. 4. Verify the installation completed successfully and the version is 2024.3 or higher

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

Have this fixed Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing4.0 h
  • Review / QA2.0 h
15.0 hours of engineering $2,640
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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