CVE-2022-3432
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 in a driver used during manufacturing process on the Ideapad Y700-14ISK 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 confidenceA manufacturing driver that should have been deactivated remains active on the Ideapad Y700-14ISK. An attacker with elevated privileges can modify NVRAM variables to change secure boot settings, compromising the boot chain integrity.
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 dataall versionsCVSS 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.
-
Confirm device modelRun 'systeminfo' or check the physical laptop label to verify the exact model is Lenovo Ideapad Y700-14ISKAffected if The device model is Ideapad Y700-14ISK and the vulnerable manufacturing driver is present in firmware
-
Identify firmware versionAccess UEFI/BIOS setup (press F2 or Fn+F2 at boot) and check the BIOS/firmware version information screen, or use 'wmic bios get smbiosbiosversion' from Windows command promptAffected if The firmware version shown belongs to the Ideapad Y700-14ISK model - all versions of this model are affected
-
Inspect secure boot configurationFrom Windows, run 'bcdedit /enum firmware' or check UEFI BIOS settings under Secure Boot section to review current secure boot settingsAffected if Secure boot is disabled or shows unexpected configuration changes that may indicate NVRAM manipulation
-
Check for NVRAM variable modificationsUse 'bcdedit /enum all' to list all boot entries, or access UEFI shell (if available) to dump NVRAM variables and compare against known-good baselineAffected if NVRAM boot entries contain unauthorized or unexpected secure boot policy changes
-
Verify manufacturing driver presenceAccess UEFI BIOS setup and look for any manufacturing diagnostic or test drivers listed in boot options, or use UEFI shell to enumerate loaded driversAffected if A manufacturing driver that should have been removed is still listed as active in the firmware
If the device is a Lenovo Ideapad Y700-14ISK, the system is affected because all firmware versions contain the vulnerable active manufacturing driver that allows NVRAM modification of secure boot settings.
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.
From vendor dataApply the Lenovo BIOS/firmware update that removes the vulnerable manufacturing driver. Until patched, monitor for unauthorized NVRAM modifications and restrict administrative access.
- Consultation4.0 h
- Implementation4.0 h
- Testing2.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,488.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-3432 — 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-3432 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