dbcve.org
Out-of-bounds WriteWeakness · CWE-787

CVE-2023-5912

MEDIUM · 6.7 CVSS v3.1 Published 2024-04-05
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 potential memory leakage vulnerability was reported in some Lenovo Notebook products 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 Lenovo notebook firmware allowing a local attacker with elevated privileges to write to NVRAM variables, potentially enabling persistent firmware-level modifications.

MitigationApply Lenovo firmware updates for affected notebook models; verify NVRAM integrity after patching.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

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 Lenovo notebook model
    Run 'wmic computersystem get manufacturer,model' or check system BIOS information
    Affected if System is not a Lenovo notebook - not affected by this specific vulnerability
  2. Check installed firmware version
    Access Lenovo Vantage or BIOS setup, or run 'wmic bios get smbiosbiosversion' to retrieve firmware version
    Affected if Firmware version falls within the affected range for your specific model (compare against Lenovo security advisory for your model)
  3. Verify NVRAM write access is available
    Check if NVRAM tools like 'nvram' command or Lenovo firmware update utilities can write to NVRAM variables
    Affected if NVRAM write access is exposed to local users with elevated privileges
  4. Inspect NVRAM variables for unauthorized changes
    Use 'nvram -p' or similar tool to list all NVRAM variables, compare against known good baseline or documentation
    Affected if Unexpected or modified NVRAM variables are present that were not intentionally configured
  5. Check for firmware-level persistence mechanisms
    Review system for unexpected firmware blobs, check secure boot status, and look for unsigned firmware modifications
    Affected if Signs of persistent firmware-level changes that could indicate exploitation

A user is affected if they have a Lenovo notebook with firmware in the vulnerable version range AND the system allows elevated-privilege users to write to NVRAM variables.

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.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Apply Lenovo firmware updates for affected notebook models; verify NVRAM integrity after patching.

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing1.0 h
  • Review / QA1.0 h
6.0 hours of engineering $1,090
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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