CVE-2023-45079
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 memory leakage vulnerability was reported in the NvmramSmm SMM 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 confidenceMemory leakage vulnerability in the NvmramSmm SMM (System Management Mode) driver allows a local attacker with elevated privileges to write to NVRAM variables. The leak occurs due to improper memory management in the SMM driver, potentially allowing memory exhaustion or controlled memory overwrite for privilege escalation.
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< o4hkt3ca< m3gkt3da< m3gkt3da< o4zkt2ba< m3gkt3daCVSS 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 Ideacentre modelRun 'wmic csproduct get name' or check system documentation to confirm the exact model number (e.g., Ideacentre C5 14imb05, Ideacentre 3 07ada05, etc.)Affected if Model is not one of the eight listed affected Ideacentre models
-
Check current firmware versionAccess the system BIOS/UEFI setup (press F1 or Del at boot) and note the BIOS/firmware version, or use 'wmic bios get smbiosbiosversion' from an elevated command promptAffected if Firmware version cannot be retrieved or is not visible
-
Compare firmware version against thresholdsCompare your installed firmware version to the affected version ranges: Ideacentre C5 14imb05 requires o4hkt3ca or higher, Ideacentre 3 07ada05 requires o4fkt39a or higher, Ideacentre 3 07imb05 requires m2vkt21a or higher, Ideacentre G5 14imb05 requires o4hkt3ca or higher, Ideacentre 5 14iob6 requires m3gkt3da or higher, Creator 5 14iob6 requires m3gkt3da or higher, Ideacentre G5 14amr05 requires o4zkt2ba or higher, Ideacentre Gaming 5 14iob6 requires m3gkt3da or higherAffected if Installed firmware version is older (lexicographically lower) than the required version for your specific model
You are affected if you own one of the eight listed Ideacentre models and your current firmware version is below the specified threshold for that model.
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 vendor-provided firmware updates that patch the NvmramSmm driver memory management. Since this is an SMM driver vulnerability, standard OS-level patches will not address it; firmware/BIOS update from the system OEM is required.
Update to firmware version o4hkt3ca (C5 14imb05, G5 14imb05), o4fkt39a (07ada05), m2vkt21a (07imb05), m3gkt3da (5 14iob6, Creator 5 14iob6, Gaming 5 14iob6), or o4zkt2ba (G5 14amr05) as appropriate for your model
- 1. Identify the exact model number of the affected Lenovo Ideacentre system by checking the system label or BIOS information.
- 2. Determine the current firmware version installed on the system - this can typically be found in the BIOS setup (F1 on boot) under 'System Information' or via the Lenovo Vantage/Legacy Update utility.
- 3. Navigate to the official Lenovo support website (support.lenovo.com) and enter the specific model number (e.g., 14imb05, 07ada05, 07imb05, 14iob6, 14amr05) to locate firmware downloads.
- 4. Download the BIOS/firmware update package corresponding to the fixed version for your model: o4hkt3ca, o4fkt39a, m2vkt21a, m3gkt3da, or o4zkt2ba as applicable.
- 5. Follow Lenovo's firmware update instructions - this usually involves running the update executable while the system is plugged into AC power and not interrupting the update process.
- 6. After the firmware update completes, verify the new firmware version matches or exceeds the fixed version listed.
- 7. Reboot the system to ensure the updated SMM driver loads with the security fix.
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation10.0 h
- Implementation16.0 h
- Testing12.0 h
- Review / QA8.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $12,992.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-45079 — 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-45079 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