cve.bz

CVE-2023-22355 intel: Uncontrolled Search Path Element

7.8 highEPSS 0.2%

High (7.8) in intel. EPSS 0.2% estimated probability of exploitation activity in the next 30 days.

On this page
Uncontrolled search path in some Intel(R) oneAPI Toolkit and component software installers before version 4.3.0.251 may allow an authenticated user to potentially enable escalation of privilege via local access.

Severity

CVSS 3.1

7.8 high
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
EPSS
0.2% (unchanged from 0.2% a week ago; 0.2% 30 days ago) estimated probability of exploitation activity in the next 30 days; 11th percentile. Scored 2026-11-21. A forecast for this CVE across the internet, not for your own systems.
CISA's assessment (SSVC)
Exploitation: none · Automatable: no · Technical impact: total, assessed 2025-01-24. From CISA's Vulnrichment in the CVE List: whether it is exploited, whether exploiting it can be automated, and how much control it gives.
CWE
CWE-427 Uncontrolled Search Path Element
OWASP Top 10
A08:2025 Software or Data Integrity Failures
Published
Modified
NVD analysis
Analyzed, since modified
Record from
the NVD, synced

Fix and patched versions

Ask an AI about this CVE

Show the promptExplain CVE-2023-22355 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2023-22355?via=ask-ai-copy and https://cve.bz/cve/CVE-2023-22355?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2023-22355 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.

Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.

Affected

Versions

From the NVD's CPE matches.

ProductAffected
intel:advisorbefore 2023.0
intel:cpu_runtimebefore 2023.0
intel:distribution_for_pythonbefore 2023.0
intel:dpc++_compatibility_toolbefore 2023.0
intel:embree_ray_tracing_kernel_librarybefore 2023.0
intel:fortran_compilerbefore 2023.0
intel:implicit_spmd_program_compilerbefore 1.18.1
intel:inspectorbefore 2023.0
intel:integrated_performance_primitivesbefore 2021.7
intel:integrated_performance_primitives_cryptographybefore 2021.6.3
intel:mpi_librarybefore 2021.8
intel:oneapi_base_toolkitbefore 2023.0
intel:oneapi_data_analytics_librarybefore 2023.0
intel:oneapi_deep_neural_network_librarybefore 2023.0
intel:oneapi_dpc++/c++_compilerbefore 2023.0
intel:oneapi_dpc++_librarybefore 2022.0
intel:oneapi_hpc_toolkitbefore 2023.0.0
intel:oneapi_hpc_toolkit2023.0.0
intel:oneapi_iot_toolkitbefore 2023.0
intel:oneapi_math_kernel_librarybefore 2023.0
intel:oneapi_rendering_toolkitbefore 2023.0
intel:oneapi_threading_building_blocksbefore 2021.8
intel:oneapi_toolkit_and_component_software_installersbefore 4.3.0.251
intel:oneapi_video_processing_librarybefore 2023.0
intel:open_image_denoisebefore 1.4.3
intel:open_volume_kernel_librarybefore 2023.0
intel:ospraybefore 2023.0
intel:ospray_studiobefore 2023.0
intel:trace_analyzer_and_collectorbefore 2021.8.0
intel:vtune_profilerbefore 2023.0

Attack patterns (CAPEC)

  • CAPEC-38 Leveraging/Manipulating Configuration File Search Paths Likelihood: High · Severity: Very High
  • CAPEC-471 Search Order Hijacking Severity: Medium

The attack patterns MITRE's CAPEC relates to this record's weaknesses, as MITRE names them. Credits.

References

Check your stackJSON