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

CVE-2023-22351

MEDIUM · 6.1 CVSS v3.1 Published 2024-09-16
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
63/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
Out-of-bounds write in UEFI firmware for some Intel(R) Processors may allow a privileged user to potentially enable escalation of privilege via local access.

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

This is an out-of-bounds write vulnerability in UEFI firmware affecting certain Intel processors. The flaw allows a privileged local user to potentially escalate privileges by writing beyond allocated memory boundaries in the firmware, which runs at the highest privilege level (below the OS).

MitigationApply Intel-provided UEFI/BIOS firmware updates to affected processors. This requires coordinated deployment across affected systems, typically during scheduled maintenance windows, as firmware updates carry risk of rendering systems unbootable if interrupted.

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
High
Privileges
High
User interaction
None
Scope
Changed
Confidentiality
None
Integrity
High
Availability
Low

CVSS:3.1/AV:L/AC:H/PR:H/UI:N/S:C/C:N/I:H/A:L

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 Intel processor model
    Run 'wmic cpu get name,processorid' on Windows or 'cat /proc/cpuinfo' on Linux to identify the exact Intel CPU model
    Affected if Processor is one of the affected Intel CPU families listed in Intel's advisory for this CVE
  2. Check UEFI/BIOS firmware version
    On Windows, run 'wmic bios get smbiosbiosversion' or check in System Information. On Linux, run 'dmidecode -s bios-version' or check /sys/class/dmi/id/bios_version
    Affected if Installed UEFI/BIOS version falls within the vulnerable version range for your specific Intel processor as documented by Intel
  3. Verify UEFI boot mode is active
    On Windows, run 'msinfo32' and check 'BIOS Mode'. On Linux, run 'test -d /sys/firmware/efi && echo UEFI || echo Legacy'
    Affected if System boots in UEFI mode (required for this vulnerability to be exploitable)
  4. Confirm local privileged access exists
    Check for users with administrator/root privileges on the system using 'whoami /priv' on Windows or 'id' on Linux
    Affected if Attacker already has privileged local access, which is required to exploit this vulnerability

You are affected if your Intel processor model is in the affected list and your installed UEFI/BIOS version is within the vulnerable version range published by Intel for that processor.

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 Intel-provided UEFI/BIOS firmware updates to affected processors. This requires coordinated deployment across affected systems, typically during scheduled maintenance windows, as firmware updates carry risk of rendering systems unbootable if interrupted.

Have this fixed Scoped from the published advisory
  • Consultation8.0 h
  • Implementation16.0 h
  • Testing8.0 h
  • Review / QA4.0 h
36.0 hours of engineering $6,400
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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