CVE-2023-43569
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 was reported in the OemSmi module in some Lenovo Desktop products that may allow a local attacker with 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 the OemSmi (OEM System Management Interrupt) module of the UEFI firmware on certain Lenovo Desktop products. The flaw allows a local attacker who already has elevated privileges to overflow a buffer in the SMI handler and execute arbitrary code with the highest firmware-level privileges.
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< o4hkt3ca< o4fkt39a< m2vkt21a< m42kt46a< m4ukt36aall versionsall versions< m40kt45aCVSS 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 desktop modelCheck the system model by looking at the physical product label, running 'systeminfo' on Windows, or 'cat /sys/class/dmi/id/product_name' on LinuxAffected if The model is one of: Ideacentre C5 14imb05, Ideacentre 3 07ada05, Ideacentre 3 07imb05, Ideacentre 5 14iab7, Ideacentre 5 14irb8, Ideacentre 5 14acn6, Ideacentre T540 15ama G, or Thinkcentre Neo 70t Gen 3
-
Check the BIOS/UEFI firmware versionAccess the BIOS setup by pressing F1 during boot, or run 'dmidecode -s bios-version' on Linux, or use Lenovo Vantage/联想管家 on Windows to view firmware versionAffected if The displayed firmware version is below the safe version for your model, or for Ideacentre 5 14acn6 or Ideacentre T540 15ama G, any version indicates exposure
-
Confirm the OemSmi module is presentThis is a UEFI firmware-level component. The vulnerability exists in the OemSmi (OEM System Management Interrupt) handler within the UEFI firmware. No user-accessible command confirms module presence; the risk is determined by product model and version aloneAffected if The system runs the vulnerable UEFI firmware version on any of the affected models
-
Verify system is a desktop form factorConfirm this is a desktop (tower or small form factor) rather than a laptop or mobile device by checking the product specifications or physical formAffected if The affected products listed are all desktop (Ideacentre Desktop, Thinkcentre) - laptops are not in scope for this CVE
A user is affected if they own any of the eight listed Lenovo desktop models and their current BIOS/UEFI firmware version is below the specified safe version threshold, or if they own the two models (Ideacentre 5 14acn6, Ideacentre T540 15ama G) marked as all versions affected.
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 firmware update for the affected desktop products as released in the Lenovo security advisory. This is a BIOS/UEFI firmware-level patch that must be applied by administrators.
Firmware version o4hkt3ca or later for Ideacentre C5 14imb05; o4fkt39a or later for Ideacentre 3 07ada05; m2vkt21a or later for Ideacentre 3 07imb05; m42kt46a or later for Ideacentre 5 14iab7; m4ukt36a or later for Ideacentre 5 14irb8; m40kt45a or later for Thinkcentre Neo 70t Gen 3; contact Lenovo
- 1. Identify the exact model number of the Lenovo desktop system from the product label or system information.
- 2. Navigate to support.lenovo.com and use the product name or model number to find the support page.
- 3. Locate the Drivers & Software section and filter by BIOS/Firmware category.
- 4. Download the latest BIOS/firmware update for the specific model, ensuring the version meets or exceeds the minimum fixed version listed (e.g., o4hkt3ca for Ideacentre C5 14imb05, o4fkt39a for Ideacentre 3 07ada05, m2vkt21a for Ideacentre 3 07imb05, m42kt46a for Ideacentre 5 14iab7, m4ukt36a for Ideacentre 5 14irb8, m40kt45a for Thinkcentre Neo 70t Gen 3).
- 5. Review the firmware update release notes to confirm it addresses CVE-2023-43569.
- 6. Follow Lenovo's documented firmware update procedure, which typically involves running the update utility from Windows or creating a bootable USB update media.
- 7. Restart the system after the firmware update completes to ensure the new firmware is properly applied.
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.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 $1,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-43569 — 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-43569 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