dbcve.org
Oneapi Rendering ToolkitApplication · Intel

CVE-2021-33071

HIGH · 7.8 CVSS v3.1 Published 2021-11-17
Fix available
A fix is available. Upgrade to 2021.2 or later.
See remediation →
80/100
Remediation priority · High
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
Incorrect default permissions in the installer for the Intel(R) oneAPI Rendering Toolkit before version 2021.2 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 Rendering Toolkit installer before version 2021.2 sets overly permissive default file and directory permissions, allowing an authenticated local user to modify installation artifacts and potentially escalate privileges by gaining write access to files that execute with elevated permissions.

MitigationUpgrade to Intel oneAPI Rendering Toolkit version 2021.2 or later, which corrects the default permission settings in the installer.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Oneapi Rendering ToolkitApplication
Affected:< 2021.2

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

CVSS:3.1/AV:L/AC:L/PR:L/UI:N/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. Check if Intel OneAPI Rendering Toolkit is installed
    Locate the installation directory. Common paths include: C:\Program Files\Intel\oneAPI\ or /opt/intel/oneapi/. Check for the presence of the 'rendering' toolkit folder or look in the main oneAPI directory for rendering-related subdirectories.
    Affected if The product is installed in the environment and the installation directory exists.
  2. Determine the installed version
    Look for a version file or check the installer log in the installation directory. Common locations: <install_dir>/version.txt or check the Windows Registry under HKEY_LOCAL_MACHINE\SOFTWARE\Intel\oneAPI\RenderingToolkit or review the original installer filename if available.
    Affected if The installed version is found to be lower than 2021.2.
  3. Inspect file permissions on the installation directory
    On Windows: Right-click the installation folder, go to Properties > Security tab. On Linux: Run 'ls -la <install_dir>' to view permissions. Check if standard users have Write or Modify permissions to the main installation folders.
    Affected if Authenticated local users have Write or Modify permissions to installation directories that should be restricted to administrators.
  4. Check for world-writable files in the installation
    On Windows: Use icacls.exe to list permissions. Example: 'icacls "C:\Program Files\Intel\oneAPI\Rendering" /T'. On Linux: Run 'find <install_dir> -type f -perm -002'. Look for files with Write permissions granted to Users or Everyone.
    Affected if Executable files or configuration files in the installation directory are writable by non-privileged users.
  5. Identify files that execute with elevated privileges
    Review the installation for service executables, scheduled tasks, or scripts that run as SYSTEM/root. Check the oneAPI startup scripts and any service configurations in the rendering toolkit folder.
    Affected if Files that execute with elevated privileges are writable by standard users, allowing potential privilege escalation.

The environment is affected if Intel OneAPI Rendering Toolkit is installed with a version prior to 2021.2 and the installation directory or its contents grant Write permissions to non-privileged authenticated users.

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
Upgrade available Upgrade to 2021.2 or later
Fixed in 2021.2
Interim mitigation

Upgrade to Intel oneAPI Rendering Toolkit version 2021.2 or later, which corrects the default permission settings in the installer.

Recommended fix High confidence

2021.2

  1. Upgrade Intel(R) oneAPI Rendering Toolkit to version 2021.2 or later
  2. After upgrading, verify that default file and directory permissions are correctly set (no world-writable permissions)
  3. If upgrading is not immediately possible, review and manually restrict permissions on installed files and directories to remove excessive access

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

Fix this in Oneapi Rendering Toolkit Scoped from the published advisory
  • Consultation2.0 h
  • Implementation6.0 h
  • Testing3.0 h
  • Review / QA2.0 h
13.0 hours of engineering $2,290
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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