dbcve.org
Ideapad Creator 5 16ach6 FirmwareOperating system · Lenovo

CVE-2022-3431

HIGH · 7.8 CVSS v3.1 Published 2023-10-09
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
80/100
Remediation priority · High
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 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.

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 · high confidence

A manufacturing debug driver was mistakenly left active in the firmware of certain Lenovo consumer notebooks. This driver allows an attacker with elevated privileges to modify NVRAM variables, specifically compromising secure boot settings by altering the secure boot configuration in UEFI NVRAM.

MitigationApply Lenovo firmware/BIOS updates as they become available to deactivate the vulnerable manufacturing driver. Organizations should verify secure boot is enabled in UEFI settings and monitor for unauthorized NVRAM variable modifications.

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
Ideapad Creator 5 16ach6 FirmwareOperating system
Affected:< gscn34ww
Ideapad 5 Pro 16ihu6 FirmwareOperating system
Affected:< grcn22ww
Ideapad 5 Pro 16ach6 FirmwareOperating system
Affected:< gscn34ww
Yoga Slim 7 13itl05 FirmwareOperating system
Affected:< f7cn39ww
Yoga Slim 7 13acn05 FirmwareOperating system
Affected:< ghcn28ww
Yoga Slim 7 Pro 16arh7 FirmwareOperating system
Affected:< klcn15ww
Yoga Slim 7 Pro 16ach6 FirmwareOperating system
Affected:< hucn16ww
Yoga Slim 7 Carbon 13itl5 FirmwareOperating system
Affected:< f7cn39ww

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
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:L/AC:L/PR:L/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 product label on the device bottom, or run `systeminfo` (Windows) or `cat /sys/class/dmi/id/product_name` (Linux) to confirm the exact model number matches one of the affected products: Ideapad Creator 5 16ach6, Ideapad 5 Pro 16ihu6, Ideapad 5 Pro 16ach6, Yoga Slim 7 13itl05, Yoga Slim 7 13acn05, Yoga Slim 7 Pro 16arh7, Yoga Slim 7 Pro 16ach6, or Yoga Slim 7 Carbon 13itl5.
    Affected if The model number is one of the listed affected products.
  2. Check the installed firmware version
    Access UEFI/BIOS setup on boot (press F2 or Enter during startup) and view the BIOS version, or use `wmic bios get smbiosbiosversion` (Windows) or `cat /sys/class/dmi/id/bios_version` (Linux). Compare the version against the affected threshold: gscn34ww, grcn22ww, f7cn39ww, ghcn28ww, klcn15ww, or hucn16ww depending on your model.
    Affected if The installed firmware version is lower than the listed version for your specific model.
  3. Verify secure boot status in UEFI
    Enter UEFI/BIOS setup and navigate to the Secure Boot option (usually under Boot or Security tab), or run `Confirm-SecureBootUEFI` (Windows PowerShell) to check if secure boot is currently enabled.
    Affected if Secure boot is disabled - this makes the NVRAM manipulation more impactful for bypassing boot protections.
  4. Inspect NVRAM variable integrity
    From an elevated command prompt in Windows, run `bcdedit /enum firmware` to list firmware boot entries, or use `powercfg /device enumerate` to check for unexpected device changes. Compare current NVRAM variables against a known-good baseline if available.
    Affected if There are unexpected or modified NVRAM variables, particularly in the secure boot configuration space.

You are affected if your Lenovo notebook model and firmware version match the affected list, especially if secure boot is disabled or you detect unauthorized NVRAM variable changes.

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 as they become available to deactivate the vulnerable manufacturing driver. Organizations should verify secure boot is enabled in UEFI settings and monitor for unauthorized NVRAM variable modifications.

Recommended fix High confidence

Firmware update to version gscn34ww (or model-specific: grcn22ww, f7cn39ww, ghcn28ww, klcn15ww, hucn16ww) or later depending on exact model

  1. 1. Identify the exact model number of the Lenovo device from the affected list (Ideapad Creator 5 16ach6, Ideapad 5 Pro 16ihu6, Ideapad 5 Pro 16ach6, Yoga Slim 7 13itl05, Yoga Slim 7 13acn05, Yoga Slim 7 Pro 16arh7, Yoga Slim 7 Pro 16ach6, or Yoga Slim 7 Carbon 13itl5)
  2. 2. Determine the current firmware version by entering the device's BIOS/UEFI setup (typically press F2 or Fn+F2 at startup) or using Lenovo Vantage/Lenovo System Update software
  3. 3. Navigate to support.lenovo.com and enter the specific model number in the search or driver download section
  4. 4. Locate the BIOS/UEFI firmware update for the device
  5. 5. Download the appropriate firmware version equal to or higher than the fixed version for the specific model (gscn34ww, grcn22ww, f7cn39ww, ghcn28ww, klcn15ww, or hucn16ww depending on model)
  6. 6. Run the firmware update utility as administrator, ensuring the device is connected to power and not interrupted
  7. 7. Allow the system to reboot and complete the firmware flash process
Caveat Firmware updates carry inherent risk of bricking if interrupted; ensure stable power and do not interrupt the update process

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

Fix this in Ideapad Creator 5 16ach6 Firmware Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA2.0 h
20.0 hours of engineering $3,500
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2022-3431 — 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-3431 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