CVE-2020-8322
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 SMI callback function used in the Legacy USB driver in some Lenovo Notebook and ThinkStation models may allow arbitrary code execution.
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 vulnerability exists in the SMI (System Management Interface) callback function within the Legacy USB driver on affected Lenovo Notebook and ThinkStation systems. The flaw may allow an attacker to execute arbitrary code by exploiting the SMI callback, which operates at a privileged level below the OS.
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 versionsall versionsall versionsall versionsall versionsCVSS 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
- High
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:L/AC:L/PR:H/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 your Lenovo modelRun 'systeminfo' (Windows) or check /sys/class/dmi/id/modalias (Linux) or check the physical product label to confirm the exact model number (e.g., 330 14ast, 340c 15api, 720s 15ikb, 730s 13iwl)Affected if The model matches one of the affected products: Lenovo 330 14ast, 330 15ast, 330 17ast, 340c 15api, 340c 15ast, 720s Touch 15ikb, 720s 15ikb, or 730s 13iwl
-
Check the firmware versionAccess the BIOS/UEFI setup (press Enter or F1 during boot) and navigate to the Information or Version section, or run 'wmic bios get smbiosbiosversion' (Windows) or check /sys/class/dmi/id/bios_version (Linux)Affected if The system is any of the affected models listed - note that all firmware versions for these models are vulnerable
-
Locate Legacy USB setting in BIOS/UEFIRestart the system and enter BIOS/UEFI setup (typically F1, F2, or Del key). Navigate to the 'Advanced', 'USB', or 'Integrated Peripherals' menu and look for 'Legacy USB Support', 'Legacy USB', or 'USB Legacy Mode'Affected if A Legacy USB setting exists and is available in the BIOS/UEFI configuration
-
Determine if Legacy USB is enabledIn the BIOS/UEFI Legacy USB setting identified in the previous step, verify whether it is set to 'Enabled', 'Auto', or 'On'Affected if Legacy USB support is enabled, auto, or on - this configuration enables the vulnerable SMI callback in the Legacy USB driver
You are affected if you own any of the listed Lenovo models (330 series, 340c, 720s, 730s) and have Legacy USB support enabled in your BIOS/UEFI settings.
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 dataApply the Lenovo firmware update provided for affected models. If immediate patching is not possible, consider disabling Legacy USB support in BIOS/UEFI settings as a compensating control.
- Consultation4.0 h
- Implementation2.0 h
- Testing3.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,152.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2020-8322 — 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-2020-8322 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