dbcve.org
PcmanagerApplication · Lenovo

CVE-2019-6197

HIGH · 7.8 CVSS v3.1 Published 2024-07-31
Fix available
A fix is available. Upgrade to 2.8.90.11211 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 vulnerability was reported in Lenovo PC Manager prior to version 2.8.90.11211 that could allow a local attacker to escalate 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 · moderate confidence

Lenovo PC Manager prior to version 2.8.90.11211 contains a local privilege escalation vulnerability allowing an attacker with local system access to gain elevated privileges. The exact exploitation vector is not detailed, but the vulnerability is classified as local attack vector requiring low complexity to exploit.

MitigationUpgrade Lenovo PC Manager to version 2.8.90.11211 or later to remediate the 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
PcmanagerApplication
Affected:< 2.8.90.11211

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 Lenovo PC Manager is installed
    Open Windows Control Panel > Programs and Features, or use PowerShell: Get-ItemProperty 'HKLM:\Software\Microsoft\Windows\CurrentVersion\Uninstall\*' | Where-Object {$_.DisplayName -like '*Lenovo*PC*Manager*'}
    Affected if Lenovo PC Manager appears in the installed programs list
  2. Find the installed version number
    In Programs and Features, click on Lenovo PC Manager to view the version, or use PowerShell: (Get-Item 'C:\Program Files\Lenovo\Lenovo PC Manager\PCManager.exe').VersionInfo.FileVersion
    Affected if The displayed version is lower than 2.8.90.11211
  3. Check the executable file version directly
    Navigate to the default install path C:\Program Files\Lenovo\Lenovo PC Manager\PCManager.exe, right-click > Properties > Details tab to view the File Version
    Affected if The File Version field shows a version below 2.8.90.11211
  4. Compare against the affected version range
    Document the exact version number found and compare it to the vulnerable range: any version prior to 2.8.90.11211
    Affected if The installed version is any release earlier than 2.8.90.11211

A user is affected if Lenovo PC Manager is installed and its version number is below 2.8.90.11211.

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.8.90.11211 or later
Fixed in 2.8.90.11211
Interim mitigation

Upgrade Lenovo PC Manager to version 2.8.90.11211 or later to remediate the vulnerability.

Recommended fix High confidence

2.8.90.11211 or later

  1. Check current Lenovo PC Manager version by opening the application and navigating to Settings > About, or right-clicking the system tray icon and selecting About
  2. Open Lenovo PC Manager and click on the Check for Updates button if available, or navigate to the official Lenovo support website at iknow.lenovo.com.cn
  3. Download the latest version of Lenovo PC Manager (version 2.8.90.11211 or later) from the official Lenovo source
  4. Run the installer and follow the on-screen prompts to complete the upgrade
  5. Restart the computer if prompted and verify the version by checking Settings > About to confirm version 2.8.90.11211 or higher is installed

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

Fix this in Pcmanager Scoped from the published advisory
  • Consultation1.0 h
  • Implementation2.0 h
  • Testing1.0 h
  • Review / QA1.0 h
5.0 hours of engineering $890
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,424.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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