BIOS Modules Unprotected by Intel Boot Guard Vulnerable to Physical Attack
In some Lenovo ThinkPad products, one BIOS region is not properly included in the checks, allowing injection of arbitrary code.
- Published
- Jul 19, 2018
- Updated
- Jun 16, 2026
- EPSS
- 0.5% · 42th percentile
- CWE
- CWE-74
Sign in to follow · You’ll be notified if a followed record enters KEV, gets an exploit or is updated.
Report tools
Action score
27
Monitor
Low priority for now.
- CVSS
- 27 / 40 · 6.8 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.5%
Affected systems
| Vendor | Product | CPE |
|---|---|---|
| lenovo | e42-80 firmware | cpe:2.3:o:lenovo:e42-80_firmware |
| lenovo | e42-80 | cpe:2.3:h:lenovo:e42-80 |
| lenovo | e42-80 isk firmware | cpe:2.3:o:lenovo:e42-80_isk_firmware |
| lenovo | e42-80 isk | cpe:2.3:h:lenovo:e42-80_isk |
| lenovo | e52-80 firmware | cpe:2.3:o:lenovo:e52-80_firmware |
| lenovo | e52-80 | cpe:2.3:h:lenovo:e52-80 |
| lenovo | e52-80 isk firmware | cpe:2.3:o:lenovo:e52-80_isk_firmware |
| lenovo | e52-80 isk | cpe:2.3:h:lenovo:e52-80_isk |
| lenovo | miix 720-12ikb firmware | cpe:2.3:o:lenovo:miix_720-12ikb_firmware |
| lenovo | miix 720-12ikb | cpe:2.3:h:lenovo:miix_720-12ikb |
| lenovo | v310-14ikb firmware | cpe:2.3:o:lenovo:v310-14ikb_firmware |
| lenovo | v310-14ikb | cpe:2.3:h:lenovo:v310-14ikb |
and 85 more
Affected versions
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- lenovo e42-80 firmwarebefore 2wcn40ww
- lenovo e42-80 isk firmwarebefore 0zcn48ww
- lenovo e52-80 firmwarebefore 2wcn40ww
- lenovo e52-80 isk firmwarebefore 0zcn48ww
- lenovo miix 720-12ikb firmwarebefore 3scn68ww
- lenovo thinkpad e480 firmwarebefore r0pet47w
- lenovo thinkpad e580 firmwarebefore r0pet47w
- lenovo thinkpad l380 firmwarebefore r0ret28w
- lenovo thinkpad l480 firmwarebefore r0qet47w
- lenovo thinkpad l580 firmwarebefore r0qet47w
- lenovo thinkpad p51 firmwarebefore n1uet71w
- lenovo thinkpad p51s firmwarebefore n1vet45w
- lenovo thinkpad p52 firmwarebefore n2cet28w
- lenovo thinkpad p52s firmwarebefore n27et27w
- lenovo thinkpad p71 firmwarebefore n1tet50w
- lenovo thinkpad p72 firmwarebefore n2cet28w
- lenovo thinkpad s1 firmwarebefore r0het48w
- lenovo thinkpad t25 firmwarebefore n1qet77w
- lenovo thinkpad t470 firmwarebefore n1qet77w
- lenovo thinkpad t470p firmwarebefore r0fet44w
Versions reported by the vendor
Affected version ranges reported by the assigning authority (lenovo). Independent of NVD's CPE analysis and usually ahead of it.
Lenovo Group Ltd. some Lenovo ThinkPads
- variousaffected
Same product
lenovo: all recordsOther highest-scoring records for the same primary product.
- CVE-2018-9069BIOS Write Protection Race Condition23Monitor
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.
FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).
Patch and commit links
Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.
No commit or PR link among the references.
Credits
All researchersFinders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.
No credits in the CNA record.
Variant candidates
Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.
No nightly-computed relations.
Chain candidates
An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.
—
Bug bounty scope
No known public program.
Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).
Technical details
Attack conditions
- Physical access to the device is required.
- No account or password is required.
- 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
- Physical
- Attack complexity
- Low
- Privileges required
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality impact
- High
- Integrity impact
- High
- Availability impact
- High
Weakness class (CWE)
CWE-74 · Improper Neutralization of Special Elements in Output Used by a Downstream Component ('Injection')CVSS vector
CVSS:3.1/AV:P/AC:L/PR:N/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.
Attack patterns (CAPEC)
- Buffer Overflow via Environment VariablesCAPEC-10likelihood: High · High
- Server Side Include (SSI) InjectionCAPEC-101likelihood: High · High
- HTTP Request SplittingCAPEC-105likelihood: Medium · High
- Command Line Execution through SQL InjectionCAPEC-108likelihood: Low · Very High
- Double EncodingCAPEC-120likelihood: Low · Medium
- Subverting Environment Variable ValuesCAPEC-13likelihood: High · Very High
- Format String InjectionCAPEC-135likelihood: High · High
- Client-side Injection-induced Buffer OverflowCAPEC-14likelihood: Medium · High
Noroxi analysis
No Noroxi analysis for this record yet
We don't hand-write analysis for all 385,000+ vulnerabilities; that wouldn't be honest. For notable, high-impact vulnerabilities our team writes the mechanism, detection and remediation steps.
We use this product, ask for helpChange log
No changes recorded on tracked fields yet. Score, KEV, exploit maturity and fix status changes appear here.
References
Vendor advisories and official records. Exploit/PoC links are deliberately left out.