CVE-2022-3431: A potential vulnerability in a driver used during manufacturing process on some consumer Lenovo Notebook devices that was mistakenly not dea
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.20% (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
A potential vulnerability in a driver used during manufacturing process on some consumer Lenovo Notebook devices that was mistakenly not deactivated may allow an attacker with elevated privileges to modify secure boot setting by modifying an NVRAM variable.
- Published
- Oct 9, 2023
- Updated
- Jun 17, 2026
- EPSS
- 0.2% · 10th percentile
- CWE
- CWE-276
Report tools
Action score
31
Monitor
Low priority for now.
- CVSS
- 31 / 40 · 7.8 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.2%
CISA SSVC decision
- Exploitation
- none
- Automatable
- no
- Technical impact
- total
Vulnrichment: CISA's decision-tree inputs.
CNA vs NVD score
- NVD
- 7.8
- CNA · lenovo
- 6.7
- 1.1 point gap
CVSS:3.1/AV:L/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H
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 creator 5-16ach6 firmware | cpe:2.3:o:lenovo:ideapad_creator_5-16ach6_firmware |
| lenovo | ideapad creator 5-16ach6 | cpe:2.3:h:lenovo:ideapad_creator_5-16ach6 |
| lenovo | ideapad 5 pro-16ihu6 firmware | cpe:2.3:o:lenovo:ideapad_5_pro-16ihu6_firmware |
| lenovo | ideapad 5 pro-16ihu6 | cpe:2.3:h:lenovo:ideapad_5_pro-16ihu6 |
| lenovo | ideapad 5 pro-16ach6 firmware | cpe:2.3:o:lenovo:ideapad_5_pro-16ach6_firmware |
| lenovo | ideapad 5 pro-16ach6 | cpe:2.3:h:lenovo:ideapad_5_pro-16ach6 |
| lenovo | yoga slim 7-13itl05 firmware | cpe:2.3:o:lenovo:yoga_slim_7-13itl05_firmware |
| lenovo | yoga slim 7-13itl05 | cpe:2.3:h:lenovo:yoga_slim_7-13itl05 |
| lenovo | yoga slim 7-13acn05 firmware | cpe:2.3:o:lenovo:yoga_slim_7-13acn05_firmware |
| lenovo | yoga slim 7-13acn05 | cpe:2.3:h:lenovo:yoga_slim_7-13acn05 |
| lenovo | yoga slim 7 pro 16arh7 firmware | cpe:2.3:o:lenovo:yoga_slim_7_pro_16arh7_firmware |
| lenovo | yoga slim 7 pro 16arh7 | cpe:2.3:h:lenovo:yoga_slim_7_pro_16arh7 |
and 38 more
Affected versions
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- lenovo d330-10igl firmwarebefore g0cn11ww
- lenovo ideapad 5 pro 16arh7 firmwarebefore j4cn33ww
- lenovo ideapad 5 pro-16ach6 firmwarebefore gscn34ww
- lenovo ideapad 5 pro-16ihu6 firmwarebefore grcn22ww
- lenovo ideapad creator 5-16ach6 firmwarebefore gscn34ww
- lenovo ideapad duet 3 10igl5 firmwarebefore eqcn37ww
- lenovo ideapad slim 7 pro 16ach6 firmwarebefore hucn16ww
- lenovo s540-15iml firmwarebefore cncn22ww
- lenovo slim 7 16arh7 firmwarebefore klcn15ww
- lenovo thinkbook 13x itg firmwarebefore hlcn30ww
- lenovo thinkbook 14 g4+ ara firmwarebefore j6cn40ww
- lenovo thinkbook 14 g4+ iap firmwarebefore hycn40ww
- lenovo thinkbook 16 g4+ ara firmwarebefore j6cn40ww
- lenovo thinkbook 16 g4+ iap firmwarebefore hycn40ww
- lenovo thinkbook 16p nx arh firmwarebefore kjcn27ww
- lenovo thinkbook plus g2 itg firmwarebefore gycn31ww
- lenovo thinkbook plus g3 iap firmwarebefore k6cn29ww
- lenovo yoga duet 7-13iml05 firmwarebefore ercn30ww
- lenovo yoga duet 7-13itl6 firmwarebefore gpcn24ww
- lenovo yoga duet 7-13itl6-lte firmwarebefore gpcn24ww
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 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.
- Martin SmolárESET for reporting these issues.finder
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.
- 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-276 · Incorrect Default PermissionsCVSS vector
CVSS:3.1/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.
Attack patterns (CAPEC)
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.