CVE-2022-3746
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 cause some peripherals to work abnormally due to an exposed Embedded Controller (EC) interface.
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 confidenceA vulnerability in LCFC BIOS for certain Lenovo consumer notebooks exposes the Embedded Controller (EC) interface, allowing a local attacker with elevated privileges to cause peripheral devices to function abnormally.
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 your Lenovo Ideapad model numberOn Windows, run 'systeminfo' or check 'msinfo32' to find the exact model (e.g., Ideapad 1 14iau7, Ideapad 3 15iau7). On Linux, run 'dmidecode -s system-product-name' or check /sys/class/dmi/id/product_name.Affected if The model is one of: Ideapad 1 14iau7, Ideapad 1 14igl7, Ideapad 1 15iau7, Ideapad 1 15igl7, Ideapad 1 14ijl7, Ideapad 1 15ijl7, Ideapad 3 14iau7, or Ideapad 3 15iau7.
-
Check your current BIOS firmware versionOn Windows, run 'wmic bios get biosversion' or check in BIOS setup (F2 on boot). On Linux, run 'dmidecode -s bios-version'.Affected if The command returns a version string that can be compared against the affected version thresholds.
-
Compare your firmware version to the affected threshold for your modelMatch your model to its threshold: Ideapad 1 14iau7/15iau7 and Ideapad 3 models need version < jkcn34ww; Ideapad 1 14igl7/15igl7 need version < kkcn15ww; Ideapad 1 14ijl7/15ijl7 need version < htcn31ww. Compare your installed version alphabetically against the threshold.Affected if Your installed firmware version is alphabetically lower than the threshold for your specific model (e.g., jkcn33ww < jkcn34ww).
You are affected if you own an Ideapad 1 or Ideapad 3 model listed above and your current BIOS firmware version is lower than the specified threshold for that model.
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-supplied BIOS firmware update from Lenovo to remediate the exposed EC interface in affected notebook models.
BIOS firmware version jkcn34ww (or respective fixed version per model: jkcn34ww, kkcn15ww, or htcn31ww)
- 1. Identify your exact Lenovo Ideapad model number (e.g., Ideapad 1 14iau7) and current BIOS firmware version by running 'wmic bios get smbiosbiosversion' or checking System Information.
- 2. Visit the Lenovo support website at support.lenovo.com and enter your product model number to access the drivers and software page.
- 3. Locate the BIOS/UEFI firmware update in the driver section. Download the correct firmware version for your model: for 14iau7/15iau7/14iau7/15iau7 use version jkcn34ww or later, for 14igl7/15igl7 use version kkcn15ww or later, for 14ijl7/15ijl7 use version htcn31ww or later.
- 4. Connect your laptop to AC power and ensure the battery is charged above 30% to prevent interruption during the flash process.
- 5. Run the downloaded BIOS update executable and follow the on-screen instructions. The laptop will automatically restart into the BIOS update process.
- 6. Do not interrupt the update or power off the device until the process completes and the system reboots normally.
- 7. After the update, verify the new BIOS version matches the fixed version installed.
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation2.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,624.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-3746 — 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-3746 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