Jidoc01

Name of the Vulnerable Software and Affected Versions: Oracle VM VirtualBox versions prior to 6.1.20 Description: The issue is related to insufficient input validation in the Core component of Oracle VM VirtualBox, allowing a low-privileged attacker with logon access to the infrastructure to compromise Oracle VM VirtualBox. Successful attacks can result in unauthorized access to critical data or complete access to all Oracle VM VirtualBox accessible data. Recommendations: For versions prior to 6.1.20, update to version 6.1.20 or later to resolve the issue. As a temporary workaround, consider restricting access to the Core component of Oracle VM VirtualBox to minimize the risk of exploitation.

Name of the Vulnerable Software and Affected Versions: Oracle VM VirtualBox versions prior to 6.1.18 Description: The issue exists due to insufficient input validation in the Core component of Oracle VM VirtualBox. Exploitation of this issue may allow an attacker to cause a denial of service, resulting in a hang or frequently repeatable crash of Oracle VM VirtualBox. Successful attacks can significantly impact additional products. The vulnerability can be easily exploited by a high-privileged attacker with logon to the infrastructure where Oracle VM VirtualBox executes. Recommendations: For versions prior to 6.1.18, update to version 6.1.18 or later to resolve the issue. As a temporary workaround, consider restricting access to the Core component of Oracle VM VirtualBox to minimize the risk of exploitation.

**Name of the Vulnerable Software and Affected Versions** Oracle VM VirtualBox versions prior to 6.1.20 **Description** The issue is related to incorrect handling of drdynvc packets in the Core component of Oracle VM VirtualBox. This can be exploited by a remote attacker to execute arbitrary code or gain full control of the application using the RDP protocol. The vulnerability is difficult to exploit and allows an unauthenticated attacker with network access via RDP to compromise Oracle VM VirtualBox, potentially resulting in a takeover of the application. **Recommendations** For versions prior to 6.1.20, update to version 6.1.20 or later to resolve the issue. As a temporary workaround, consider restricting access to the RDP protocol to minimize the risk of exploitation.