Kaveh Razavi

A side channel vulnerability on some of the AMD CPUs may allow an attacker to influence the return address prediction. This may result in speculative execution at an attacker-controlled address, potentially leading to information disclosure. The vulnerability, also known as Inception, is a novel transient execution attack that leaks arbitrary data on all AMD Zen CPUs in the presence of all previously deployed software- and hardware mitigations.

The issue is related to aliases in the branch predictor of some AMD processors, which may cause them to predict the wrong branch type. This could potentially lead to information disclosure. The vulnerability is associated with incorrect branch type prediction, allowing an attacker to disclose protected information.

The issue is related to mis-trained branch predictions for return instructions, which may allow arbitrary speculative code execution under certain microarchitecture-dependent conditions. This can lead to the disclosure of protected information from kernel memory or enable an attack on the host system from virtual machines. An attacker with unprivileged user access can hijack return instructions to achieve arbitrary speculative code execution.

The issue is related to an unprotected alternative channel of return branch target prediction in some Intel(R) Processors, which may allow an authorized user to potentially enable information disclosure via local access. The RSBA behavior allows alternate branch predictors to be used by near RET instructions when the RSB is empty. When eIBRS is enabled, the predicted target of these alternate predictors are restricted to those belonging to the indirect branch predictor entries of the current prediction domain.

The issue is related to errors in processing the `ret` instruction, which retrieves an address for transition from the stack. This can allow an attacker to disclose protected information from kernel memory or launch an attack on the host system from virtual machines. An attacker with unprivileged user access can hijack return instructions to achieve arbitrary speculative code execution under certain microarchitecture-dependent conditions.

The issue is related to the `vt ioctl` function, specifically the `vt setactivate` call, where the `array index nospec` mechanism fails to properly sanitize an out-of-bounds value, leading to a transient integer underflow. The `vsa.console` value should be decreased first and then sanitized with `array index nospec` to prevent this issue.

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.

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 Microarchitectural Data Sampling Uncacheable Memory (MDSUM) on some microprocessors that utilize speculative execution. This may allow an authenticated user with local access to potentially enable information disclosure via a side channel. An attacker with local access to a targeted system may exploit this issue to obtain data on the targeted system, causing some information leakage.

The issue is related to Microarchitectural Fill Buffer Data Sampling (MFBDS), which may allow an authenticated user to potentially enable information disclosure via a side channel with local access. This is due to the speculative execution utilized by some microprocessors.

The issue is related to Microarchitectural Load Port Data Sampling (MLPDS), which may allow an authenticated user to potentially enable information disclosure via a side channel with local access. This is due to the incorrect implementation of saving outdated operation results in the load port table. The exploitation of this issue can allow an attacker to access confidential information.

Name of the Vulnerable Software and Affected Versions: No specific software or versions are mentioned. Description: A hardware vulnerability in GPU memory modules enables attackers to accelerate micro-architectural attacks through the use of the JavaScript WebGL API. Recommendations: At the moment, there is no information about a newer version that contains a fix for this vulnerability.

The issue is related to the Kernel Samepage Merging (KSM) component in the Linux kernel, which does not prevent the use of a write-timing side channel. This allows guest OS users to defeat the Address Space Layout Randomization (ASLR) protection mechanism on other guest OS instances via a Cross-VM ASL Introspection (CAIN) attack. The vendor suggests disabling deduplication to mitigate this attack vector. This issue can be classified as a potentially misunderstood behavior rather than a vulnerability, as share-until-written approaches for memory conservation among mutually untrusting tenants are inherently detectable for information disclosure.

An issue in the kernel ION subsystem could allow a local malicious application to execute arbitrary code within the context of the kernel, potentially leading to a local permanent device compromise. This may require reflashing the operating system to repair the device.

The issue is related to a buffer overflow in Unicode processing within the logging functionality. This can be triggered by sending a command with a long argument, which then causes a buffer overflow when an admin selects the Logging section in the FTP server main window, potentially allowing remote authenticated users to execute arbitrary code.

The issue allows remote attackers to execute arbitrary SQL commands via the `password` field in the login.asp file. This can potentially lead to unauthorized access and data manipulation.