CVE-2022-3744
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 · uneditedA potential vulnerability was discovered in LCFC BIOS for some Lenovo consumer notebook models that could allow a local attacker with elevated privileges to unlock UEFI variables due to a hard-coded SMI handler credential.
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 confidenceA hard-coded credential in the System Management Interrupt (SMI) handler within LCFC BIOS firmware for certain Lenovo consumer notebooks allows a local attacker with elevated privileges to bypass security controls and unlock UEFI variables, potentially modifying firmware-level settings.
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< jkcn34ww< kkcn15ww< jkcn34ww< kkcn15ww< htcn31ww< htcn31ww< jkcn34ww< jkcn34wwCVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Identify the exact notebook model numberCheck the system model using 'systeminfo' on Windows or 'dmidecode -s system-product-name' on Linux, or visually inspect the chassis for the full model designation (e.g., Ideapad 1 14iau7)Affected if The model is not one of the eight listed affected Ideapad models (1 14iau7, 1 14igl7, 1 15iau7, 1 15igl7, 1 14ijl7, 1 15ijl7, 3 14iau7, 3 15iau7)
-
Determine the current BIOS firmware versionRun 'wmic bios get smbiosbiosversion' on Windows, 'dmidecode -s bios-version' on Linux, or access the BIOS setup menu (press F2 at boot) to view the BIOS versionAffected if Unable to retrieve a BIOS version string from the system
-
Compare installed version against affected rangesMatch your model to its version threshold: Ideapad 1 14iau7/15iau7 and Ideapad 3 14iau7/15iau7 are affected below jkcn34ww; Ideapad 1 14igl7/15igl7 below kkcn15ww; Ideapad 1 14ijl7/15ijl7 below htcn31wwAffected if The installed BIOS version is lower than the threshold for your specific model (e.g., jkcn34ww for 14iau7)
-
Verify the BIOS vendor is LCFCCheck the BIOS vendor information using 'wmic bios get manufacturer' on Windows or 'dmidecode -s bios-vendor' on Linux; LCFC (Lenovo Capital Factory Inc.) is the OEM for these consumer notebooksAffected if The BIOS vendor is not LCFC or the system uses a different BIOS supplier
A system is affected if it is one of the eight listed Ideapad models with a BIOS version lower than the specified threshold for that model, and the BIOS is manufactured by LCFC.
Generated from the published advisory. Verify against your own configuration.
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 · scopedApply the vendor-provided BIOS/firmware update from Lenovo to remove the hard-coded SMI handler credential. Restrict physical and local access to affected systems as a compensating control until the patch is deployed.
jkcn34ww (for 14iau7/15iau7/3 models) | kkcn15ww (for 14igl7/15igl7) | htcn31ww (for 14ijl7/15ijl7)
- 1. Identify the exact model number of the Lenovo Ideapad laptop (e.g., Ideapad 1 14iau7, Ideapad 3 15iau7, etc.)
- 2. Determine the current BIOS/firmware version installed on the system via BIOS setup or Lenovo Vantage software
- 3. Navigate to the Lenovo support website (support.lenovo.com) and enter the product model number
- 4. Locate the BIOS/firmware update section and download the latest version that addresses CVE-2022-3744
- 5. For Ideapad 1 14iau7/15iau7 and Ideapad 3 models: download version jkcn34ww or later
- 6. For Ideapad 1 14igl7/15igl7: download version kkcn15ww or later
- 7. For Ideapad 1 14ijl7/15ijl7: download version htcn31ww or later
- 8. Run the BIOS update utility with administrator privileges and ensure the laptop is connected to AC power
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation6.0 h
- Implementation4.0 h
- Testing8.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,144.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-3744 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2022-3744 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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