dbcve.org
Incorrect Default PermissionsWeakness · CWE-276

CVE-2025-27711

MEDIUM · 6.7 CVSS v3.1 Published 2025-11-11
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
67/100
Remediation priority · Elevated

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
Incorrect default permissions for some Intel(R) One Boot Flash Update (Intel(R) OFU) software before version 14.1.31 within Ring 3: User Applications may allow an escalation of privilege. Unprivileged software adversary with an authenticated user combined with a high complexity attack may enable escalation of privilege. This result may potentially occur via local access when attack requirements are present without special internal knowledge and requires active user interaction. The potential vulnerability may impact the confidentiality (high), integrity (high) and availability (high) of the vulnerable system, resulting in subsequent system confidentiality (none), integrity (none) and availability (none) impacts.

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

Intel(R) One Boot Flash Update software before version 14.1.31 contains incorrect default permissions in Ring 3 user applications, potentially allowing an authenticated unprivileged user to escalate privileges through a high-complexity local attack requiring active user interaction.

MitigationUpdate Intel OFU to version 14.1.31 or later to apply corrected default permissions.

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
Low
User interaction
Required
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:L/AC:H/PR:L/UI:R/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. Verify Intel One Boot Flash Update is installed
    Check for Intel OFU in installed programs via Windows Settings > Apps & Features, or run 'wmic product get name,version' and look for 'Intel(R) One Boot Flash Update'
    Affected if The software is not installed (not affected) or is installed (proceed to version check)
  2. Determine installed version of Intel OFU
    Right-click Intel OFU in Programs and Features > Properties, or check the version in the software's About/Help section, or locate the executable (typically in C:\Program Files\Intel\ or C:\Program Files (x86)\Intel\) and view its file properties
    Affected if Version cannot be determined (unknown status)
  3. Compare installed version against 14.1.31
    Compare the version found in step 2 to 14.1.31 using standard version comparison
    Affected if Installed version is lower than 14.1.31 (for example, 14.1.30, 14.0.x, or earlier)
  4. Confirm user account type and authentication status
    Verify the user account attempting to exploit this would be an authenticated but non-privileged user on the system (check via Computer Management > Local Users and Groups or 'whoami /all' command)
    Affected if System allows authenticated non-administrator users to log in and the vulnerable software is present
  5. Verify Ring 3 application permissions (if version is affected)
    Use icacls or Sysinternals AccessChk to examine permissions on Intel OFU executable files and associated user-mode applications - look for overly permissive ACLs allowing write or execute by standard users
    Affected if Non-privileged users have elevated permissions on OFU executables (this confirms exploitability but version check in step 3 is primary indicator)

A system is affected if Intel One Boot Flash Update is installed with a version lower than 14.1.31 and the system allows authenticated non-administrator users to access the vulnerable software.

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.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Update Intel OFU to version 14.1.31 or later to apply corrected default permissions.

Recommended fix High confidence

14.1.31

  1. Identify the current version of Intel(R) One Boot Flash (Intel(R) OFU) software installed on the system
  2. Navigate to the official Intel support website or security advisory page for CVE-2025-27711
  3. Download the Intel OFU software version 14.1.31 or later from Intel's official download center
  4. Verify the integrity of the downloaded package using checksums provided by Intel
  5. Close any running applications and ensure the system is connected to a stable power source
  6. Run the Intel OFU installer with administrative privileges
  7. Follow the on-screen prompts to complete the installation
  8. Restart the system as prompted to ensure the update takes effect
Caveat Firmware/BIOS update utilities may carry inherent risks; ensure backup and follow Intel's update documentation precisely

Generated from the published advisory — verify against the referenced sources before acting.

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing2.0 h
  • Review / QA1.0 h
9.0 hours of engineering $1,600
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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