Glassy

**Name of the Vulnerable Software and Affected Versions** Apache IoTDB versions 1.0.0 through 1.2.2 **Description** The issue is a Remote Code Execution vulnerability in Apache IoTDB, which exists due to insufficient input validation. This allows a remote attacker to execute arbitrary code. Users are recommended to upgrade to a fixed version. **Recommendations** For Apache IoTDB versions 1.0.0 through 1.2.2, upgrade to version 1.3.0, which fixes the issue.

**Name of the Vulnerable Software and Affected Versions** Oracle WebLogic Server versions 12.2.1.4.0 through 14.1.1.0.0 **Description** The issue is related to insufficient input validation in the Core component of Oracle WebLogic Server, allowing an unauthenticated attacker with network access via T3 or IIOP to compromise the server. Successful attacks can result in unauthorized access to critical data or complete access to all Oracle WebLogic Server accessible data. Approximately 2,992,153 devices are potentially affected, mainly distributed in the United States, Japan, and other countries. **Recommendations** For versions 12.2.1.4.0 and 14.1.1.0.0, update to a version that includes the fix for this issue, as specified in Oracle's January 2024 patch advisory. As a temporary workaround, consider restricting access to the T3 and IIOP protocols to minimize the risk of exploitation. Avoid using vulnerable API endpoints, such as those related to JNDI injection, until the issue is resolved.

**Name of the Vulnerable Software and Affected Versions** Oracle WebLogic Server versions 10.3.6.0.0 through 14.1.1.0.0 **Description** The issue is related to insufficient access control in the Console component of Oracle WebLogic Server, allowing a remote attacker to gain full control over the application via the HTTP protocol. This can result in the takeover of Oracle WebLogic Server. The vulnerability is easily exploitable and can be used by a high-privileged attacker with network access. **Recommendations** For Oracle WebLogic Server versions 10.3.6.0.0 through 14.1.1.0.0, update to a version that includes the fix for this issue. At the moment, there is no information about a newer version that contains a fix for this vulnerability.