CVE-2023-43573
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 LEMALLDriversConnectedEventHook 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 in the LEMALLDriversConnectedEventHook module in Lenovo Desktop products allows a local attacker with elevated privileges to execute arbitrary code via heap or stack overflow. The CVSS 6.7 score indicates moderate severity with local attack vector and high confidentiality/availability impact potential.
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 system modelCheck the system model number via system information utility, BIOS setup (F1 at boot), or command: 'wmic computersystem get model' or 'systeminfo' in Windows. For firmware version, access UEFI/BIOS setup (F1 at boot) or use Lenovo Vantage/Commercial Vantage tool.Affected if The system 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.
-
Locate the current firmware versionAccess the UEFI/BIOS setup (press F1 at boot) and note the BIOS/firmware version shown on the main screen. Alternatively, use Lenovo Vantage or Commercial Vantage software under 'System Update' or 'BIOS Update' section, or run: 'wmic bios get smbiosbiosversion' in Windows.Affected if The displayed firmware version cannot be determined or is not visible in the system information.
-
Compare firmware version against affected ranges for Ideacentre C5 14imb05If system model is Ideacentre C5 14imb05, compare the installed firmware version string to 'o4hkt3ca'. Versions lower than o4hkt3ca are affected (e.g., o4hkt3cb is NOT affected).Affected if Installed firmware version is lexicographically less than o4hkt3ca.
-
Compare firmware version against affected ranges for Ideacentre 3 modelsIf system model is Ideacentre 3 07ada05, compare to 'o4fkt39a'. If model is Ideacentre 3 07imb05, compare to 'm2vkt21a. Versions lower than these thresholds are affected.Affected if For 07ada05: version < o4fkt39a. For 07imb05: version < m2vkt21a.
-
Compare firmware version against affected ranges for Ideacentre 5 and Thinkcentre modelsFor Ideacentre 5 14iab7, compare to 'm42kt46a'. For 14irb8, compare to 'm4ukt36a'. For Thinkcentre Neo 70t Gen 3, compare to 'm40kt45a'. Versions lower than these are affected. Ideacentre 5 14acn6 and Ideacentre T540 15ama G are affected in ALL versions.Affected if 14iab7: version < m42kt46a; 14irb8: version < m4ukt36a; Neo 70t Gen 3: version < m40kt45a; or model is Ideacentre 5 14acn6 / Ideacentre T540 15ama G (all versions affected).
A user is affected if their Lenovo Desktop matches an affected model AND their installed firmware version is lower than the specified threshold (or is any version for the models with 'all versions' listed).
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-supplied firmware updates or patches for affected Desktop products to remediate the buffer overflow in LEMALLDriversConnectedEventHook. Prioritize systems with elevated-privilege user access.
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
- Identify the exact model number of the Lenovo desktop system from the affected product list
- Navigate to support.lenovo.com and use the product search or model number to find the firmware download page
- Locate the BIOS/UEFI firmware update for the specific model
- Download and apply the firmware update matching or exceeding the fixed version threshold: o4hkt3ca (C5 14imb05), o4fkt39a (3 07ada05), m2vkt21a (3 07imb05), m42kt46a (5 14iab7), m4ukt36a (5 14irb8), m40kt45a (Neo 70t Gen 3)
- For Ideacentre 5 14acn6 and Ideacentre T540 15ama G (all versions), contact Lenovo support directly to verify if a patched firmware is available
- Restart the system after applying the firmware update to complete the remediation
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation2.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 $2,752.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-43573 — 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-43573 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