Intel(R) oneAPI DPC++/C++ Compiler software: Improper Access Control
CVE-2023-35121 is a high-severity improper access control vulnerability in Intel(R) oneAPI DPC++/C++ Compiler software, with a CVSS 3.1 base score of 7.8 out of 10. It can be exploited with local access to the system by an attacker with a low-privileged account, without any action from a user. Affected Intel(R) oneAPI DPC++/C++ Compiler software versions: before version 2023.2.1. The record does not name a fixed version, so check the vendor advisory. There is no confirmed exploitation so far. EPSS estimates a 0.16% chance of exploitation within 30 days, which is low compared with other CVEs.
High severity with no evidence of exploitation so far.
What to do
- Update advisor to 2023.2.0 or a later version.
- Update inspector to 2023.2.0 or a later version.
- Update oneapi_ai_analytics_toolkit to 2023.2 or a later version.
- Read the advisory on intel.com for workarounds and exact fixed builds.
Affected products and versions
| Vendor | Product | Affected versions | Fixed in |
|---|---|---|---|
| Intel(R) oneAPI DPC++/C++ Compiler software | Intel(R) oneAPI DPC++/C++ Compiler software | before version 2023.2.1 | Not stated |
| Intel | advisor | before 2023.2.0 | 2023.2.0 |
| Intel | inspector | before 2023.2.0 | 2023.2.0 |
| Intel | oneapi_ai_analytics_toolkit | before 2023.2 | 2023.2 |
| Intel | oneapi_base_toolkit | before 2023.2.0 | 2023.2.0 |
| Intel | oneapi_deep_neural_network | before 2023.2.0 | 2023.2.0 |
| Intel | oneapi_hpc_toolkit | before 2023.2.0 | 2023.2.0 |
| Intel | oneapi_iot_toolkit | before 2023.2.0 | 2023.2.0 |
| Intel | Cluster Checker | 2021.7.3 | Not stated |
| Intel | Distribution For Python | 2023.1 | Not stated |
| Intel | Integrated Performance Primitives | 2021.9 | Not stated |
| Intel | Integrated Performance Primitives Cryptography | before 2021.8 | 2021.8 |
| Intel | Mpi Library | before 2021.10 | 2021.10 |
| Intel | Oneapi Math Kernel Library | before 2023.2 | 2023.2 |
| Intel | Threading Building Blocks | before 2021.10 | 2021.10 |
| Intel | Trace Analyzer And Collector | 2021.10.0 | Not stated |
| Intel | Vtune Profiler | before 2023.2 | 2023.2 |
Version data comes from the organisation that assigned the CVE. Confirm against the vendor advisory before deciding you are unaffected.
How the severity score breaks down
- Attack vector
- LocalThe attacker needs local access or must trick a user into running something.
- Attack complexity
- HighSuccess depends on conditions outside the attacker's control.
- Privileges required
- LowA basic user account is enough.
- User interaction
- NoneNo action by a victim is required.
- Scope
- ChangedThe attack can reach beyond the vulnerable component into other systems.
- Confidentiality
- HighAll data handled by the component can be read.
- Integrity
- HighData or code can be modified at will.
- Availability
- HighThe component can be taken down completely.
Vector: CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:C/C:H/I:H/A:H. Scored by CNA (intel.com).
Official description
Improper access control in the Intel(R) oneAPI DPC++/C++ Compiler before version 2022.2.1 for some Intel(R) oneAPI Toolkits before version 2022.3.1 may allow authenticated user to potentially enable escalation of privilege via local access.
Source: the CVE record as published by its numbering authority, via NVD and CVE.org.
The underlying weakness: Improper Access Control
The product does not restrict or incorrectly restricts access to a resource from an unauthorized actor.
How developers prevent this class of flaw
- Very carefully manage the setting, management, and handling of privileges. Explicitly manage trust zones in the software.
- Compartmentalize the system to have safe areas where trust boundaries can be unambiguously drawn. Do not allow sensitive data to go outside of the trust boundary and always be careful when interfacing with a compartment outside of the safe area. Ensure that appropriate compartmentalization is built into the system design, and the compartmentalization allows for and reinforces privilege separation functionality. Architects and designers should rely on the principle of least privilege to decide the appropriate time to use privileges and the time to drop privileges.
Timeline
- CVE record published.
- CISA published its SSVC assessment (exploitation: none, automatable: no, technical impact: total).
- Record last changed materially (score, affected products, status or references).
References
Recent Improper Access Control vulnerabilities
- 9.8 Critical severity
- 7.8 High severity
- 7.8 High severity
- 7.8 High severity
- 7.8 High severity
- 7.8 High severity
Spotted an error? Tell us.