CVE-2017-3753
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 vulnerability has been identified in some Lenovo products that use UEFI (BIOS) code developed by American Megatrends, Inc. (AMI). With this vulnerability, conditions exist where an attacker with administrative privileges or physical access to a system may be able to run specially crafted code that can allow them to bypass system protections such as Device Guard and Hyper-V.
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 confidenceThis is a UEFI (BIOS) firmware vulnerability in Lenovo products using American Megatrends Inc. (AMI) code. An attacker with administrative privileges or physical access can execute specially crafted code to bypass Windows security protections such as Device Guard and Hyper-V, effectively circumventing virtualization-based security boundaries.
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 dataall versionsall versionsall versionsall versions= fckt78a= fckt78a= fckt78a= fckt78aCVSS 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
- Physical
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.0/AV:P/AC:L/PR:N/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 the Lenovo system modelRun 'wmic computersystem get model' or check the system documentation/label to confirm the exact model name (e.g., Ideacentre 300, Ideacentre 510s, H50, M4500)Affected if The model matches one listed in the affected products: Ideacentre 300, 300s, 510s, 700, 63, H50 30g, M4500, or M4500 Id
-
Check the installed UEFI BIOS versionRun 'wmic bios get smbiosbiosversion' from an administrative command prompt, or press F1/F2 during boot to enter UEFI setup and view the BIOS versionAffected if The version returned matches the affected version fckt78a (for 63, H50 30g, M4500 models) or is any version (for Ideacentre models listed as 'all versions')
-
Verify the BIOS vendor is American Megatrends Inc. (AMI)Run 'wmic bios get manufacturer' or check the BIOS setup screenAffected if The BIOS is manufactured by American Megatrends Inc. (AMI), as this CVE specifically affects AMI code in Lenovo firmware
A user is affected if they have one of the listed Lenovo models (Ideacentre 300/300s/510s/700, 63, H50 30g, M4500) with AMI UEFI firmware version fckt78a or, for Ideacentre models, any version of the affected firmware.
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 UEFI (BIOS) firmware to the latest version provided by Lenovo for the affected product. This is a firmware-level vulnerability that requires a BIOS update rather than configuration changes.
- Consultation4.0 h
- Implementation8.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 $5,120.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2017-3753 — 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-3753 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