CVE-2023-28823
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 · uneditedUncontrolled search path in some Intel(R) oneAPI Toolkit and component software installers before version 4.3.1.493 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 · high confidenceUncontrolled search path vulnerability in Intel oneAPI Toolkit and component installers allows DLL hijacking, potentially enabling an authenticated local user to load malicious libraries and escalate privileges.
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< 2023.1< 2023.1< 2023.1< 2023.1< 2023.1< 2023.1< 1.19.1< 2023.1CVSS 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
- Required
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:L/AC:L/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 checksWork through these to decide whether this CVE applies to you.
-
Check if Intel oneAPI Toolkit or affected components are installedOn Windows, search for Intel software in C:\Program Files\Intel\ or check Add/Remove Programs. On Linux, check /opt/intel/ or look for packages starting with 'intel-' or 'oneAPI'.Affected if Any of these Intel products are present: Intel Advisor, Intel CPU Runtime for OpenCL, Intel Distribution for Python, Intel DPC++ Compatibility Tool, Intel Embree, Intel Fortran Compiler, Intel Implicit SPMD Program Compiler, or Intel Inspector.
-
Identify installed Intel oneAPI component versionsFor each found Intel product, check its version using the product's executable with --version flag, or look for version information in the product's installation directory (often in a version.txt file or in the executable's properties).Affected if The installed version is less than 2023.1 (or less than 1.19.1 for Intel Implicit Spmd Program Compiler).
-
Check for multiple affected Intel installationsReview all Intel development tools installed on the system, as multiple components may be affected simultaneously.Affected if Multiple Intel oneAPI components are installed and any are below the fixed version.
If any Intel oneAPI component (Advisor, CPU Runtime for OpenCL, Distribution for Python, DPC++ Compatibility Tool, Embree, Fortran Compiler, Implicit SPMD Program Compiler, or Inspector) is installed at a version below 2023.1 (or below 1.19.1 for Implicit SPMD Program Compiler), the system is vulnerable to DLL hijacking and local privilege escalation.
Generated from the published advisory. Verify against your own configuration.
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 · scoped1.19.12023.1
Upgrade Intel oneAPI Toolkit and all affected component installers to version 4.3.1.493 or later to eliminate the uncontrolled search path.
Intel oneAPI Toolkit and components version 2023.1 or later (specifically 4.3.1.493)
- Obtain the updated Intel oneAPI Toolkit or component software from the official Intel download center
- Ensure you download version 2023.1 or later for the affected products (Cpu Runtime For Opencl Applications, Distribution For Python, Dpc++ Compatibility Tool, Embree, Fortran Compiler, Inspector For Oneapi, Advisor For Oneapi)
- For Implicit Spmd Program Compiler, obtain version 1.19.1 or later
- Install the updated software following Intel's standard installation procedures
- Verify the installed version matches or exceeds the fixed release (2023.1 / 4.3.1.493)
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation1.0 h
- Implementation1.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,376.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-28823 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2023-28823 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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