# CVE-2017-3771: Security feature bypass in E95, ThinkCentre M710s/M710t

> Attackers can bypass BIOS/UEFI security controls on Lenovo E95 and ThinkCentre M710s/M710t due to incomplete factory initialization.

- **Severity:** High 7.5 (`CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 26 Oct 2017
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-vfh4-7jhx-g4cq

## What is CVE-2017-3771?

CVE-2017-3771 is a high-severity vulnerability in Lenovo Group Ltd. E95, ThinkCentre M710s/M710t, published on 26 Oct 2017. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

System boot process is not adequately secured In Lenovo E95 and ThinkCentre M710s/M710t because systems were shipped from factory without completing BIOS/UEFI initialization process.

## Which versions are affected by CVE-2017-3771?

It affects 3 products.


Products: Lenovo Aio E95 Firmware, Lenovo Thinkcentre M710s Firmware, Lenovo Thinkcentre M710t Firmware.

## How do I fix CVE-2017-3771?

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

## Is CVE-2017-3771 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2017-3771 and fix it if it is affected.

What it is: CVE-2017-3771 is a high-severity vulnerability in Lenovo Group Ltd. E95, ThinkCentre M710s/M710t, published on 26 Oct 2017. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2017-3771 in the wild and no public exploit code.

Affected product: Lenovo Group Ltd. E95, ThinkCentre M710s/M710t. 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-2017-3771/ (Markdown: https://insights.sbomify.com/CVE-2017-3771/index.md)
```

## Sources

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

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