CVE-2023-4028
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 buffer overflow has been identified in the SystemUserMasterHddPwdDxe driver in some Lenovo Notebook products which may allow an attacker with local access and elevated 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 confidenceA buffer overflow vulnerability exists in Lenovo's SystemUserMasterHddPwdDxe UEFI driver, which handles HDD password management. An attacker with local access and elevated privileges can exploit the overflow to execute arbitrary code in the system firmware context.
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< jacn38ww< kbcn20ww< fqcn29ww< dwcn28ww< fqcn29ww< dwcn28ww< gjcn32ww< eecn43wwCVSS 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 Lenovo notebook modelRun 'systeminfo' (Windows) or check the device label on the chassis. The system model name (e.g., 13w Yoga, Ideapad 1 11ada05, Flex 5 14alc05) must match one of the affected products listed.Affected if The model is any of: 13w Yoga, 13w Yoga Gen 2, Ideapad 1 11ada05, Ideapad 1 11igl05, Ideapad 1 14ada05, Ideapad 1 14igl05, Flex 5 14alc05, or Flex 5 14are05.
-
Check the current BIOS/firmware versionOn Windows, run 'wmic bios get smbiosbiosversion' or check in BIOS/UEFI setup under ' BIOS Version' or 'System Information'. On Linux, run 'dmidecode -s bios-version'. Note the exact version string.Affected if The installed BIOS version is lower than the threshold for the specific model: jacn38ww (13w Yoga), kbcn20ww (13w Yoga Gen 2), fqcn29ww (Ideapad 1 11ada05/14ada05), dwcn28ww (Ideapad 1 11igl05/14igl05), gjcn32ww (Flex 5 14alc05), or eecn43ww (Flex 5 14are05).
-
Confirm HDD password feature is accessibleAccess the BIOS/UEFI setup (press Enter or F2 during boot) and navigate to the 'Security' or 'HDD Password' section. The SystemUserMasterHddPwdDxe driver is only invoked when HDD password management is used.Affected if A HDD user or master password is set, or the feature is available in the BIOS setup menu - the driver executes whenever the HDD password subsystem is initialized.
-
Verify local administrator accessConfirm the user has local administrator or root privileges on the operating system. The attacker needs elevated privileges to interact with the UEFI driver.Affected if The user has local admin/root access - combined with the vulnerable driver version, this meets the privilege requirement for exploitation.
You are affected if your Lenovo model matches one of the eight affected products AND your installed BIOS version is below the specified threshold for that model, regardless of whether you actively use the HDD password feature since the driver loads at boot.
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 Lenovo BIOS/firmware update for affected notebook models as specified in Lenovo's security advisory.
Upgrade to firmware version jacn38ww (13w Yoga), kbcn20ww (13w Yoga Gen 2), fqcn29ww (Ideapad 1 11ada05/14ada05), dwcn28ww (Ideapad 1 11igl05/14igl05), gjcn32ww (Flex 5 14alc05), or eecn43ww (Flex 5 14are05) or later
- 1. Identify the exact Lenovo notebook model number (e.g., 13w Yoga, Ideapad 1 11ada05, Flex 5 14are05)
- 2. Navigate to Lenovo's support website at support.lenovo.com
- 3. Enter the model number in the search field to access the product support page
- 4. Locate the 'Drivers & Software' or 'BIOS' section
- 5. Find the firmware update corresponding to the fixed version for your model: 13w Yoga: jacn38ww | 13w Yoga Gen 2: kbcn20ww | Ideapad 1 11ada05/14ada05: fqcn29ww | Ideapad 1 11igl05/14igl05: dwcn28ww | Flex 5 14alc05: gjcn32ww | Flex 5 14are05: eecn43ww
- 6. Download the firmware update package
- 7. Follow Lenovo's instructions to apply the firmware update, which typically requires running the executable and allowing the system to restart
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation3.0 h
- Implementation4.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,880.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-4028 — 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-2023-4028 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