dbcve.org
Power GadgetApplication · Intel

CVE-2023-41234

MEDIUM · 5.5 CVSS v3.1 Published 2024-05-16
Fix available
A fix is available. Upgrade to 3.6.0 or later.
See remediation →
57/100
Remediation priority · Elevated
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
NULL pointer dereference in Intel(R) Power Gadget software for Windows all versions 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 · moderate confidence

Intel Power Gadget for Windows contains a NULL pointer dereference vulnerability that can be triggered by an authenticated local user, leading to denial of service. The vulnerability affects all versions of the software.

MitigationApply the latest Intel Power Gadget update from Intel's official website or contact Intel support for patch availability. As a compensating control, limit local user privileges and monitor for DoS conditions.

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
Power GadgetApplication
Affected:< 3.6.0

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
None
Integrity
None
Availability
High

CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/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. Check if Intel Power Gadget is installed
    Look for Intel Power Gadget in the Windows Start Menu, or check Program Files for the folder (typically C:\Program Files\Intel\Power Gadget 3.6\ or similar path containing 'Intel' and 'Power Gadget')
    Affected if Intel Power Gadget is present on the system
  2. Find the installed version number
    Right-click the Intel Power Gadget executable (PowerGadget3.exe), select Properties, then view the Details tab for the Product Version field. Alternatively, open the application and check Help > About for the version number.
    Affected if Version cannot be determined or is below 3.6.0
  3. Verify the affected version range
    Compare the identified version against the affected range: any version before 3.6.0 (such as 3.5.x, 3.0.x, 2.x, or 1.x) is considered vulnerable.
    Affected if Installed version is less than 3.6.0 (for example, 3.5.0, 3.0, 2.6)
  4. Confirm local user access context
    Determine if any authenticated local user account can execute Intel Power Gadget on this system. Check file permissions on the installation directory and executable.
    Affected if Non-admin or standard local users have access to run Intel Power Gadget

The system is affected if Intel Power Gadget is installed with any version prior to 3.6.0 and local authenticated users can trigger the application, leading to potential denial of service via NULL pointer dereference.

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 3.6.0 or later
Fixed in 3.6.0
Interim mitigation

Apply the latest Intel Power Gadget update from Intel's official website or contact Intel support for patch availability. As a compensating control, limit local user privileges and monitor for DoS conditions.

Recommended fix High confidence

3.6.0

  1. Check the current installed version of Intel Power Gadget via Programs and Features or the application's About/Help menu
  2. Close any running instances of Intel Power Gadget
  3. Uninstall the current version of Intel Power Gadget through Windows Control Panel > Programs and Features
  4. Download Intel Power Gadget version 3.6.0 or later from the official Intel website (www.intel.com)
  5. Run the installer for the downloaded version and follow the on-screen prompts to complete the installation
  6. Restart the system if prompted and verify the installed version is 3.6.0 or later

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

Fix this in Power Gadget Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing3.0 h
  • Review / QA1.0 h
8.0 hours of engineering $1,390
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,224.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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