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

> Lenovo BIOS fails to detect SATA configuration changes, allowing attackers to bypass security controls intended to prevent unauthorized hardware modifications.

- **Severity:** Low 2.4 (`CVSS:3.1/AV:P/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N`)
- **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:** 11 Nov 2020
- **Updated:** 4 Aug 2024
- **Also known as:** GHSA-xvgf-q2mq-jv66

## What is CVE-2020-8352?

CVE-2020-8352 is a low-severity vulnerability in Lenovo BIOS, published on 11 Nov 2020. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

In some Lenovo Desktop models, the Configuration Change Detection BIOS setting failed to detect SATA configuration changes.

Weakness: CWE-358 (Improperly Implemented Security Check for Standard)

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

It affects 16 products.


Products: Lenovo Qitian 4500 Firmware, Lenovo Qitian B4550 Firmware, Lenovo Qitian M4550 Firmware, Lenovo Thinkcentre E73 Firmware, Lenovo Thinkcentre M4500k Firmware, Lenovo Thinkcentre M4500s Firmware, Lenovo Thinkcentre M4500t Firmware, Lenovo Thinkcentre M73 Firmware, Lenovo Yangtian Afh81 Firmware, Lenovo Yangtian Mc H81 Firmware, Lenovo Yangtian Mf Firmware, Lenovo Yangtian Ms Firmware, Lenovo Yangtian Tc Firmware, Lenovo Yangtian Wcc H81 Pci Firmware, Lenovo Yangtian Wf H81 Pci Firmware, Lenovo Yangtian Ws H81 Firmware.

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

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

## Is CVE-2020-8352 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2020-8352 is a low-severity vulnerability in Lenovo BIOS, published on 11 Nov 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-8352 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-8352/ (Markdown: https://insights.sbomify.com/CVE-2020-8352/index.md)
```

## Sources

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

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