A potential vulnerability by a driver used during older manufacturing processes on some consumer Lenovo Notebook devices that was mistakenly
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: 1.2% (FIRST EPSS); higher than 68.7% of all records.
- 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 by a driver used during older manufacturing processes on some consumer Lenovo Notebook devices that was mistakenly included in the BIOS image could allow an attacker with elevated privileges to modify firmware protection region by modifying an NVRAM variable.
- Published
- Apr 22, 2022
- Updated
- Jun 17, 2026
- EPSS
- 1.2% · 68th percentile
- CWE
- CWE-489
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 · 1.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 | ideapad 3-14ada05 firmware | cpe:2.3:o:lenovo:ideapad_3-14ada05_firmware |
| lenovo | ideapad 3-14ada05 | cpe:2.3:h:lenovo:ideapad_3-14ada05 |
| lenovo | ideapad 3-14ada6 firmware | cpe:2.3:o:lenovo:ideapad_3-14ada6_firmware |
| lenovo | ideapad 3-14ada6 | cpe:2.3:h:lenovo:ideapad_3-14ada6 |
| lenovo | ideapad 3-14alc6 firmware | cpe:2.3:o:lenovo:ideapad_3-14alc6_firmware |
| lenovo | ideapad 3-14alc6 | cpe:2.3:h:lenovo:ideapad_3-14alc6 |
| lenovo | ideapad 3-14are05 firmware | cpe:2.3:o:lenovo:ideapad_3-14are05_firmware |
| lenovo | ideapad 3-14are05 | cpe:2.3:h:lenovo:ideapad_3-14are05 |
| lenovo | ideapad 3-15ada6 firmware | cpe:2.3:o:lenovo:ideapad_3-15ada6_firmware |
| lenovo | ideapad 3-15ada6 | cpe:2.3:h:lenovo:ideapad_3-15ada6 |
| lenovo | ideapad 3-15alc6 firmware | cpe:2.3:o:lenovo:ideapad_3-15alc6_firmware |
| lenovo | ideapad 3-15alc6 | cpe:2.3:h:lenovo:ideapad_3-15alc6 |
and 134 more
Affected versions
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- lenovo ideapad 3-14ada05 firmwarebefore e8cn33ww
- lenovo ideapad 3-14ada6 firmwarebefore hbcn21ww
- lenovo ideapad 3-14alc6 firmwarebefore glcn43ww
- lenovo ideapad 3-14are05 firmwarebefore dzcn42ww
- lenovo ideapad 3-14igl05 firmwarebefore emcn52ww
- lenovo ideapad 3-14iil05 firmwarebefore dvcn23ww
- lenovo ideapad 3-15ada05 firmwarebefore e8cn33ww
- lenovo ideapad 3-15ada6 firmwarebefore hbcn21ww
- lenovo ideapad 3-15alc6 firmwarebefore glcn43ww
- lenovo ideapad 3-15are05 firmwarebefore dzcn42ww
- lenovo ideapad 3-15igl05 firmwarebefore dvcn23ww
- lenovo ideapad 3-15iil05 firmwarebefore emcn52ww
- lenovo ideapad 3-17ada05 firmwarebefore e8cn33ww
- lenovo ideapad 3-17ada6 firmwarebefore hbcn21ww
- lenovo ideapad 3-17alc6 firmwarebefore glcn43ww
- lenovo ideapad 3-17are05 firmwarebefore dzcn42ww
- lenovo ideapad 3-17iil05 firmwarebefore emcn52ww
- lenovo ideapad 5-15are05 firmwarebefore e7cn44ww
- lenovo ideapad creator 5-15imh05 firmwarebefore egcn36ww
- lenovo ideapad gaming 3-15arh05 firmwarebefore fccn17ww
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 Notebook BIOS
- variousaffected
Same product
lenovo: all recordsOther highest-scoring records for the same primary product.
- CVE-2021-3972A potential vulnerability by a driver used during manufacturing process on some consumer Lenovo Notebook devices' BIOS that was mistakenly n27Monitor
- CVE-2021-3970A potential vulnerability in LenovoVariable SMI Handler due to insufficient validation in some Lenovo Notebook models BIOS may allow an atta26Monitor
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.
- Martin SmolárESET for reporting these issues.
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-489 · Active Debug CodeCVSS 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)
ATT&CK techniques
—
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.