dbcve.org
Ideacentre C5 14imb05 FirmwareOperating system · Lenovo

CVE-2023-45075

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 memory leakage vulnerability was reported in the SWSMI_Shadow DXE driver that may allow a local attacker with elevated privileges to write to NVRAM variables.

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

Memory leakage vulnerability in the SWSMI_Shadow DXE driver allows a local attacker with elevated privileges to write to NVRAM variables. This is a UEFI firmware issue where memory is not properly freed in the driver, potentially leading to resource exhaustion or enabling privilege escalation through NVRAM manipulation.

MitigationApply vendor-supplied firmware updates for the SWSMI_Shadow DXE driver. This requires obtaining a patched firmware image from the system/board manufacturer and following their documented firmware update procedure.

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 G5 14imb05 FirmwareOperating system
Affected:< o4hkt3ca
Ideacentre 5 14iob6 FirmwareOperating system
Affected:< m3gkt3da
Ideacentre Creator 5 14iob6 FirmwareOperating system
Affected:< m3gkt3da
Ideacentre G5 14amr05 FirmwareOperating system
Affected:< o4zkt2ba
Ideacentre Gaming 5 14iob6 FirmwareOperating system
Affected:< m3gkt3da

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 Ideacentre model number
    Check the system model label on the case or use system information tools (such as 'systeminfo' on Windows or 'dmidecode' on Linux) to confirm the exact model (e.g., C5 14imb05, 3 07ada05, G5 14imb05, etc.)
    Affected if The model matches one of the listed affected Ideacentre variants
  2. Check the installed UEFI firmware version
    Access the UEFI/BIOS setup on boot (typically pressing F1 or Del) and look at the BIOS/UEFI version information, or use platform-specific tools like 'wmic bios get version' on Windows or 'dmidecode -s bios-version' on Linux
    Affected if The firmware version is below the threshold for your specific model (o4hkt3ca, o4fkt39a, m2vkt21a, m3gkt3da, or o4zkt2ba depending on model)
  3. Confirm the SWSMI_Shadow driver presence
    Use UEFI shell tools or firmware inspection utilities (such as UEFItool or Chipsec) to examine the DXE drivers loaded in the firmware image and look for a driver named SWSMI_Shadow
    Affected if The SWSMI_Shadow DXE driver is present in the firmware and the firmware version is below the patched version
  4. Verify NVRAM access capability
    Confirm you have elevated privileges and can access NVRAM variables through UEFI runtime services or tools like 'efivar' on Linux or UEFI variable enumerators on Windows
    Affected if You can write to NVRAM variables with elevated privileges and the vulnerable driver is loaded

You are affected if you have a listed Ideacentre model with firmware version below the specified threshold and the SWSMI_Shadow driver is present in your UEFI firmware.

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 vendor-supplied firmware updates for the SWSMI_Shadow DXE driver. This requires obtaining a patched firmware image from the system/board manufacturer and following their documented firmware update procedure.

Recommended fix High confidence

Firmware version o4hkt3ca or higher for C5/G5 14imb05; o4fkt39a or higher for Ideacentre 3 07ada05; m2vkt21a or higher for Ideacentre 3 07imb05; m3gkt3da or higher for Ideacentre 5/Creator 5/Gaming 5 14iob6; o4zkt2ba or higher for Ideacentre G5 14amr05

  1. 1. Identify the exact model number of the Lenovo Ideacentre device from the affected list
  2. 2. Visit the Lenovo support website (support.lenovo.com) and navigate to the Drivers & Software section for the specific model
  3. 3. Locate the BIOS/UEFI firmware update corresponding to the fixed version for your model: o4hkt3ca, o4fkt39a, m2vkt21a, m3gkt3da, or o4zkt2ba (depending on model)
  4. 4. Download the firmware update package from Lenovo's official support site
  5. 5. Follow Lenovo's firmware update instructions - typically this involves running the update utility or placing the file on a USB drive for BIOS flash
  6. 6. Ensure the device remains powered on throughout the firmware update process
  7. 7. After update, verify the firmware version has been successfully updated to the fixed version or higher
Caveat Firmware updates carry a risk of device bricking if interrupted; ensure stable power 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
  • Implementation2.0 h
  • Testing6.0 h
  • Review / QA3.0 h
15.0 hours of engineering $2,600
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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