dbcve.org
100e 2nd Gen FirmwareOperating system · Lenovo

CVE-2022-1892

HIGH · 7.8 CVSS v3.1 Published 2023-01-26
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 buffer overflow in the SystemBootManagerDxe driver in some Lenovo Notebook products may allow an attacker with local privileges to execute arbitrary code.

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

A buffer overflow vulnerability exists in the SystemBootManagerDxe UEFI driver on certain Lenovo notebook systems. The flaw allows a local attacker with existing privileges to achieve arbitrary code execution at the firmware level, which runs with the highest system privileges.

MitigationApply the Lenovo firmware update for the SystemBootManagerDxe driver to the affected notebook models. Verify the update through system BIOS/UEFI version confirmation.

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
100e 2nd Gen FirmwareOperating system
Affected:< frcn23ww
100w Gen 3 FirmwareOperating system
Affected:< gacn38ww
13w Yoga FirmwareOperating system
Affected:< jacn31ww
14w Gen 2 FirmwareOperating system
Affected:< h0cn21ww
300e 2nd Gen FirmwareOperating system
Affected:< frcn23ww
300w Gen 3 FirmwareOperating system
Affected:< gacn38ww
500w Gen 3 FirmwareOperating system
Affected:< g6cn40ww
730s 13iml FirmwareOperating system
Affected:< brcn20ww

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 the exact Lenovo notebook model
    Check the system model via Windows Command Prompt (wmic csproduct get name), Linux (cat /sys/class/dmi/id/product_name), or physical laptop label
    Affected if The model is one of: Lenovo 100e 2nd Gen, 100w Gen 3, 13w Yoga, 14w Gen 2, 300e 2nd Gen, 300w Gen 3, 500w Gen 3, or 730s 13iml - if not, this CVE does not apply
  2. Determine the current BIOS/UEFI firmware version
    Access BIOS setup (press F1 or F2 at startup), or run in Windows: wmic bios get smbiosbiosversion, or in Linux: dmidecode -s bios-version, or use Lenovo Vantage/System Update utility
    Affected if The displayed firmware version is below the safe threshold for your model (see version list in CVE details)
  3. Compare your firmware version against affected ranges
    Reference the version number obtained against these thresholds: 100e 2nd Gen: frcn23ww, 100w Gen 3: gacn38ww, 13w Yoga: jacn31ww, 14w Gen 2: h0cn21ww, 300e 2nd Gen: frcn23ww, 300w Gen 3: gacn38ww, 500w Gen 3: g6cn40ww, 730s 13iml: brcn20ww
    Affected if Your installed version is lower (lexicographically) than the corresponding threshold version - meaning version numbers like frcn22ww, gacn37ww, etc indicate vulnerability
  4. Confirm SystemBootManagerDxe driver presence (optional advanced check)
    This requires UEFI shell tools or examining a BIOS image dump - most users should rely on version checking above. If available, inspect the SystemBootManagerDxe driver signature in the BIOS/UEFI firmware image
    Affected if This check is supplementary; version comparison in step 3 is the primary indicator

You are affected if your Lenovo notebook model matches one of the eight listed models AND your current BIOS/UEFI firmware version is below the specified threshold version for that model.

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 the Lenovo firmware update for the SystemBootManagerDxe driver to the affected notebook models. Verify the update through system BIOS/UEFI version confirmation.

Recommended fix High confidence

Firmware version frcn23ww (100e/300e 2nd Gen), gacn38ww (100w/300w Gen 3), g6cn40ww (500w Gen 3), jacn31ww (13w Yoga), h0cn21ww (14w Gen 2), or brcn20ww (730s 13iml) - depending on model

  1. 1. Identify the exact Lenovo notebook model number (e.g., 100e 2nd Gen, 500w Gen 3, etc.)
  2. 2. Determine the current firmware version by accessing the BIOS/UEFI setup or using Lenovo's Vantage/System Update utility
  3. 3. Navigate to support.lenovo.com and enter the specific model number to access firmware downloads
  4. 4. Download the firmware update package matching the fixed version for the model: 100e 2nd Gen/300e 2nd Gen -> frcn23ww or later, 100w Gen 3/300w Gen 3 -> gacn38ww or later, 500w Gen 3 -> g6cn40ww or later, 13w Yoga -> jacn31ww or later, 14w Gen 2 -> h0cn21ww or later, 730s 13iml -> brcn20ww or later
  5. 5. Follow Lenovo's provided instructions to apply the firmware update, typically by running the update utility from Windows or creating a bootable USB for offline update
  6. 6. Restart the system after the update completes and verify the new firmware version
Caveat Firmware updates carry inherent risk of bricking the device if interrupted; ensure stable power and follow update instructions precisely

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

Fix this in 100e 2nd Gen Firmware Scoped from the published advisory
  • Consultation2.0 h
  • Implementation3.0 h
  • Testing2.0 h
  • Review / QA1.0 h
8.0 hours of engineering $1,420
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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