dbcve.org
Ideacentre C5 14imb05 FirmwareOperating system · Lenovo

CVE-2023-43575

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 UltraFunctionTable 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 UltraFunctionTable module of certain Lenovo Desktop products. The flaw allows a local attacker who already possesses elevated privileges to execute arbitrary code by overflowing a buffer in the UltraFunctionTable component.

MitigationApply the Lenovo firmware/driver update for the UltraFunctionTable module to affected Lenovo Desktop products. Since the vulnerability requires elevated privileges, ensure proper access controls and monitor for privilege escalation attempts.

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 the Lenovo desktop model
    Run system information commands (such as 'systeminfo' on Windows, 'dmidecode' on Linux, or check the system BIOS/UEFI information) to confirm the exact model name and model number matches one of the affected products: 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.
    Affected if The model is any of these eight products.
  2. Check the installed firmware version
    Access the system BIOS/UEFI setup during boot, or use manufacturer-provided tools (such as Lenovo Vantage, Lenovo System Update, or 'fwupdmgr' on Linux) to retrieve the current firmware version. Compare the version string against the affected ranges: for C5 14imb05 check if version is earlier than o4hkt3ca, for 07ada05 earlier than o4fkt39a, for 07imb05 earlier than m2vkt21a, for 14iab7 earlier than m42kt46a, for 14irb8 earlier than m4ukt36a, and for Thinkcentre Neo 70t Gen 3 earlier than m40kt45a. For 14acn6 and T540 15ama G all versions are affected.
    Affected if The firmware version is lower than the specified threshold for your model, or your model is the 14acn6 or T540 15ama G variant.
  3. Verify UltraFunctionTable module presence
    Check if the UltraFunctionTable component is present on the system by examining the installed firmware package, BIOS update bundle contents, or system drivers/modules list. On Windows, use 'wmic bios get version' or check the Lenovo firmware update package. On Linux, examine /sys/class/dmi/id/ or the UEFI firmware descriptor.
    Affected if The UltraFunctionTable module exists in the firmware build for your system.

You are affected if your Lenovo desktop model matches one of the eight listed products and your firmware version falls below the specified threshold (or is any version for the 14acn6 and T540 15ama G 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 the Lenovo firmware/driver update for the UltraFunctionTable module to affected Lenovo Desktop products. Since the vulnerability requires elevated privileges, ensure proper access controls and monitor for privilege escalation attempts.

Recommended fix High confidence

Firmware version >= o4hkt3ca (C5 14imb05), >= o4fkt39a (07ada05), >= m2vkt21a (07imb05), >= m42kt46a (14iab7), >= m4ukt36a (14irb8), >= m40kt45a (Neo 70t Gen 3) - check Lenovo support for specific model

  1. 1. Identify the exact Lenovo Desktop model from the affected product list
  2. 2. Visit the official Lenovo support website at support.lenovo.com
  3. 3. Enter the product model number or serial number to access the product support page
  4. 4. Navigate to the 'Drivers & Software' or 'Firmware' section
  5. 5. Download the latest BIOS/firmware update that meets or exceeds the fixed version number for your specific model: - Ideacentre C5 14imb05: o4hkt3ca or higher - Ideacentre 3 07ada05: o4fkt39a or higher - Ideacentre 3 07imb05: m2vkt21a or higher - Ideacentre 5 14iab7: m42kt46a or higher - Ideacentre 5 14irb8: m4ukt36a or higher - Thinkcentre Neo 70t Gen 3: m40kt45a or higher
  6. 6. Review the firmware update release notes to confirm it addresses CVE-2023-43575
  7. 7. Follow Lenovo's provided instructions to apply the firmware update (typically requires restarting the system)
Caveat Firmware updates carry a risk of bricking the device if interrupted; ensure stable power connection and follow 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
  • Consultation4.0 h
  • Implementation3.0 h
  • Testing3.0 h
  • Review / QA2.0 h
12.0 hours of engineering $2,150
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2023-43575 — 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-43575 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