dbcve.org
D330 10igl FirmwareOperating system · Lenovo

CVE-2022-3430

MEDIUM · 6.7 CVSS v3.1 Published 2023-01-23
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
69/100
Remediation priority · Elevated
Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
A potential vulnerability in the WMI Setup driver on some consumer Lenovo Notebook devices may allow an attacker with elevated privileges to modify secure boot setting by modifying an NVRAM variable.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · moderate confidence

The WMI Setup driver on certain consumer Lenovo Notebook devices contains a vulnerability allowing an attacker with elevated privileges to modify NVRAM variables, specifically targeting secure boot settings. This represents a privilege escalation issue where an already-privileged attacker can compromise the firmware-level security mechanism that ensures only trusted operating system loaders can execute.

MitigationApply Lenovo firmware/BIOS updates for affected notebook models once available. Verify secure boot is enabled in UEFI settings and ensure physical security to prevent unauthorized local access.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
D330 10igl FirmwareOperating system
Affected:< g0cn11ww
Ideapad 5 Pro 16iah7 FirmwareOperating system
Affected:< j4cn33ww
Ideapad 5 Pro 16arh7 FirmwareOperating system
Affected:< j5cn27ww
Ideapad Duet 3 10igl5 FirmwareOperating system
Affected:< eqcn37ww
Slim 7 16arh7 FirmwareOperating system
Affected:< klcn15ww
Thinkbook 15p Imp FirmwareOperating system
Affected:< f6cn25ww
Slim 7 14are05 FirmwareOperating system
Affected:< dmcn43ww
Ideapad Slim 7 14iil05 FirmwareOperating system
Affected:< dhcn35ww

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Local
Complexity
Low
Privileges
High
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:L/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify your Lenovo notebook model
    Check the device label on the bottom of the notebook, or run 'wmic computersystem get model' in Command Prompt
    Affected if Your model matches one of the affected products: D330 10igl, Ideapad 5 Pro 16iah7, Ideapad 5 Pro 16arh7, Ideapad Duet 3 10igl5, Slim 7 16arh7, Thinkbook 15p Imp, Slim 7 14are05, or Ideapad Slim 7 14iil05
  2. Determine your current firmware version
    Enter UEFI/BIOS setup by pressing F2 or Delete during boot, then locate the BIOS/UEFI version information. Alternatively, run 'wmic bios get smbiosbiosversion' in Command Prompt
    Affected if The installed firmware version is below the safe threshold for your specific model (see version list)
  3. Compare your firmware version against affected ranges
    Match your model and firmware version to the following thresholds: D330 10igl requires g0cn11ww or higher; Ideapad 5 Pro 16iah7 requires j4cn33ww or higher; Ideapad 5 Pro 16arh7 requires j5cn27ww or higher; Ideapad Duet 3 10igl5 requires eqcn37ww or higher; Slim 7 16arh7 requires klcn15ww or higher; Thinkbook 15p Imp requires f6cn25ww or higher; Slim 7 14are05 requires dmcn43ww or higher; Ideapad Slim 7 14iil05 requires dhcn35ww or higher
    Affected if Your current firmware version is LOWER than the required version for your model
  4. Verify if the WMI Setup driver is present
    Open Device Manager, expand 'System devices', and look for a driver named 'Lenovo WMI Setup Driver' or similar WMI-related entries. Alternatively, check 'wmic service list brief' for WMI-related services
    Affected if The WMI Setup driver is installed and present on the system (required for the vulnerability to be exploitable)

Your environment is affected if you have one of the listed Lenovo notebook models AND your current firmware version is below the specified threshold AND the WMI Setup driver is present on your system.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Apply Lenovo firmware/BIOS updates for affected notebook models once available. Verify secure boot is enabled in UEFI settings and ensure physical security to prevent unauthorized local access.

Recommended fix High confidence

Update to firmware version g0cn11ww or later for D330 10igl; j4cn33ww or later for Ideapad 5 Pro 16iah7; j5cn27ww or later for Ideapad 5 Pro 16arh7; eqcn37ww or later for Ideapad Duet 3 10igl5; klcn15ww or later for Slim 7 16arh7; f6cn25ww or later for Thinkbook 15p Imp; dmcn43ww or later for Slim 7

  1. 1. Identify the exact model of the Lenovo device from the affected list
  2. 2. Visit the Lenovo support website (support.lenovo.com) and navigate to the Drivers & Software section for the specific device model
  3. 3. Download the latest BIOS/firmware update for the device
  4. 4. Ensure the device is connected to power and not running on battery only
  5. 5. Run the firmware update utility and follow the on-screen instructions
  6. 6. Allow the system to restart and complete the firmware update process - do not interrupt this process
  7. 7. Verify the installed firmware version matches or exceeds the fixed version for your device
Caveat Firmware updates carry inherent risk of rendering the device unusable if interrupted or if an incorrect version is applied; ensure correct model match and stable power

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in D330 10igl Firmware Scoped from the published advisory
  • Consultation2.0 h
  • Implementation1.0 h
  • Testing3.0 h
  • Review / QA2.0 h
8.0 hours of engineering $1,390
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,224.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2022-3430 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2022-3430 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data