dbcve.org
Ideacentre C5 14imb05 FirmwareOperating system · Lenovo

CVE-2023-45077

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 534D0740 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

A memory leakage vulnerability in the 534D0740 DXE driver allows a locally authenticated attacker with elevated privileges to write to NVRAM variables. This occurs during the UEFI Driver Execution Environment phase, potentially enabling persistent firmware-level modifications that survive operating system reinstalls.

MitigationApply vendor-supplied firmware updates that patch the 534D0740 DXE driver memory leak; verify NVRAM integrity after patching to ensure no malicious persistence.

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
    Locate the model label on the device chassis or check system information in BIOS/UEFI setup. Confirm it matches one of the affected models: C5 14imb05, 3 07ada05, 3 07imb05, G5 14imb05, 5 14iob6, Creator 5 14iob6, G5 14amr05, or Gaming 5 14iob6.
    Affected if Your model is NOT one of these eight Ideacentre models, then you are not affected by this specific CVE.
  2. Determine the installed firmware version
    Access the UEFI/BIOS setup (press F1 or Del at boot) and locate the firmware or BIOS version information. Alternatively, use the manufacturer-provided firmware update tool or utility for your Ideacentre model to query the current firmware version.
    Affected if You cannot determine the firmware version, treat the status as unknown and follow vendor guidance.
  3. Compare your firmware version against the affected thresholds
    Match your model to its version threshold: C5 14imb05 and G5 14imb05 need < o4hkt3ca; 3 07ada05 needs < o4fkt39a; 3 07imb05 needs < m2vkt21a; 5 14iob6, Creator 5 14iob6, and Gaming 5 14iob6 need < m3gkt3da; G5 14amr05 needs < o4zkt2ba. If your version is lower than the threshold, you are in the affected range.
    Affected if Your installed firmware version is below the threshold listed for your specific model, indicating the vulnerable 534D0740 DXE driver is present.
  4. Inspect NVRAM variables for unexpected modifications
    Use a UEFI shell tool, firmware configuration utility, or third-party UEFI variable inspection tool to dump and review NVRAM variables. Look for any NVRAM entries that were not created by expected system firmware or operating system installers, particularly persistent boot-related or configuration variables.
    Affected if Unexpected NVRAM variables exist that you did not create, suggesting possible exploitation of this vulnerability for persistence.
  5. Check for signs of unauthorized firmware-level persistence
    After a clean OS reinstall, verify that boot behavior remains consistent and that no unexpected boot entries, device option ROMs, or firmware-level configurations reappear. Compare current boot configuration against a known-good baseline if available.
    Affected if Boot behavior or configuration changed after a clean OS reinstall without your action, indicating firmware-level persistence that could stem from this vulnerability.

You are affected if your Ideacentre model matches one of the eight listed models AND your installed firmware version is below the threshold specified for that model.

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 that patch the 534D0740 DXE driver memory leak; verify NVRAM integrity after patching to ensure no malicious persistence.

Recommended fix Moderate confidence

Firmware version >= o4hkt3ca (C5 14imb05, G5 14imb05), >= o4fkt39a (3 07ada05), >= m2vkt21a (3 07imb05), >= m3gkt3da (5 14iob6, Creator 5 14iob6, Gaming 5 14iob6), >= o4zkt2ba (G5 14amr05)

  1. 1. Identify the specific Ideacentre model number from the affected product list
  2. 2. Visit support.lenovo.com and search for the model or navigate to the product's support page
  3. 3. Locate the Drivers & Software section and download the latest BIOS/firmware update
  4. 4. Ensure the device is connected to power and do not interrupt the update process
  5. 5. Run the firmware update utility or follow the BIOS update instructions provided by Lenovo
  6. 6. After the update completes, verify the firmware version has been updated to or beyond the fixed version (o4hkt3ca, o4fkt39a, m2vkt21a, m3gkt3da, or o4zkt2ba depending on model)
Caveat Firmware updates carry a risk of bricking the device if interrupted; ensure stable power during update

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
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA2.0 h
18.0 hours of engineering $3,200
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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