CVE-2020-8341 json
In Lenovo systems, SMM BIOS Write Protection is used to prevent writes to SPI Flash.
published 6y ago modified 4mo ago also EUVD-2020-29208
- cvss
- 2.4
- version 3.1, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.3%
- EPSS 0.3% chance of exploitation in 30 days, percentile 28%
- public exploits
- 0
- none known
Summary
In Lenovo systems, SMM BIOS Write Protection is used to prevent writes to SPI Flash. While this provides sufficient protection, an additional layer of protection is provided by SPI Protected Range Registers (PRx). After resuming from S3 sleep mode in various versions of BIOS for some Lenovo ThinkPad systems, the PRx is not set. This does not impact the SMM BIOS Write Protection, which keeps systems protected.
Patch / fix
- lenovo thinkpad_t490_(20nx)_firmware n2iet90w
- lenovo thinkpad_t490_(20qx)_firmware n2iet90w
- lenovo thinkpad_t490_(20rx)_firmware n2ret16w
- lenovo thinkpad_t490s_(20nx)_firmware n2jet89w
- lenovo thinkpad_t495_drift_firmware 2020-08-30
- lenovo thinkpad_t590_(20nx)_firmware n2iet90w
- lenovo thinkpad_x1_carbon_(20qx)_firmware n2het54w
- lenovo thinkpad_x1_yoga_(20qx)_firmware n2het54w
- lenovo thinkpad_x390_(20qx)_firmware n2jet89w
- lenovo thinkpad_x390_(20sx)_firmware n2set18w
Is CVE-2020-8341 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 FencerExploit prediction
0.35% chance of exploitation in the next 30 days, higher than 28% of all scored CVEs (FIRST EPSS, 2026-11-09).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 3.1 | 2.4 | CVSS:3.1/AV:P/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N |
| NVD | 2.0 | 2.1 | AV:L/AC:L/Au:N/C:N/I:P/A:N |
Affected products
- Lenovo ThinkPad
References
-
support.lenovo.com
/us/en/product_security/LEN-30042
vendor-advisory
Sources
- CVE List CVE-2020-8341
- NVD CVE-2020-8341
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.