# CVE-2020-8321: Code injection in BIOS

> A vulnerability in the Lenovo BIOS System Lock Preinstallation driver allows arbitrary code execution via SMI callback functions.

- **Severity:** Medium 6.4 (`CVSS:3.1/AV:L/AC:H/PR:H/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 9 Jun 2020
- **Updated:** 17 Sep 2024
- **Also known as:** GHSA-7939-9jcj-5hqr

## What is CVE-2020-8321?

CVE-2020-8321 is a medium-severity code injection vulnerability in Lenovo BIOS, published on 9 Jun 2020. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

A potential vulnerability in the SMI callback function used in the System Lock Preinstallation driver in some Lenovo Notebook and ThinkStation models may allow arbitrary code execution.

## Which versions are affected by CVE-2020-8321?

It affects 172 products.


Products: Lenovo 130-14ast Firmware, Lenovo 130-14ikb Firmware, Lenovo 130-15ast Firmware, Lenovo 130-15ikb Firmware, Lenovo 320c-15ikb Firmware, Lenovo 330-14igm Firmware, Lenovo 330-14ikb Firmware, Lenovo 330-14ikbr Firmware, Lenovo 330-15arr Firmware, Lenovo 330-15arr Touch Firmware, Lenovo 330-15ich Firmware, Lenovo 330-15igm Firmware, Lenovo 330-15ikb Firmware, Lenovo 330-15ikbr Firmware, Lenovo 330-15ikbr Touch Firmware, Lenovo 330-17ich Firmware, Lenovo 330-17ikb Firmware, Lenovo 330-17ikbr Firmware, Lenovo 330c-14ikb Firmware, Lenovo 330c-15ikb Firmware and 152 more.

## How do I fix CVE-2020-8321?

No fix has been published for CVE-2020-8321 yet. Limit exposure of the affected software until one is available.

## Is CVE-2020-8321 being exploited?

There is no known exploitation of CVE-2020-8321 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2020-8321 and fix it if it is affected.

What it is: CVE-2020-8321 is a medium-severity code injection vulnerability in Lenovo BIOS, published on 9 Jun 2020. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2020-8321 in the wild and no public exploit code.

Affected product: Lenovo BIOS. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2020-8321/ (Markdown: https://insights.sbomify.com/CVE-2020-8321/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2020-8321
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2020-8321
- OSV: https://osv.dev/vulnerability/CVE-2020-8321

---
From sbomify Insights: https://insights.sbomify.com/CVE-2020-8321/
Summaries are generated and may contain mistakes; the official description above is the record.