dbcve.org
Oneapi CliApplication · Intel

CVE-2022-25992

HIGH · 7.8 CVSS v3.1 Published 2023-02-16
Fix available
A fix is available. Upgrade to 0.2.0 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
Insecure inherited permissions in the Intel(R) oneAPI Toolkits oneapi-cli before version 0.2.0 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

This is a local privilege escalation vulnerability in Intel's oneAPI CLI tool (oneapi-cli) versions prior to 0.2.0. The issue stems from insecure inherited permissions, where files or processes created by the tool inherit overly permissive access controls that allow authenticated local users to modify executables or configuration files and elevate privileges.

MitigationUpgrade oneapi-cli to version 0.2.0 or later to obtain the patched binary with corrected permission settings. Conduct a permission audit on systems where the tool was previously installed to ensure no lingering insecure artifacts remain.

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 CliApplication
Affected:< 0.2.0

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 oneapi-cli installation and version
    Run 'oneapi-cli --version' or check the installation location using 'where oneapi-cli' (Windows) or 'which oneapi-cli' (Linux). Also check any package manager records if installed via package managers.
    Affected if The installed version is below 0.2.0 or the version cannot be determined but the tool is present
  2. Audit permissions on oneapi-cli executables
    Inspect file permissions on the oneapi-cli binary and its installation directory. On Windows, check ACLs using 'icacls' or the Security tab. On Linux, check with 'ls -la' or 'stat'. Look for any entries granting write access to non-admin users.
    Affected if Non-privileged users have write permission to the oneapi-cli binary or its installation directory
  3. Review oneapi-cli configuration files for overly permissive access
    Locate configuration files created or used by oneapi-cli (check default installation paths and user profile directories). Use file permission tools to verify ACLs on these files.
    Affected if Configuration files are writable by authenticated local users other than the administrator or owner
  4. Check for spawned processes and their child artifacts
    If oneapi-cli has been run, examine any created files or processes in the system. Look for temporary files, logs, or spawned executables and verify their permission settings.
    Affected if Files created by oneapi-cli operations are writable by other local users, allowing privilege escalation through modification

A user is affected if Intel oneapi-cli version 0.2.0 or later is not installed, or if the tool or its artifacts have permissions allowing authenticated local users to modify executables or configuration files.

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 0.2.0 or later
Fixed in 0.2.0
Interim mitigation

Upgrade oneapi-cli to version 0.2.0 or later to obtain the patched binary with corrected permission settings. Conduct a permission audit on systems where the tool was previously installed to ensure no lingering insecure artifacts remain.

Recommended fix Moderate confidence

0.2.0 or later

  1. Check current oneapi-cli version using: oneapi-cli --version or oneapi-cli --help
  2. Download Intel oneAPI Toolkit version 0.2.0 or later from the official Intel website (www.intel.com)
  3. Install the updated oneapi-cli package following Intel's installation documentation
  4. Verify the installation by checking the version: oneapi-cli --version
  5. Ensure the version shows 0.2.0 or higher

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

Fix this in Oneapi Cli Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA4.0 h
22.0 hours of engineering $3,860
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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