# CVE-2020-8334: Security feature bypass in BIOS

> Attackers can bypass BIOS tamper detection on specific Lenovo ThinkPad models, potentially enabling unauthorized physical access to the device.

- **Severity:** Medium 6.1 (`CVSS:3.1/AV:P/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **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-9x9m-j8v4-cx96

## What is CVE-2020-8334?

CVE-2020-8334 is a medium-severity 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

The BIOS tamper detection mechanism was not triggered in Lenovo ThinkPad T495s, X395, T495, A485, A285, A475, A275 which may allow for unauthorized access.

Weakness: CWE-754 (Improper Check for Unusual or Exceptional Conditions)

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

It affects 7 products.


Products: Lenovo Thinkpad A275 Firmware, Lenovo Thinkpad A285 Firmware, Lenovo Thinkpad A475 Firmware, Lenovo Thinkpad A485 Firmware, Lenovo Thinkpad T495 Firmware, Lenovo Thinkpad T495s Firmware, Lenovo Thinkpad X395 Firmware.

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

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

## Is CVE-2020-8334 being exploited?

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

## Other vulnerabilities in Lenovo BIOS

- [CVE-2020-8335](https://insights.sbomify.com/CVE-2020-8335/): Security feature bypass in ThinkPad A285 BIOS (medium 6.1)

## Fix prompt for AI coding agents

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

What it is: CVE-2020-8334 is a medium-severity 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-8334 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-8334/ (Markdown: https://insights.sbomify.com/CVE-2020-8334/index.md)
```

## Sources

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

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