dbcve.org
DiagnosticsApplication · Lenovo

CVE-2022-3699

HIGH · 7.8 CVSS v3.1 Published 2023-10-25
Fix available
A fix is available. Upgrade to 1.3.1.2 / 2.4.1.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
A privilege escalation vulnerability was reported in the Lenovo HardwareScanPlugin prior to version 1.3.1.2 and Lenovo Diagnostics prior to version 4.45 that could allow a local user to execute code with elevated privileges.

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

A local privilege escalation vulnerability in Lenovo HardwareScanPlugin (prior to 1.3.1.2) and Lenovo Diagnostics (prior to 4.45) allows an authenticated local user to execute arbitrary code with elevated SYSTEM or administrator privileges. The diagnostic software runs with higher privileges and contains a flaw enabling a local attacker to escalate their privileges.

MitigationUpdate Lenovo HardwareScanPlugin to version 1.3.1.2 or later and Lenovo Diagnostics to version 4.45 or later. Deploy via enterprise patch management tools and verify successful installation.

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
DiagnosticsApplication
Affected:< 4.45.0
Hardwarescan AddinApplication
Affected:< 2.4.1.1
Hardwarescan PluginPlugin / extension
Affected:< 1.3.1.2

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 Lenovo Diagnostics version
    Open Programs and Features (appwiz.cpl) or check the installation directory typically at C:\Program Files\Lenovo\Lenovo Diagnostics\ and locate the main executable file properties to view version, or check registry at HKLM\SOFTWARE\Lenovo\Lenovo Diagnostics for Version value
    Affected if Version is present and less than 4.45.0
  2. Check Lenovo HardwareScanPlugin version
    Check the installation directory typically at C:\Program Files\Lenovo\HardwareScanPlugin\ for the plugin executable file properties to view version, or check registry at HKLM\SOFTWARE\Lenovo\HardwareScanPlugin for Version
    Affected if Version is present and less than 1.3.1.2
  3. Check Lenovo Hardwarescan Addin version
    Check the installation directory typically at C:\Program Files\Lenovo\HardwareScan Addin\ for the addin executable file properties to view version, or check registry at HKLM\SOFTWARE\Lenovo\HardwareScan Addin for Version
    Affected if Version is present and less than 2.4.1.1
  4. Identify running diagnostic services with elevated privileges
    Open Services (services.msc) and look for Lenovo diagnostic services running with SYSTEM or administrator privileges, or use command 'sc query type= service' and 'sc qc <service_name>' to check the binary path and startup type
    Affected if Any Lenovo diagnostic service is installed and runs with elevated privileges while the version is below the fixed releases

If any of the three affected Lenovo software components are installed with a version below 4.45.0 (Diagnostics), 1.3.1.2 (HardwareScanPlugin), or 2.4.1.1 (HardwareScan Addin) and the software runs with elevated privileges, the environment is affected by this CVE.

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 1.3.1.2 / 2.4.1.1 / 4.45.0 or later
Fixed in 1.3.1.22.4.1.14.45.0
Interim mitigation

Update Lenovo HardwareScanPlugin to version 1.3.1.2 or later and Lenovo Diagnostics to version 4.45 or later. Deploy via enterprise patch management tools and verify successful installation.

Recommended fix High confidence

Diagnostics >= 4.45.0 | HardwareScan Plugin >= 1.3.1.2 | HardwareScan Addin >= 2.4.1.1

  1. Identify which Lenovo component is installed: Diagnostics, Hardwarescan Addin, or Hardwarescan Plugin
  2. For Lenovo Diagnostics: Upgrade to version 4.45.0 or later
  3. For Lenovo HardwareScan Plugin: Upgrade to version 1.3.1.2 or later
  4. For Lenovo HardwareScan Addin: Upgrade to version 2.4.1.1 or later
  5. Obtain the updated versions from the official Lenovo support website (support.lenovo.com)
  6. Apply the update following Lenovo's standard installation procedures
  7. Verify the installed version matches the fixed release

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

Fix this in Diagnostics 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-2022-3699 — 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-2022-3699 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