CVE-2023-45078
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 DustFilterAlertSmm 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 confidenceA memory leakage vulnerability in the DustFilterAlertSmm SMM (System Management Mode) driver could allow a local attacker with elevated privileges to leak memory and write to NVRAM variables, potentially persisting malicious configuration changes at the firmware level.
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 modelCheck the system model number on the physical device or via system information (e.g., 'wmic computersystem get model' or 'systeminfo' on Windows)Affected if Model is one of: Ideacentre C5 14imb05, Ideacentre 3 07ada05, Ideacentre 3 07imb05, Ideacentre G5 14imb05, Ideacentre 5 14iob6, Ideacentre Creator 5 14iob6, Ideacentre G5 14amr05, or Ideacentre Gaming 5 14iob6
-
Check the BIOS/firmware versionAccess the UEFI/BIOS setup (press F1 or Delete at boot) and locate the BIOS Version/Build information, or use a tool like 'wmic bios get smbiosbiosversion' on Windows or 'dmidecode -s bios-version' on LinuxAffected if Firmware version is below the threshold for the specific model (C5 14imb05/G5 14imb05: < o4hkt3ca; 3 07ada05: < o4fkt39a; 3 07imb05: < m2vkt21a; 5 14iob6/Creator 5 14iob6/Gaming 5 14iob6: < m3gkt3da; G5 14amr05: < o4zkt2ba)
-
Verify the DustFilterAlertSmm driver presenceThis SMM driver is embedded in the firmware and not directly visible from the operating system. Check vendor firmware release notes or use the vendor's BIOS update utility which typically lists included drivers/componentsAffected if The firmware contains the DustFilterAlertSmm SMM driver (this driver exists in all affected firmware versions before the fix)
The system is affected if it is one of the listed Ideacentre models AND the installed firmware version is lower than the version threshold for that model, meaning the patched DustFilterAlertSmm driver has not been applied.
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-supplied BIOS/firmware update containing the patched DustFilterAlertSmm driver to remediate the memory leak and prevent unauthorized NVRAM writes.
Upgrade to firmware version o4hkt3ca (for C5 14imb05, G5 14imb05), o4fkt39a (for 3 07ada05), m2vkt21a (for 3 07imb05), m3gkt3da (for 5 14iob6, Creator 5 14iob6, Gaming 5 14iob6), or o4zkt2ba (for G5 14amr05)
- 1. Identify the exact Ideacentre model number from the affected list (C5 14imb05, 3 07ada05, 3 07imb05, G5 14imb05, 5 14iob6, Creator 5 14iob6, G5 14amr05, or Gaming 5 14iob6)
- 2. Visit support.lenovo.com and navigate to the Drivers & Downloads section for your specific model
- 3. Locate the BIOS/firmware update corresponding to the fixed version number for your model (o4hkt3ca, o4fkt39a, m2vkt21a, m3gkt3da, or o4zkt2ba)
- 4. Download the firmware update package
- 5. Follow Lenovo's firmware update instructions, which typically require running the update utility from Windows or creating a bootable USB update disk
- 6. Ensure the system remains powered on during the entire firmware update process
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation2.0 h
- Testing8.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,928.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-45078 — 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-45078 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