Alyssa Milburn

The issue is related to insufficient granularity of access control in UEFI firmware, which may allow an authenticated user to potentially enable denial of service via local access.

The issue is related to improper Finite State Machines (FSMs) in the hardware logic of some Intel(R) Processors. This may allow a privileged user to potentially enable denial of service via local access.

The issue is related to an untrusted pointer dereference in some Intel(R) Graphics Drivers, which may allow an authenticated user to potentially enable escalation of privilege via local access.

The issue is related to information exposure through microarchitectural state after transient execution from some register files for some Intel(R) Atom(R) Processors. This may allow an authenticated user to potentially enable information disclosure via local access. The vulnerability is caused by the possibility of determining residual information from the register files of the processor, which are used for shared storage of register contents in all tasks on the same CPU core. The estimated number of potentially affected devices worldwide is not available.

A sequence of processor instructions can lead to unexpected behavior in some Intel processors, potentially allowing an authenticated user to enable escalation of privilege, information disclosure, or denial of service via local access. This issue is related to the interpretation of redundant prefixes and can cause the system to crash or become unresponsive. The vulnerability, termed Reptar, primarily affects multi-tenant virtualized environments where multiple virtual machines are run on the same host.

The issue is related to insufficient control flow management in the BIOS firmware for some Intel(R) Processors. This may allow a privileged user to potentially enable denial of service via local access.

The issue is related to insufficient protection of internal data in the Windows operating system, which can allow an attacker to gain unauthorized access to protected information. This can enable attackers to obtain sensitive information and affect the system.

The issue is related to the implementation of the Indirect Branch Prediction Barrier (IBPB) mechanism in AMD processor microcode, which may lead to a potential information disclosure due to incorrect clearing of the Return Address Stack (RAS). This could allow an attacker to obtain sensitive information using a side channel. The vulnerability is being actively exploited.

The issue is related to non-transparent sharing of return predictor targets between contexts in some Intel(R) Processors, which may allow an authorized user to potentially enable information disclosure via local access. This could be linked to errors in handling the RET instruction after virtual machine exit, potentially allowing an attacker to execute arbitrary code.

The issue is related to the LFENCE/JMP module in AMD CPUs, specifically concerning the branch prediction mechanism. This allows an attacker to access protected memory from a program without the necessary privileges by exploiting indirect branch prediction.

Name of the Vulnerable Software and Affected Versions: BOINC (affected versions not specified) Description: The issue allows remote attackers to execute arbitrary SQL commands via unspecified vectors, due to multiple SQL injection vulnerabilities. Recommendations: At the moment, there is no information about a newer version that contains a fix for this vulnerability.

The issue is related to cleanup errors in some data cache evictions for some Intel(R) Processors, which may allow an authenticated user to potentially enable information disclosure via local access. This is caused by a data leak from the L1D cache. The vulnerability can be exploited to disclose protected information. Researchers have found a new speculative execution vulnerability in Intel CPUs that could let attackers leak targeted sensitive data from the OS kernel, co-resident virtual machines, and even from Intel's secured SGX enclave.

The issue is related to cleanup errors in some Intel(R) processors, which may allow an authenticated user to potentially enable information disclosure via local access. This is connected to a leak in the store buffer of results from reading vector registers, which are modified during the execution of vector instructions. An attacker could exploit this to disclose protected information.

Name of the Vulnerable Software and Affected Versions: Linaro/OP-TEE OP-TEE versions prior to v3.4.0 Description: The issue is related to boundary checks in the optee os component. This could lead to corruption of any memory that the TA can access. Recommendations: For versions prior to v3.4.0, update to version v3.4.0 to resolve the issue. As a temporary workaround, consider restricting access to sensitive memory areas to minimize the risk of exploitation.

Name of the Vulnerable Software and Affected Versions: Linaro/OP-TEE versions prior to 3.4.0 Description: The issue is a buffer overflow in the optee os component, allowing execution of code in the TEE core (kernel) context. Recommendations: For versions prior to 3.4.0, update to version 3.4.0 or later to resolve the issue.

Name of the Vulnerable Software and Affected Versions: Linaro/OP-TEE OP-TEE versions prior to 3.4.0 Description: The issue is related to a buffer overflow in the optee os component, which can lead to code execution in the context of the TEE core (kernel). Recommendations: For versions prior to 3.4.0, update to version 3.4.0 or later to resolve the issue.

Name of the Vulnerable Software and Affected Versions: Linaro/OP-TEE OP-TEE versions 3.3.0 and earlier Description: The issue affects the `optee os` component and is related to a buffer overflow, which can lead to memory corruption and disclosure of memory content. Recommendations: For versions 3.3.0 and earlier, update to version 3.4.0 or later to resolve the issue.

Name of the Vulnerable Software and Affected Versions: Linaro/OP-TEE versions prior to 3.4.0 Description: The issue is related to a rounding error in the optee os component, potentially leading to the leakage of code and/or data from previous Trusted Applications. Recommendations: For versions prior to 3.4.0, update to version 3.4.0 or later to resolve the issue.

Name of the Vulnerable Software and Affected Versions: Linaro/OP-TEE versions prior to 3.4.0 Description: The issue affects the optee os component and can lead to memory corruption of the TEE itself due to boundary crossing. Recommendations: For versions prior to 3.4.0, update to version 3.4.0 or later to resolve the issue.

Name of the Vulnerable Software and Affected Versions: Linaro/OP-TEE versions prior to 3.4.0 Description: The issue is related to a buffer overflow in the optee os component, which can lead to code execution in the context of the TEE core (kernel). Recommendations: For versions prior to 3.4.0, update to version 3.4.0 or later to resolve the issue.