Power GadgetApplication · Intel

CVE-2023-42773

HIGH · 7.8 CVSS v3.1 Published 2024-05-16
Fix available
A fix is available. Upgrade to 3.6.0 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
Improper neutralization in Intel(R) Power Gadget software for Windows all versions 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 confidence

Intel Power Gadget for Windows contains an improper input validation vulnerability that allows an authenticated local user to elevate privileges. The vulnerability stems from insufficient input sanitization within the application, enabling a local attacker to execute code with elevated privileges.

MitigationApply the latest Intel Power Gadget patch or uninstall the software if unused. If patching is not immediately feasible, restrict user access to the application and monitor for suspicious local activity.

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
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. Check if Intel Power Gadget is installed
    Look for Intel Power Gadget in the Windows registry under HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall or check for the installation directory at C:\Program Files\Intel\Power Gadget 3.6 or C:\Program Files (x86)\Intel\Power Gadget 3.6
    Affected if The application is found installed on the system
  2. Locate the Intel Power Gadget executable
    Search for Power Gadget.exe or IntelPowerGadget.exe in the installation directory and subdirectories, or use Get-ChildItem -Path "C:\Program Files","C:\Program Files (x86)" -Recurse -Filter "*Power*Gadget*" -ErrorAction SilentlyContinue
    Affected if The executable is present on the system
  3. Determine the installed version
    Right-click the executable, select Properties, then go to the Details tab to view the File Version, or run (Get-Item "path\to\PowerGadget.exe").VersionInfo
    Affected if The version shown is less than 3.6.0 (for example, 3.5.x, 3.0.x, etc.)
  4. Check if the Intel Power Gadget service or driver is active
    Open Services.msc and look for Intel Power Gadget related services, or run Get-Service | Where-Object {$_.DisplayName -like "*Intel*Power*Gadget*"} to list any running services
    Affected if The service or driver is running on the system

A user is affected if Intel Power Gadget version 3.6.0 or higher is NOT installed on their Windows system, meaning a version lower than 3.6.0 is present and the application is accessible to authenticated local users.

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 patch or uninstall the software if unused. If patching is not immediately feasible, restrict user access to the application and monitor for suspicious local activity.

Recommended fix High confidence

Intel Power Gadget 3.6.0

  1. Navigate to the official Intel website and download Intel Power Gadget version 3.6.0 or later
  2. Uninstall the currently installed version of Intel Power Gadget from the Windows system
  3. Install the newly downloaded version 3.6.0 or later
  4. Restart the computer if prompted by the installer
  5. Verify the installation by checking that the installed version is 3.6.0 or higher

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
  • Testing2.0 h
  • Review / QA1.0 h
7.0 hours of engineering $1,240
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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