CVE-2016-5247: The BIOS for Lenovo ThinkCentre E93, M6500t/s, M6600, M6600q, M6600t/s, M73p, M800, M83, M8500t/s, M8600t/s, M900, M93, and M93P devices…
Noroxi assessment
Priority: Monitor (action score 31/100)
- The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
- Probability of exploitation in the next 30 days: 0.37% (FIRST EPSS).
- Someone with local access to the system can trigger it. A low-privileged account is enough. No user action is required. No special conditions are required; it is repeatable.
- According to the record, no fixed version is available yet.
Low priority for now. Update when a fix is released; follow the vendor's advisory.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
Primary sources: NVD · CVE.org · FIRST EPSS
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.
- Published
- Sep 22, 2016
- Updated
- Jun 16, 2026
- EPSS
- 0.3% · 32th percentile
- CWE
- CWE-254
Report tools
Action score
31
Low priority for now.
- CVSS
- 31 / 40 · 7.8 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.3%
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- No public exploit code on record
- No fixed version yet
If any of these changes, we'll tell you in the daily email digest.
Is your version affected? Check itNoroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
| Vendor | Product | CPE |
|---|---|---|
| lenovo | bios | cpe:2.3:o:lenovo:bios |
| lenovo | thinkcentre e93 | cpe:2.3:h:lenovo:thinkcentre_e93 |
| lenovo | thinkcentre m6500t\/s | cpe:2.3:h:lenovo:thinkcentre_m6500t\/s |
| lenovo | thinkcentre m6600 | cpe:2.3:h:lenovo:thinkcentre_m6600 |
| lenovo | thinkcentre m6600q | cpe:2.3:h:lenovo:thinkcentre_m6600q |
| lenovo | thinkcentre m6600t\/s | cpe:2.3:h:lenovo:thinkcentre_m6600t\/s |
| lenovo | thinkcentre m73p | cpe:2.3:h:lenovo:thinkcentre_m73p |
| lenovo | thinkcentre m800 | cpe:2.3:h:lenovo:thinkcentre_m800 |
| lenovo | thinkcentre m83 | cpe:2.3:h:lenovo:thinkcentre_m83 |
| lenovo | thinkcentre m8500t\/s | cpe:2.3:h:lenovo:thinkcentre_m8500t\/s |
| lenovo | thinkcentre m8600t\/s | cpe:2.3:h:lenovo:thinkcentre_m8600t\/s |
| lenovo | thinkcentre m900 | cpe:2.3:h:lenovo:thinkcentre_m900 |
and 11 more
Affected versions
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- lenovo biosall versions
Same product
lenovo: all recordsOther highest-scoring records for the same primary product.
- CVE-2023-25493A potential vulnerability was reported in the BIOS update tool driver for some Desktop, Smart Edge, Smart Office, and ThinkStation products…26Monitor
- CVE-2021-3452A potential vulnerability in the system shutdown SMI callback function in some ThinkPad models may allow an attacker with local access and…26Monitor
- CVE-2017-3754Some Lenovo brand notebook systems do not have write protections properly configured in the system BIOS.26Monitor
Published before and after this one in the same product
- Later →CVE-2016-8224Nov 29, 2016 · A vulnerability has been identified in some Lenovo Notebook and ThinkServer systems where an attacker with administrative privileges on a…17Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
No fix version is recorded for this entry. Check the references for vendor advisories.
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
No dated events beyond publication.
Not on record for this CVE: EPSS history · patch commit or PR link · researcher credit · variant or chain candidate · public bounty program.
Technical details
Attack conditions
- Someone with local access to the system can trigger it.
- A low-privileged account is enough.
- No user action is required.
- No special conditions are required; it is repeatable.
If successful
- Confidentiality
- high · data can be read
- Integrity
- high · data or configuration can be modified
- Availability
- high · the service can be disrupted
- Attack vector
- Local
- Attack complexity
- Low
- Privileges required
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality impact
- High
- Integrity impact
- High
- Availability impact
- High
Weakness class (CWE)
CWE-254 · 7PK - Security FeaturesCVSS vector
CVSS:3.0/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
nvd-primary
Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
MITRE has no CAPEC/ATT&CK mapping for this CWE.
Change log (0)
No changes recorded on tracked fields yet. Score, KEV, exploit maturity and fix status changes appear here.
References
Show all references (1 more)Show less
Vendor advisories and official records. Exploit/PoC links are deliberately left out.