dbcve.org
Ideacentre C5 14imb05 FirmwareOperating system · Lenovo

CVE-2023-43567

MEDIUM · 6.7 CVSS v3.1 Published 2023-11-08
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
69/100
Remediation priority · Elevated
Zero-click

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 · unedited
A buffer overflow was reported in the LemSecureBootForceKey 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 confidence

A buffer overflow vulnerability exists in the LemSecureBootForceKey module of certain Lenovo Desktop products. An attacker with already-elevated local privileges can exploit this buffer overflow to execute arbitrary code with those elevated privileges.

MitigationApply Lenovo firmware/security updates for affected desktop products once released. Since this requires local elevated access, ensure systems are not exposed to untrusted local users and restrict physical access to endpoints.

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
Ideacentre C5 14imb05 FirmwareOperating system
Affected:< o4hkt3ca
Ideacentre 3 07ada05 FirmwareOperating system
Affected:< o4fkt39a
Ideacentre 3 07imb05 FirmwareOperating system
Affected:< m2vkt21a
Ideacentre 5 14iab7 FirmwareOperating system
Affected:< m42kt46a
Ideacentre 5 14irb8 FirmwareOperating system
Affected:< m4ukt36a
Ideacentre 5 14acn6 FirmwareOperating system
Affected:all versions
Ideacentre T540 15ama G FirmwareOperating system
Affected:all versions
Thinkcentre Neo 70t Gen 3 FirmwareOperating system
Affected:< m40kt45a

CVSS 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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify your Lenovo desktop model
    Run 'systeminfo' or check the physical machine label to confirm the exact model (e.g., Ideacentre C5 14imb05, Thinkcentre Neo 70t Gen 3)
    Affected if The model matches any of the affected product names listed in the CVE
  2. Retrieve your current firmware version
    Access the UEFI/BIOS setup during boot (press F1 or Delete) and check the BIOS version, or use commands like 'wmic bios get smbiosbiosversion' on Windows or 'dmidecode -s bios-version' on Linux
    Affected if The firmware version is returned and can be compared against the affected ranges
  3. Compare your firmware version to the affected ranges
    For each affected model, compare your installed version string to the threshold: C5 14imb05 requires < o4hkt3ca, 3 07ada05 requires < o4fkt39a, 3 07imb05 requires < m2vkt21a, 5 14iab7 requires < m42kt46a, 5 14irb8 requires < m4ukt36a, Thinkcentre Neo 70t Gen 3 requires < m40kt45a. Ideacentre 5 14acn6 and T540 15ama G are affected at all versions
    Affected if Your firmware version is lower than the threshold version, or your model is one of the 'all versions' variants
  4. Verify the LemSecureBootForceKey module is present
    This module is a UEFI firmware component and is not directly visible from the operating system. Check if your firmware/BIOS supports the 'SecureBoot Force Key' feature in the UEFI settings, typically under Security or Boot options
    Affected if The system has UEFI firmware with SecureBoot configuration capabilities (the vulnerable module exists in the firmware)

You are affected if your Lenovo desktop model matches one of the eight affected products and your current firmware version falls below the specified threshold version (or is any version for the two 'all versions' models).

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Apply Lenovo firmware/security updates for affected desktop products once released. Since this requires local elevated access, ensure systems are not exposed to untrusted local users and restrict physical access to endpoints.

Recommended fix High confidence

Upgrade to firmware version o4hkt3ca (C5 14imb05), o4fkt39a (3 07ada05), m2vkt21a (3 07imb05), m42kt46a (5 14iab7), m4ukt36a (5 14irb8), or m40kt45a (Thinkcentre Neo 70t Gen 3) depending on model; Ideacentre 5 14acn6 and Ideacentre T540 15ama G have no fixed firmware available

  1. 1. Identify the exact model number of the affected Lenovo desktop system
  2. 2. Navigate to support.lenovo.com and enter the product model number to access the drivers and firmware download page
  3. 3. Locate the BIOS/UEFI firmware update for the specific model
  4. 4. Download the firmware update version that matches or exceeds the fixed version for your model: o4hkt3ca for C5 14imb05, o4fkt39a for 3 07ada05, m2vkt21a for 3 07imb05, m42kt46a for 5 14iab7, m4ukt36a for 5 14irb8, m40kt45a for Thinkcentre Neo 70t Gen 3
  5. 5. Review the firmware update release notes for any prerequisites or warnings
  6. 6. Run the firmware update utility as an administrator, ensuring the system is connected to power and not interrupted
  7. 7. After the update completes, verify the firmware version has been applied successfully
Caveat Firmware updates carry inherent risk of system damage if interrupted; ensure stable power and follow Lenovo update instructions precisely

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Ideacentre C5 14imb05 Firmware Scoped from the published advisory
  • Consultation1.0 h
  • Implementation1.0 h
  • Testing2.0 h
  • Review / QA1.0 h
5.0 hours of engineering $860
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,376.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2023-43567 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2023-43567 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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