dbcve.org
Battery Life Diagnostic ToolApplication · Intel

CVE-2023-34430

HIGH · 7.8 CVSS v3.1 Published 2023-11-14
Fix available
A fix is available. Upgrade to 2.2.1 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 Battery Life Diagnostic Tool software before version 2.2.1 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

The Intel Battery Life Diagnostic Tool before version 2.2.1 uses an uncontrolled search path when loading libraries or resources, allowing an authenticated local user to place malicious DLLs in directories searched by the application PATH to achieve privilege escalation.

MitigationUpdate to Intel Battery Life Diagnostic Tool version 2.2.1 or later, which includes a fix for the uncontrolled search path 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
Battery Life Diagnostic ToolApplication
Affected:< 2.2.1

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 Battery Life Diagnostic Tool is installed
    Open Windows Registry Editor and navigate to HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\ or HKCU\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\, look for an entry named 'Intel Battery Life Diagnostic Tool' or search for 'BatteryLifeDiagnostic'
    Affected if No entry found means the product is not installed and is not affected
  2. Determine the installed version
    Locate the installed executable (typically in C:\Program Files\Intel\Battery Life Diagnostic Tool\ or C:\Program Files (x86)\Intel\Battery Life Diagnostic Tool\) and right-click the executable to view Properties, or check the Version string in the Registry uninstall entry
    Affected if The version displayed is less than 2.2.1 (for example, 2.2.0, 2.1.0, 1.x.x, etc.)
  3. Confirm the vulnerability condition
    The vulnerability exists in any version prior to 2.2.1 due to the uncontrolled search path when loading DLLs. If the installed version is below 2.2.1, the application loads libraries from directories in the system PATH that an unprivileged user can modify
    Affected if The installed version is any release prior to 2.2.1, meaning the application is vulnerable to DLL hijacking via PATH manipulation

You are affected if Intel Battery Life Diagnostic Tool is installed with any version number lower than 2.2.1, as the uncontrolled search path vulnerability is present in all prior versions.

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

Update to Intel Battery Life Diagnostic Tool version 2.2.1 or later, which includes a fix for the uncontrolled search path vulnerability.

Recommended fix High confidence

2.2.1

  1. Obtain Intel Battery Life Diagnostic Tool version 2.2.1 or later from Intel's official support website (support.intel.com)
  2. Close any running instances of the Battery Life Diagnostic Tool
  3. Uninstall the current version through Windows Control Panel > Programs and Features
  4. Run the installer for version 2.2.1 as Administrator
  5. Follow the on-screen prompts to complete the installation
  6. Restart the computer if prompted to ensure the application loads with the updated DLL search paths

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

Fix this in Battery Life Diagnostic Tool 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-34430 — 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-34430 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