CVE-2016-8225
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 · uneditedUnquoted service path vulnerability in Lenovo Edge and Lenovo Slim USB Keyboard Driver versions earlier than 1.21 allows local users 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 confidenceAn unquoted service path vulnerability exists in Lenovo Edge and Lenovo Slim USB Keyboard Driver versions earlier than 1.21. This allows local users to place a malicious executable in an unquoted service path directory, which gets executed with elevated privileges when the service starts.
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.20<= 1.20CVSS 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.0/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.
-
Identify installed Lenovo USB Keyboard Driver versionOpen Windows Registry Editor and navigate to HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Setup or check the driver file properties of the installed keyboard driver. Alternatively, open Device Manager, expand Keyboards, right-click the Lenovo USB keyboard device, select Properties, and view the Driver tab for the driver version.Affected if The displayed version number is 1.20 or lower, or if no version is shown but the driver was installed prior to the 1.21 release.
-
Locate the USB Keyboard service in the Windows registryOpen Registry Editor and navigate to HKLM\SYSTEM\CurrentControlSet\Services. Look for service entries related to Lenovo keyboard or USB keyboard drivers (commonly named something like 'LenovoUSBKeyboard' or 'SlimUsbKbd').Affected if A service entry matching the Lenovo USB Keyboard Driver exists in the services registry.
-
Examine the service binary path for quotingWith the service identified in the previous step, locate the 'ImagePath' value in the registry. View the data to see the full path to the service executable.Affected if The ImagePath value contains a file path with spaces that is NOT enclosed in quotation marks (for example, C:\Program Files\Lenovo\Driver\kbd.exe instead of "C:\Program Files\Lenovo\Driver\kbd.exe").
You are affected if the installed Lenovo USB Keyboard Driver version is 1.20 or earlier AND the service executable path in the Windows registry contains unquoted spaces, allowing potential path traversal exploitation.
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 dataUpdate the Lenovo USB Keyboard Driver to version 1.21 or later. Alternatively, ensure the service path in the Windows registry is properly quoted to prevent path traversal exploitation.
- Consultation2.0 h
- Implementation2.0 h
- Testing1.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,744.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2016-8225 — 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-2016-8225 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