dbcve.org
Extreme Tuning UtilityApplication · Intel

CVE-2023-34350

HIGH · 7.8 CVSS v3.1 Published 2023-11-14
Fix available
A fix is available. Upgrade to 7.12.0.15 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 element in some Intel(R) XTU software before version 7.12.0.15 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

Intel XTU (Extreme Tuning Utility) before version 7.12.0.15 contains an uncontrolled search path element vulnerability, allowing an authenticated local user to potentially achieve privilege escalation by placing malicious DLLs in locations where the application searches for libraries.

MitigationUpdate Intel XTU to version 7.12.0.15 or later to remediate this vulnerability.

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
Extreme Tuning UtilityApplication
Affected:< 7.12.0.15

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. Verify Intel XTU is installed
    Check for the presence of Intel XTU executable on the system. Look for 'Intel Extreme Tuning Utility' in the list of installed programs via Control Panel > Programs and Features, or search for XTU-related processes running on the system.
    Affected if Intel XTU is found installed on the system.
  2. Locate the Intel XTU installation directory
    Find where Intel XTU is installed. Common paths include C:\Program Files\Intel\Intel(R) Extreme Tuning Utility\ or C:\Program Files (x86)\Intel\Intel(R) Extreme Tuning Utility\. The executable is typically named 'XTU3CPService.exe' or similar XTU-related files.
    Affected if Intel XTU executable files exist on the system.
  3. Determine the installed Intel XTU version
    Right-click on the Intel XTU executable file (such as XTU3CPService.exe), select Properties, then navigate to the Details tab to view the File Version. Alternatively, open Intel XTU itself and check Help > About for the version number.
    Affected if The installed version is lower than 7.12.0.15.
  4. Confirm the vulnerability condition
    Compare your identified version against the affected range: any version of Intel Extreme Tuning Utility below 7.12.0.15 is vulnerable to this uncontrolled search path element flaw.
    Affected if Installed version is < 7.12.0.15.

The system is affected if Intel XTU is installed and the running version is below 7.12.0.15, making it susceptible to DLL hijacking through uncontrolled search paths.

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

Update Intel XTU to version 7.12.0.15 or later to remediate this vulnerability.

Recommended fix High confidence

7.12.0.15

  1. Verify current installed version of Intel Extreme Tuning Utility (XTU) by opening the application and checking About/Version information
  2. Navigate to the official Intel support website to download Intel XTU version 7.12.0.15 or later
  3. Close any running instances of Intel XTU and ensure related services are stopped
  4. Uninstall the current version of Intel XTU through Windows Control Panel > Programs and Features
  5. Run the installer for the downloaded Intel XTU 7.12.0.15 or newer version
  6. Follow the on-screen installation prompts to complete the upgrade
  7. Restart the system if prompted by the installer
  8. Verify the installed version matches 7.12.0.15 or later after installation completes

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

Fix this in Extreme Tuning Utility Scoped from the published advisory
  • Consultation1.0 h
  • Implementation1.0 h
  • Testing2.0 h
  • Review / QA1.0 h
5.0 hours of engineering $860
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,376.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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