LiveActive security incident?Get immediate response
CVE Record

CVE-2020-8354: A potential vulnerability in the SMI callback function used in the VariableServiceSmm driver in some Lenovo...

A potential vulnerability in the SMI callback function used in the VariableServiceSmm driver in some Lenovo Notebook models may allow arbitrary code execution.

MediumCVSS 6.4Not KEV-listedUpdated
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

This is a Lenovo notebook firmware issue. A privileged local attacker may be able to exploit a race condition in BIOS SMM code to execute arbitrary code below the operating system. Business urgency is moderate because exploitation requires high privileges and high complexity, but successful compromise could affect confidentiality, integrity, and availability at a deep firmware layer.

Executive priority

Treat this as a moderate-priority firmware hygiene issue. It is not shown as actively exploited, but the potential impact is severe if an attacker already has privileged local access on an affected Lenovo notebook.

Technical view

CVE-2020-8354 is a CWE-367 time-of-check/time-of-use issue in the SMI callback function used by Lenovo's VariableServiceSmm BIOS driver. CVSS 3.1 is 6.4: local attack vector, high complexity, high privileges required, no user interaction, unchanged scope, and high CIA impact.

Likely exposure

Exposure is limited to some Lenovo Notebook models with affected BIOS firmware. The provided bundle does not identify exact models or vulnerable BIOS versions, so asset teams must compare device model and firmware version against Lenovo advisory LEN-49266.

Exploitation context

The CVE is not listed as CISA KEV in the bundle, and no cited source states active exploitation. The privilege requirement suggests this is most relevant after local compromise or insider misuse, not broad remote exploitation.

Researcher notes

Evidence is incomplete for exact affected models, fixed versions, and proof-of-concept status. Avoid assuming exploit availability. Validation should focus on firmware inventory, Lenovo advisory mapping, and whether local privilege controls reduce realistic attack paths.

Mitigation direction

  • Check Lenovo advisory LEN-49266 for affected notebook models and BIOS guidance.
  • Update applicable Lenovo notebook BIOS firmware using vendor-approved packages.
  • Prioritize systems used by administrators, executives, developers, and high-risk remote users.
  • Limit local administrator rights on Lenovo notebooks where feasible.
  • Track firmware update completion in asset or endpoint management records.

Validation and detection

  • Inventory Lenovo notebook model numbers and current BIOS versions.
  • Compare each device against Lenovo LEN-49266 applicability criteria.
  • Verify updated BIOS version after remediation completes.
  • Confirm firmware update process uses trusted vendor channels.
  • Review privileged local access exposure on affected notebooks.
Prepared
Confidence
medium
Sources
3

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cwe · low confidence lookup

CWE-367: Exact CWE lookup

Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.

Open ATT&CK lookup
description · low confidence lookup

Execution behavior lookup

The CVE wording references code or command execution, so execution technique review may help defensive triage. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2020-8354 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Medium
CVSS
6.4 (3.1)
Known Exploited
No
Published

Vector: CVSS:3.1/AV:L/AC:H/PR:H/UI:N/S:U/C:H/I:H/A:H

Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

1CVSS vectors
0Timeline events
0ADP providers
2Source links

CVSS vector scores

1 official score

We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.

ScoreVersionSeverityVectorExploitImpactSource
6.4CVSS 3.1MediumCVSS:3.1/AV:L/AC:H/PR:H/UI:N/S:U/C:H/I:H/A:H0.55.9Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

6.4Medium
CVSS 3.1 vector shape for CVE-2020-8354Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

Vector: CVSS:3.1/AV:L/AC:H/PR:H/UI:N/S:U/C:H/I:H/A:H

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Privileges Required
NoneLowHigh
User Interaction
NoneRequired
Scope
ChangedUnchanged
Confidentiality Impact
HighLowNone
Integrity Impact
HighLowNone
Availability Impact
HighLowNone

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
LenovoBIOSunspecifiedListed
Weakness

CWE details

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.

CWE-367 · source CWE mapping

Time-of-check Time-of-use (TOCTOU) Race Condition

Time-of-check Time-of-use (TOCTOU) Race Condition represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.