# CVE-2016-5247: Security feature bypass in n/a

> Local or physically proximate attackers can bypass Secure Boot protection in Lenovo BIOS by leveraging an AMI test key.

- **Severity:** High 7.8 (`CVSS:3.0/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 22 Sep 2016
- **Updated:** 6 Aug 2024
- **Also known as:** GHSA-m3q5-wvc8-gpj3

## What is CVE-2016-5247?

CVE-2016-5247 is a high-severity vulnerability in n/a, published on 22 Sep 2016. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

The BIOS for Lenovo ThinkCentre E93, M6500t/s, M6600, M6600q, M6600t/s, M73p, M800, M83, M8500t/s, M8600t/s, M900, M93, and M93P devices; ThinkServer RQ940, RS140, TS140, TS240, TS440, and TS540 devices; and ThinkStation E32, P300, and P310 devices might allow local users or physically proximate attackers to bypass the Secure Boot protection mechanism by leveraging an AMI test key.

Weakness: CWE-254

## Which versions are affected by CVE-2016-5247?

It affects 1 product.


Products: Lenovo Bios.

## How do I fix CVE-2016-5247?

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

## Is CVE-2016-5247 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2021-3452](https://insights.sbomify.com/CVE-2021-3452/): Code injection in ThinkPad BIOS (medium 6.7)
- [CVE-2017-3754](https://insights.sbomify.com/CVE-2017-3754/): Security feature bypass in Lenovo Notebook BIOS (medium 6.7)
- [CVE-2016-8224](https://insights.sbomify.com/CVE-2016-8224/): Privilege escalation in Lenovo Notebook models 110-14IBR/110-15IBR, B70-80, E31-80, E40-80, E41-80, E51-80, G40-80, G50-80, G50-80 Touch, Ideapad 300-14IBR/300-15IBR, Ideapad 300-14ISK/300-15ISK/300-17ISK, Ideapad 510S-12ISK, K21-80, K41-80, MIIX 710-12IKB , XiaoXin Air 12, YOGA 510-14ISK/510-15ISK, YOGA 710-11IKB, Yoga 710-11ISK, Yoga 900-13ISK, YOGA 900S-12ISK; ThinkServer models ThinkServer TS150, ThinkServer TS450 (medium 4.4)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2016-5247 and fix it if it is affected.

What it is: CVE-2016-5247 is a high-severity vulnerability in n/a, published on 22 Sep 2016. 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-2016-5247 in the wild and no public exploit code.

Affected product: n/a. 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-2016-5247/ (Markdown: https://insights.sbomify.com/CVE-2016-5247/index.md)
```

## Sources

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

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