CVE-2023-43581
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 Update_WMI 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 Update_WMI module of certain Lenovo Desktop products. An attacker with already elevated local privileges can exploit this buffer overflow to execute arbitrary code, potentially maintaining persistence or escalating further.
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 system information to determine if the machine is a Lenovo 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 3Affected if The system model matches any of the affected models listed in the CVE
-
Locate the firmware versionAccess the UEFI/BIOS settings or use system information tools to find the installed firmware version stringAffected if The firmware version cannot be determined or retrieved
-
Compare firmware version against affected rangesMatch the installed firmware version to the version thresholds: Ideacentre C5 14imb05 < o4hkt3ca, Ideacentre 3 07ada05 < o4fkt39a, Ideacentre 3 07imb05 < m2vkt21a, Ideacentre 5 14iab7 < m42kt46a, Ideacentre 5 14irb8 < m4ukt36a, Thinkcentre Neo 70t Gen 3 < m40kt45aAffected if The installed firmware version is lower than the specified threshold for that model, or for Ideacentre 5 14acn6 and Ideacentre T540 15ama G the version is any value
-
Check for Update_WMI module presenceReview installed software or drivers to determine if the Update_WMI module is present on the systemAffected if The Update_WMI module is installed on an affected model with vulnerable firmware version
A user is affected if they own an affected Ideacentre or Thinkcentre model with a firmware version below the specified threshold (or any version for Ideacentre 5 14acn6 and Ideacentre T540 15ama G) and the Update_WMI module is present.
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 Lenovo's security updates for the Update_WMI module to affected Desktop products; verify all systems are patched and monitor for any anomalous WMI activity.
Firmware version o4hkt3ca (C5 14imb05), o4fkt39a (07ada05), m2vkt21a (07imb05), m42kt46a (14iab7), m4ukt36a (14irb8), m40kt45a (Neo 70t Gen 3) or later; contact Lenovo for specific updates to 14acn6 and T540 15ama G
- 1. Identify the exact Lenovo Desktop model number (e.g., Ideacentre C5 14imb05, Thinkcentre Neo 70t Gen 3)
- 2. Visit the Lenovo support website (support.lenovo.com) and navigate to the Drivers & Updates section for your specific model
- 3. Locate the BIOS/UEFI firmware update that matches or exceeds the fixed version number for your product: C5 14imb05 needs o4hkt3ca or later, 07ada05 needs o4fkt39a or later, 07imb05 needs m2vkt21a or later, 14iab7 needs m42kt46a or later, 14irb8 needs m4ukt36a or later, 14acn6 needs any available update, T540 15ama G needs any available update, Neo 70t Gen 3 needs m40kt45a or later
- 4. Download the firmware update package from Lenovo's official support site
- 5. Follow Lenovo's firmware update instructions, typically requiring running the update utility or copying to a USB drive for BIOS flashing
- 6. Restart the system after the firmware update completes
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation3.0 h
- Implementation6.0 h
- Testing4.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 $4,224.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-43581 — 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-43581 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