CVE Vulnerabilities


Uncontrolled Search Path Element

Published: May 10, 2023 | Modified: Nov 07, 2023
CVSS 3.x
CVSS 2.x

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


The product uses a fixed or controlled search path to find resources, but one or more locations in that path can be under the control of unintended actors.

Affected Software

Name Vendor Start Version End Version
Advisor Intel * 2023.0 (excluding)
Cpu_runtime Intel * 2023.0 (excluding)
Distribution_for_python Intel * 2023.0 (excluding)
Dpc++_compatibility_tool Intel * 2023.0 (excluding)
Embree_ray_tracing_kernel_library Intel * 2023.0 (excluding)
Fortran_compiler Intel * 2023.0 (excluding)
Implicit_spmd_program_compiler Intel * 1.18.1 (excluding)
Inspector Intel * 2023.0 (excluding)
Integrated_performance_primitives Intel * 2021.7 (excluding)
Integrated_performance_primitives_cryptography Intel * 2021.6.3 (excluding)
Mpi_library Intel * 2021.8 (excluding)
Oneapi_base_toolkit Intel * 2023.0 (excluding)
Oneapi_data_analytics_library Intel * 2023.0 (excluding)
Oneapi_deep_neural_network_library Intel * 2023.0 (excluding)
Oneapi_dpc++/c++_compiler Intel * 2023.0 (excluding)
Oneapi_dpc++_library Intel * 2022.0 (excluding)
Oneapi_hpc_toolkit Intel * 2023.0.0 (excluding)
Oneapi_hpc_toolkit Intel 2023.0.0 (including) 2023.0.0 (including)
Oneapi_iot_toolkit Intel * 2023.0 (excluding)
Oneapi_math_kernel_library Intel * 2023.0 (excluding)
Oneapi_rendering_toolkit Intel * 2023.0 (excluding)
Oneapi_threading_building_blocks Intel * 2021.8 (excluding)
Oneapi_toolkit_and_component_software_installers Intel * (excluding)
Oneapi_video_processing_library Intel * 2023.0 (excluding)
Open_image_denoise Intel * 1.4.3 (excluding)
Open_volume_kernel_library Intel * 2023.0 (excluding)
Ospray Intel * 2023.0 (excluding)
Ospray_studio Intel * 2023.0 (excluding)
Trace_analyzer_and_collector Intel * 2021.8.0 (excluding)
Vtune_profiler Intel * 2023.0 (excluding)

Extended Description

Although this weakness can occur with any type of resource, it is frequently introduced when a product uses a directory search path to find executables or code libraries, but the path contains a directory that can be modified by an attacker, such as “/tmp” or the current working directory. In Windows-based systems, when the LoadLibrary or LoadLibraryEx function is called with a DLL name that does not contain a fully qualified path, the function follows a search order that includes two path elements that might be uncontrolled:

In some cases, the attack can be conducted remotely, such as when SMB or WebDAV network shares are used. One or more locations in that path could include the Windows drive root or its subdirectories. This often exists in Linux-based code assuming the controlled nature of the root directory (/) or its subdirectories (/etc, etc), or a code that recursively accesses the parent directory. In Windows, the drive root and some of its subdirectories have weak permissions by default, which makes them uncontrolled. In some Unix-based systems, a PATH might be created that contains an empty element, e.g. by splicing an empty variable into the PATH. This empty element can be interpreted as equivalent to the current working directory, which might be an untrusted search element. In software package management frameworks (e.g., npm, RubyGems, or PyPi), the framework may identify dependencies on third-party libraries or other packages, then consult a repository that contains the desired package. The framework may search a public repository before a private repository. This could be exploited by attackers by placing a malicious package in the public repository that has the same name as a package from the private repository. The search path might not be directly under control of the developer relying on the framework, but this search order effectively contains an untrusted element.

Potential Mitigations