CVE-2024-31155
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 · uneditedImproper buffer restrictions in the 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 confidenceThis is a UEFI firmware vulnerability in certain Intel processors involving improper buffer restrictions, likely allowing a buffer overflow. A privileged local user can exploit this to escalate their privileges. The vulnerability requires local access and existing privileged credentials to execute the exploit.
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
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:L/AC:H/PR:H/UI:N/S:C/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 Intel processor modelRun 'wmic cpu get name' on Windows or 'cat /proc/cpuinfo | grep "model name"' on Linux to retrieve the processor modelAffected if The processor is an Intel CPU that falls within the affected product families (check Intel advisory for specific model numbers)
-
Check the current UEFI/BIOS firmware versionOn Windows, run 'wmic bios get smbiosbiosversion' or check the BIOS setup screen. On Linux, run 'dmidecode -s bios-version'Affected if The installed firmware version matches an affected version listed in Intel's security advisory for this CVE
-
Verify system has local administrator/root privilegesCheck if the current user has elevated privileges: run 'whoami /priv' on Windows or 'id' on LinuxAffected if The user already possesses privileged credentials (this is a prerequisite for exploitation, not an indicator of compromise)
-
Confirm UEFI/BIOS is not in a known secure stateIf available, check Intel Processor Diagnostic Tool or system manufacturer utilities for firmware integrity statusAffected if Firmware integrity checks fail or reveal unauthorized modifications
Your environment is affected if you are running an Intel processor within the affected families AND your current UEFI/BIOS firmware version matches an affected version listed in the Intel security advisory for CVE-2024-31155.
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.
From vendor dataApply the Intel firmware update for affected processors once available. Verify system inventory to identify affected hardware, test firmware updates in a controlled environment before production deployment, and ensure secure firmware update mechanisms are used.
- Consultation8.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,352.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-31155 — 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-2024-31155 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