dbcve.org
Oneapi Ai Analytics ToolkitApplication · Intel

CVE-2023-29242

HIGH · 7.8 CVSS v3.1 Published 2023-05-12
Fix available
A fix is available. Upgrade to after 2021.1 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
Improper access control for Intel(R) oneAPI Toolkits before version 2021.1 Beta 10 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

Intel oneAPI Toolkits before version 2021.1 Beta 10 contains an improper access control vulnerability that allows an authenticated local user to escalate privileges. The vulnerability stems from insufficient access control mechanisms within the toolkit installation.

MitigationUpdate Intel oneAPI Toolkits to version 2021.1 Beta 10 or later to remediate the improper access control vulnerability.

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 Ai Analytics ToolkitApplication
Affected:<= 2021.1
Oneapi Base ToolkitApplication
Affected:<= 2021.1
Oneapi Dl Framework Developer ToolkitApplication
Affected:<= 2021.1
Oneapi Hpc ToolkitApplication
Affected:<= 2021.1
Oneapi Iot ToolkitApplication
Affected:<= 2021.1
Oneapi Rendering ToolkitApplication
Affected:<= 2021.1

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. Identify installed Intel oneAPI Toolkits
    Check for Intel oneAPI toolkit installations by searching for 'Intel' or 'oneAPI' in installed programs (Windows: Registry or Programs and Features; Linux: dpkg, rpm, or /opt directory listings)
    Affected if Any Intel oneAPI toolkit is found installed on the system
  2. Determine the installed toolkit version
    Locate the version information for each installed toolkit. Common locations: installation directory metadata, version.txt file, or running the toolkit's version command (e.g., oneAPI environment variables or --version flag)
    Affected if The installed version cannot be determined or shows a version <= 2021.1
  3. Compare version against affected range
    If version is retrieved, compare it to the affected range: any version <= 2021.1 is vulnerable. Versions prior to 2021.1 Beta 10 are affected
    Affected if Installed version is 2021.1 or any earlier version (e.g., 2020.x, 1.x series)
  4. Confirm the specific toolkit type
    Identify which of the affected toolkits are present: AI Analytics Toolkit, Base Toolkit, DL Framework Developer Toolkit, HPC Toolkit, IoT Toolkit, or Rendering Toolkit
    Affected if Any of these six toolkits are installed at version <= 2021.1

The system is affected if any Intel oneAPI Toolkit (AI Analytics, Base, DL Framework Developer, HPC, IoT, or Rendering) is installed at version 2021.1 or earlier.

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 a release after 2021.1
Interim mitigation

Update Intel oneAPI Toolkits to version 2021.1 Beta 10 or later to remediate the improper access control vulnerability.

Recommended fix High confidence

Intel oneAPI Toolkit 2021.1 Beta 10 or later

  1. 1. Identify the currently installed Intel oneAPI Toolkit version by checking the installation directory or running 'intel64 --version' or reviewing installed programs
  2. 2. Download Intel oneAPI Toolkit version 2021.1 Beta 10 or later from the official Intel website or download center
  3. 3. If upgrading in-place: Uninstall the current version through Windows Add/Remove Programs or the installer, then install the new version
  4. 4. If using a package manager: Run the update command (e.g., 'apt update && apt upgrade' for Linux or check for updates via package manager)
  5. 5. Verify the new version is installed by checking the version information again
  6. 6. Confirm the vulnerability is addressed by reviewing the Intel security advisory for CVE-2023-29242
Caveat Review release notes for 2021.1 Beta 10 for any API changes, deprecated features, or compatibility considerations with existing projects

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

Fix this in Oneapi Ai Analytics Toolkit Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing2.0 h
  • Review / QA2.0 h
10.0 hours of engineering $1,780
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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