dbcve.org
Incorrect Default PermissionsWeakness · CWE-276

CVE-2025-20087

MEDIUM · 6.7 CVSS v3.1 Published 2025-08-12
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) oneAPI DPC++/C++ Compiler software installers may allow an authenticated 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

The Intel oneAPI DPC++/C++ Compiler installers set overly permissive default file system permissions on installed files and directories. This allows authenticated local users to modify or replace executable files, libraries, or configuration files that may be used by higher-privileged processes, potentially enabling local privilege escalation.

MitigationAudit and remediate file system permissions on the Intel compiler installation directory post-installation, restricting write access to administrator accounts only. Apply any vendor-supplied patches when available.

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. Locate Intel oneAPI DPC++/C++ Compiler installation directory
    Check common installation paths such as C:\Program Files\Intel\oneAPI (Windows) or /opt/intel/oneapi (Linux). Use commands: on Windows - 'dir /s /b "C:\Program Files\Intel\oneAPI\*' or check registry at HKEY_LOCAL_MACHINE\SOFTWARE\Intel\oneAPI; on Linux - 'ls -la /opt/intel/oneapi'
    Affected if The compiler is installed in a directory that exists on the system
  2. Verify if installation directory allows write access by non-privileged users
    On Windows, right-click the oneAPI folder, go to Properties > Security, and check permissions for Users orAuthenticated Users group. On Linux, run 'ls -ld /opt/intel/oneapi' and check if the directory has write permission for 'others' or non-admin groups
    Affected if Users or authenticated users group has Write or Modify permissions on the installation directory
  3. Inspect executable files (.exe, .dll, .so) in the compiler directory for overly broad permissions
    On Windows, use icacls 'C:\Program Files\Intel\oneAPI\*' or examine a sample directory recursively. On Linux, run 'find /opt/intel/oneapi -type f -perm -o=w' to find files writable by others
    Affected if Executable files, libraries, or binaries are writable by non-admin users or the 'others' group
  4. Check configuration files for write access by standard users
    Examine config files in the oneAPI directory (typically in subfolders like compiler, lib, or config). Use 'icacls' on Windows or 'ls -la' on Linux to view permissions on .json, .xml, or .cfg configuration files
    Affected if Configuration files used by the compiler are modifiable by non-privileged accounts
  5. Test write access with a standard user account (if permissible in your environment)
    As a non-administrator user, attempt to create or modify a test file in the oneAPI installation directory: on Windows - 'echo test > C:\Program Files\Intel\oneAPI\test_write.txt'; on Linux - 'touch /opt/intel/oneapi/test_write.txt'
    Affected if A standard user account can successfully create or modify files in the compiler installation directory

If the Intel oneAPI DPC++/C++ Compiler is installed and its directory structure permits write access by non-privileged users (Users/Authenticated Users group or 'others'), the environment is affected by this vulnerability.

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

Audit and remediate file system permissions on the Intel compiler installation directory post-installation, restricting write access to administrator accounts only. Apply any vendor-supplied patches when available.

Have this fixed Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA2.0 h
18.0 hours of engineering $3,200
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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