CVE-2017-3740
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 · uneditedIn Lenovo Active Protection System before 1.82.0.14, an attacker with local privileges could send commands to the system's embedded controller, which could cause a denial of service attack on the system or the ability to alter hardware functionality.
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 confidenceLenovo Active Protection System before version 1.82.0.14 contains a vulnerability where an attacker with local system privileges can send arbitrary commands to the system's embedded controller. This could result in denial of service or modification of hardware functionality.
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.00b= 1.01b= 1.20b= 1.21= 1.22= 1.23= 1.30b= 1.31= 1.32= 1.33b= 1.34= 1.40CVSS 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
- None
- Integrity
- None
- Availability
- High
CVSS:3.0/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/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.
-
Find installed Lenovo Active Protection System versionOpen Windows Control Panel > Programs and Features, or right-click the Lenovo Active Protection System executable and select Properties > Details to view the version fieldAffected if The version listed is 1.00b, 1.01b, 1.20b, 1.21, 1.22, 1.23, 1.30b, 1.31, 1.32, 1.33b, 1.34, or 1.40
-
Check registry for version informationOpen Registry Editor and navigate to HKLM\SOFTWARE\Lenovo\Lenovo Active Protection System or HKLM\SOFTWARE\WOW6432Node\Lenovo\Lenovo Active Protection System, then locate the Version valueAffected if The Version value matches any of the affected versions listed above (1.00b through 1.40)
-
Verify user privilege contextDetermine if untrusted users or processes on the system have local system or administrator privileges, as the vulnerability requires the attacker to possess local system-level privileges to exploit the embedded controllerAffected if Untrusted accounts or processes have local system or administrative access on the machine
A system is affected if Lenovo Active Protection System is installed with any version from 1.00b through 1.40 AND an untrusted user or process possesses local system or administrator privileges on that machine.
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 dataUpgrade Lenovo Active Protection System to version 1.82.0.14 or later to remediate this vulnerability.
- Consultation4.0 h
- Implementation2.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,392.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2017-3740 — 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-2017-3740 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