During an internal product security audit a potential vulnerability due to use of Boot Services in the SmmOEMInt15 SMI handler was discovere
Noroxi assessment
Priority: Monitor (action score 26/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.26% (FIRST EPSS).
- Someone with local access to the system can trigger it. Administrator privileges are required. 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
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
Follow it and we'll tell you in the daily email digest when the record enters KEV, gets exploit code, is updated (including a fix) or its EPSS rises 20 points in a week. Connect a webhook and KEV listings and weaponized exploits arrive instantly.
Is your version affected? Check itDuring an internal product security audit a potential vulnerability due to use of Boot Services in the SmmOEMInt15 SMI handler was discovered in some ThinkPad models could be exploited by an attacker with elevated privileges that could allow for execution of code.
- Published
- Apr 22, 2022
- Updated
- Jun 17, 2026
- EPSS
- 0.3% · 18th percentile
- CWE
- CWE-20
Report tools
Action score
26
Monitor
Low priority for now.
- CVSS
- 26 / 40 · 6.7 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.3%
CNA vs NVD score
- NVD
- 6.7
- CNA · lenovo
- 6.7
- agree
The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.
Noroxi 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 | thinkpad 11e firmware | cpe:2.3:o:lenovo:thinkpad_11e_firmware |
| lenovo | thinkpad 11e | cpe:2.3:h:lenovo:thinkpad_11e |
| lenovo | thinkpad helix firmware | cpe:2.3:o:lenovo:thinkpad_helix_firmware |
| lenovo | thinkpad helix | cpe:2.3:h:lenovo:thinkpad_helix |
| lenovo | thinkpad l560 firmware | cpe:2.3:o:lenovo:thinkpad_l560_firmware |
| lenovo | thinkpad l560 | cpe:2.3:h:lenovo:thinkpad_l560 |
| lenovo | thinkpad l570 firmware | cpe:2.3:o:lenovo:thinkpad_l570_firmware |
| lenovo | thinkpad l570 | cpe:2.3:h:lenovo:thinkpad_l570 |
| lenovo | thinkpad p50s firmware | cpe:2.3:o:lenovo:thinkpad_p50s_firmware |
| lenovo | thinkpad p50s | cpe:2.3:h:lenovo:thinkpad_p50s |
| lenovo | thinkpad p51s firmware | cpe:2.3:o:lenovo:thinkpad_p51s_firmware |
| lenovo | thinkpad p51s | cpe:2.3:h:lenovo:thinkpad_p51s |
and 48 more
Affected versions
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- lenovo thinkpad 11e firmwarebefore n15et78w
- lenovo thinkpad 11e yoga firmwarebefore n15et78w
- lenovo thinkpad helix firmwarebefore n17eta8w
- lenovo thinkpad l560 firmwarebefore n1het85w
- lenovo thinkpad l570 firmwarebefore n1xet65w
- lenovo thinkpad p50s firmwarebefore n1ket46w
- lenovo thinkpad p51s firmwarebefore n1vet50w
- lenovo thinkpad p52s firmwarebefore n27et36w
- lenovo thinkpad s540 firmwarebefore gpet80ww
- lenovo thinkpad t550 firmwarebefore n11et50w
- lenovo thinkpad t560 firmwarebefore n1ket46w
- lenovo thinkpad t570 firmwarebefore n1vet50w
- lenovo thinkpad t580 firmwarebefore n27et36w
- lenovo thinkpad w540 firmwarebefore gnet92ww
- lenovo thinkpad w541 firmwarebefore gnet92ww
- lenovo thinkpad w550s firmwarebefore n11et50w
- lenovo thinkpad x1 carbon 3rd gen firmwarebefore n14et52w
- lenovo thinkpad x1 carbon 4th gen firmwarebefore n1fet70w
- lenovo thinkpad x1 carbon 5th gen kabylake firmwarebefore n1met55w
- lenovo thinkpad x1 carbon 5th gen skylake firmwarebefore n1met55w
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 ThinkPad BIOS
- variousaffected
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
- Someone with local access to the system can trigger it.
- Administrator privileges are 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
- Local
- Attack complexity
- Low
- Privileges required
- High
- User interaction
- None
- Scope
- Unchanged
- Confidentiality impact
- High
- Integrity impact
- High
- Availability impact
- High
Weakness class (CWE)
CWE-20 · Improper Input ValidationCVSS vector
CVSS:3.1/AV:L/AC:L/PR:H/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
- Cross Zone ScriptingCAPEC-104likelihood: Medium · High
- Command Line Execution through SQL InjectionCAPEC-108likelihood: Low · Very High
- Object Relational Mapping InjectionCAPEC-109likelihood: Low · High
- SQL Injection through SOAP Parameter TamperingCAPEC-110likelihood: High · Very High
- Double EncodingCAPEC-120likelihood: Low · Medium
- Subverting Environment Variable ValuesCAPEC-13likelihood: High · Very High
ATT&CK techniques
- Obfuscated Files or InformationT1027
- Masquerading: Invalid Code SignatureT1036.001
- Steal Web Session CookieT1539
- Subvert Trust Controls: Code SigningT1553.002
- Impair Defenses:Impair Command History LoggingT1562.003
- Hijack Execution Flow:Dynamic Linker HijackingT1574.006
- Hijack Execution Flow:Path Interception by PATH Environment VariableT1574.007
Change 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.