CVE-2019-6191
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 · uneditedA potential vulnerability in the discontinued LenovoPaper software version 1.0.0.22 may allow local privilege escalation.
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 confidenceLenovoPaper version 1.0.0.22 contains a local privilege escalation vulnerability allowing an attacker with low-level access to elevate to higher system privileges. The CVSS 7.8 score indicates a local attack vector with low complexity and high impact on system integrity.
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= 1.0.0.22CVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Verify LenovoPaper installation existsOpen Windows Control Panel, navigate to Programs and Features, or run 'Get-Package -ProviderName Programs -IncludeAvailableProgram' in PowerShell to list installed software. Look for 'Lenovo Paper' or 'LenovoPaper' in the installed programs list.Affected if LenovoPaper is not listed in installed programs, the system is not affected.
-
Confirm installed version numberIn Programs and Features window, click on Lenovo Paper to display the version, or use PowerShell: Get-WmiObject -Class Win32_Product | Where-Object {$_.Name -like '*Lenovo*Paper*'} | Select-Object Name, VersionAffected if Version displayed is 1.0.0.22, the exact affected version.
-
Check for LenovoPaper executable presenceSearch for 'LenovoPaper.exe' or 'LPaper.exe' in common installation directories: C:\Program Files\Lenovo, C:\Program Files (x86)\Lenovo, or C:\Users\%USERNAME%\AppData\Local\Lenovo. Use PowerShell: Get-ChildItem -Path C:\ -Recurse -Filter 'LenovoPaper.exe' -ErrorAction SilentlyContinueAffected if The executable LenovoPaper.exe is found on the system, indicating potential exposure.
-
Identify if software runs with elevated privilegesOpen Task Manager, go to Details tab, look for LenovoPaper.exe processes. Right-click and check 'Run as administrator' status or examine process tokens. Also check Windows Services for 'LenovoPaper' service if present.Affected if LenovoPaper runs as a service or with elevated permissions, the privilege escalation vulnerability is applicable.
A system is affected if Lenovo Paper version 1.0.0.22 is installed and the software is present and executable on the system.
Generated from the published advisory. Verify against your own configuration.
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.
From vendor dataSince LenovoPaper is discontinued and receives no further updates, the recommended remediation is to uninstall or remove the software entirely from affected systems to eliminate the privilege escalation risk.
- Consultation2.0 h
- Implementation2.0 h
- Testing2.0 h
- Review / QA1.0 h
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 locallyCheck whether your project pulls in CVE-2019-6191 — 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 sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2019-6191 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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