CVE-2023-25945 is a medium severity (CVSS 6.7) protection mechanism failure in Intel One Boot Flash Update (OFU) software. An authenticated local user could escalate privileges. Versions before 14.1.31 are affected, so update to 14.1.31 or later and read Intel advisory SA-00927.
What's affected
The record says Intel OFU software before version 14.1.31 is affected, and the product entry is Intel One Boot Flash Update. The advisory is Intel SA-00927. Intel's site blocked my automated request, so I could not read the advisory's fixed version table. The version statement here is from the NVD text only.
The weakness is CWE-693, protection mechanism failure. In plain terms a safeguard that should limit what a user can do does not work as intended. The vector is local, high complexity, low privileges, user interaction required, with high confidentiality, integrity and availability impact.
OFU is firmware update tooling. Its job is to write to firmware, so a flaw that lets a user cross a privilege boundary here is worth taking seriously, even though the score is medium. No second severity figure was available, so there is no conflict to report.
How to check if you're exposed
Look for the installed tool on Windows endpoints:
Get-ItemProperty HKLM:\Software\Microsoft\Windows\CurrentVersion\Uninstall\*,
HKLM:\Software\WOW6432Node\Microsoft\Windows\CurrentVersion\Uninstall\* |
Where-Object DisplayName -match "OFU|One Boot Flash" |
Select-Object DisplayName, DisplayVersion
If you receive firmware tooling from a board or system vendor, the vendor may bundle OFU under a different product name. Ask the vendor for the version in your bundle and for their fixed release. Anything below 14.1.31 needs attention.
To see which of your own applications pull in affected components, run the free in-browser dependency scan at gold.safeguard.sh/scan.
What to do now
- Read SA-00927 for the fixed version and supported platforms.
- Inventory OFU installations, including copies bundled by system vendors.
- Update to 14.1.31 or later.
- Remove the tool from machines that do not need it.
- Control who can run firmware update tooling on shared machines.
Why it matters
Protection mechanism failure is a broad label. It means a check that was meant to stop misuse did not stop it. For firmware update tools, the stakes are higher than the score suggests because the tool touches low level code.
The attacker needs a local account and some interaction, so exposure is narrow. It still belongs in the patch cycle for any fleet where users have standard accounts on shared hardware. The record does not flag the CVE in CISA KEV.
Quick check
What is fixed in 14.1.31?
The record says versions before 14.1.31 are affected. Read Intel SA-00927 for details, as I could not load it.
Can it be exploited remotely?
The record rates the vector as local, so a remote attacker would need a prior foothold.
Sources
Last reviewed: 19 October 2026.