CVE-2021-3843: A potential vulnerability in the SMI function to access EEPROM in some ThinkPad models may allow an attacker with local access and elevated
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.27% (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
Primary sources: NVD · CVE.org · FIRST EPSS
A potential vulnerability in the SMI function to access EEPROM in some ThinkPad models may allow an attacker with local access and elevated privileges to execute arbitrary code.
- Published
- Nov 12, 2021
- Updated
- Jun 17, 2026
- EPSS
- 0.2% · 20th 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.2%
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.
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.
Running WordPress? Scan your site free with WP Lens
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 3rd gen firmware | cpe:2.3:o:lenovo:thinkpad_11e_3rd_gen_firmware |
| lenovo | thinkpad 11e 3rd gen | cpe:2.3:h:lenovo:thinkpad_11e_3rd_gen |
| lenovo | thinkpad 11e 4th gen i3 firmware | cpe:2.3:o:lenovo:thinkpad_11e_4th_gen_i3_firmware |
| lenovo | thinkpad 11e 4th gen i3 | cpe:2.3:h:lenovo:thinkpad_11e_4th_gen_i3 |
| lenovo | thinkpad 11e 4th gen i7 firmware | cpe:2.3:o:lenovo:thinkpad_11e_4th_gen_i7_firmware |
| lenovo | thinkpad 11e 4th gen i7 | cpe:2.3:h:lenovo:thinkpad_11e_4th_gen_i7 |
| lenovo | thinkpad 11e 4th gen i5 firmware | cpe:2.3:o:lenovo:thinkpad_11e_4th_gen_i5_firmware |
| lenovo | thinkpad 11e 4th gen i5 | cpe:2.3:h:lenovo:thinkpad_11e_4th_gen_i5 |
| lenovo | thinkpad 11e 4th gen celeron firmware | cpe:2.3:o:lenovo:thinkpad_11e_4th_gen_celeron_firmware |
| lenovo | thinkpad 11e 4th gen celeron | cpe:2.3:h:lenovo:thinkpad_11e_4th_gen_celeron |
| lenovo | thinkpad 11e yoga gen 6 firmware | cpe:2.3:o:lenovo:thinkpad_11e_yoga_gen_6_firmware |
| lenovo | thinkpad 11e yoga gen 6 | cpe:2.3:h:lenovo:thinkpad_11e_yoga_gen_6 |
and 47 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 3rd gen firmwareup to 1.29 inclusive
- lenovo thinkpad 11e 3rd gen firmwareup to 1.22 inclusive
- lenovo thinkpad 11e 4th gen celeron firmwareup to 1.27 inclusive
- lenovo thinkpad 11e 4th gen i3 firmwareup to 1.22 inclusive
- lenovo thinkpad 11e 4th gen i5 firmwareup to 1.22 inclusive
- lenovo thinkpad 11e 4th gen i7 firmwareup to 1.22 inclusive
- lenovo thinkpad 11e 5th gen firmwareup to 1.13 inclusive
- lenovo thinkpad 11e yoga gen 6 firmwareup to 1.12 inclusive
- lenovo thinkpad 13 gen 2 firmwareup to 1.29 inclusive
- lenovo thinkpad l13 firmwareup to 1.31 inclusive
- lenovo thinkpad l13 gen 2 firmwareup to 1.11 inclusive
- lenovo thinkpad l13 gen 2 firmwareup to 1.08 inclusive
- lenovo thinkpad l13 yoga firmwareup to 1.31 inclusive
- lenovo thinkpad l13 yoga gen 2 firmwareup to 1.11 inclusive
- lenovo thinkpad l13 yoga gen 2 firmwareup to 1.08 inclusive
- lenovo thinkpad l14 firmwarebefore 1.20.1.17
- lenovo thinkpad l14 gen 1 firmwarebefore 1.15
- lenovo thinkpad l15 firmwarebefore 1.20.1.17
- lenovo thinkpad l15 gen 1 firmwarebefore 1.15
- lenovo thinkpad l380 firmwareup to 1.26 inclusive
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
Same product
lenovo: all recordsOther highest-scoring records for the same primary product.
- CVE-2021-3718A denial of service vulnerability was reported in some ThinkPad models that could cause a system to crash when the Enhanced Biometrics setti18Monitor
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.
No history yet (it accumulates with the daily EPSS job).
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.
- Jiawei Yin(@yngweijw) and Menghao LiIIE varas
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.