Skip to content
Fencer Intel
medium 6.4

CVE-2020-8333 json

A potential vulnerability in the SMI callback function used in the EEPROM driver in some Lenovo Desktops and ThinkStation models may allow…

published 6y ago modified 4mo ago also EUVD-2020-29200

cvss
6.4
version 3.1, CNA
cisa kev
Not listed
not in CISA's catalog
epss
0.3%
EPSS 0.3% chance of exploitation in 30 days, percentile 26%
public exploits
0
none known

Summary

A potential vulnerability in the SMI callback function used in the EEPROM driver in some Lenovo Desktops and ThinkStation models may allow arbitrary code execution

Patch / fix

  • lenovo 63_firmware fckt98a
  • lenovo h50-30g_firmware fckt98a
  • lenovo m4500_firmware fckt98a
  • lenovo m4550_firmware fckt98a
  • lenovo qitian_4500_firmware fckt98a
  • lenovo qitian_b4550_firmware fckt98a
  • lenovo qitian_m4550_firmware fckt98a
  • lenovo thinkcentre_e73_firmware fckt98a
  • lenovo thinkcentre_e73s_firmware fckt98a
  • lenovo thinkcentre_m4500k_firmware fckt98a
  • lenovo thinkcentre_m4500q_firmware fhkt85a
  • lenovo thinkcentre_m4500t_firmware fckt98a
  • lenovo thinkcentre_m4500s_firmware fckt98a
  • lenovo yangtian_afh81_firmware fckt98a
  • lenovo yangtian_mc_h81_firmware fckt98a
  • lenovo yangtian_mf_h81_pci_firmware fckt98a
  • lenovo yangtian_wf_h81_pci_firmware fckt98a
  • lenovo yangtian_tc_h81_pci_firmware fckt98a
  • lenovo yangtian_wcc_h81_pci_firmware fckt98a
  • lenovo thinkcentre_m9350z_firmware fekta2a

Is CVE-2020-8333 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

Exploit prediction

0.33% chance of exploitation in the next 30 days, higher than 26% of all scored CVEs (FIRST EPSS, 2026-11-09).

CVSS scores

assigned by version score vector
CNA 3.1 6.4 CVSS:3.1/AV:L/AC:H/PR:H/UI:N/S:U/C:H/I:H/A:H
NVD 3.1 7.8 CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
NVD 2.0 7.2 AV:L/AC:L/Au:N/C:C/I:C/A:C

Affected products

  • Lenovo BIOS

References

Sources

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.