Xu Yuanzhen

**Name of the Vulnerable Software and Affected Versions** IBM Db2 JDBC Driver for Db2 for Linux, UNIX and Windows versions 10.5, 11.1, and 11.5 **Description** The issue is related to an unchecked logger injection in the IBM Db2 JDBC Driver, which could allow a remote authenticated attacker to execute arbitrary code on the system. This can be achieved by sending a specially crafted request using the `traceFile` property. The vulnerability is also described as being related to incorrect code generation management. **Recommendations** For versions 10.5, 11.1, and 11.5, consider disabling the use of the `traceFile` property until a patch is available to prevent exploitation. As a temporary workaround, restrict access to the system to minimize the risk of remote authenticated attackers exploiting this issue. At the moment, there is no information about a newer version that contains a fix for this vulnerability.

**Name of the Vulnerable Software and Affected Versions** IBM Db2 JDBC Driver for Db2 for Linux, UNIX and Windows versions 10.5, 11.1, and 11.5 **Description** The issue is related to incorrect code generation management in the IBM DB2 database management system's JDBC client driver. It allows a remote attacker to execute arbitrary code on the system by sending a specially crafted request using the `pluginClassName` class. This is caused by an unchecked class instantiation when providing plugin classes. **Recommendations** For versions 10.5, 11.1, and 11.5, consider restricting access to the `pluginClassName` class to minimize the risk of exploitation until a patch is available. At the moment, there is no information about a newer version that contains a fix for this vulnerability.

**Name of the Vulnerable Software and Affected Versions** IBM Db2 JDBC Driver for Db2 for Linux, UNIX and Windows versions 10.5, 11.1, and 11.5 **Description** The issue is related to incorrect code generation management in the IBM DB2 JDBC driver, which could allow a remote authenticated attacker to execute arbitrary code. By sending a specially crafted request using the `clientRerouteServerListJNDIName` property, an attacker could exploit this to execute arbitrary code on the system. **Recommendations** For versions 10.5, 11.1, and 11.5, consider disabling the use of the `clientRerouteServerListJNDIName` property until a patch is available to prevent exploitation. At the moment, there is no information about a newer version that contains a fix for this vulnerability.

**Name of the Vulnerable Software and Affected Versions** IBM Informix JDBC Driver versions 4.10 and 4.50 **Description** The issue allows for remote code execution via JNDI injection when the driver code or the application using the driver does not verify the supplied LDAP URL in the Connect String. **Recommendations** For IBM Informix JDBC Driver versions 4.10 and 4.50, consider verifying the supplied LDAP URL in the Connect String to prevent JNDI injection attacks. As a temporary workaround, consider restricting the use of the Connect String or the LDAP URL until a patch is available. At the moment, there is no information about a newer version that contains a fix for this vulnerability.

**Name of the Vulnerable Software and Affected Versions** MySQL Connectors versions 8.0.26 and prior **Description** A difficult to exploit vulnerability in MySQL Connectors allows a high privileged attacker with network access via multiple protocols to compromise the system. Successful attacks can result in unauthorized access to critical data or complete access to all accessible data and the ability to cause a hang or frequently repeatable crash of MySQL Connectors. **Recommendations** For versions 8.0.26 and prior, update to a version that contains a fix for this issue. At the moment, there is no information about a newer version that contains a fix for this vulnerability.

**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.

**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 input validation in the Oracle WebLogic Server, allowing a remote attacker to execute arbitrary code via the IIOP protocol. This can result in the takeover of the Oracle WebLogic Server. The vulnerability can be easily exploited by an unauthenticated attacker with network access. **Recommendations** For versions 10.3.6.0.0, 12.1.3.0.0, 12.2.1.3.0, 12.2.1.4.0, and 14.1.1.0.0, consider disabling the IIOP protocol until a patch is available to prevent exploitation. As a temporary workaround, restrict access to the Core component of the Oracle WebLogic Server to minimize the risk of exploitation. Avoid using the IIOP protocol in the affected Oracle WebLogic Server versions until the issue is resolved. At the moment, there is no information about a newer version that contains a fix for this vulnerability.

**Name of the Vulnerable Software and Affected Versions** Oracle WebLogic Server versions 10.3.6.0.0 through 12.2.1.4.0 **Description** The issue is related to inadequate access control in the Console component of Oracle WebLogic Server, allowing an unauthenticated attacker with network access via HTTP to compromise the server. Successful attacks require human interaction from a person other than the attacker and can result in unauthorized update, insert, or delete access to some of the server's accessible data. **Recommendations** For versions 10.3.6.0.0, 12.1.3.0.0, 12.2.1.3.0, and 12.2.1.4.0, consider restricting access to the Console component until a patch is available. As a temporary workaround, consider disabling remote access via HTTP to minimize the risk of exploitation. Restrict access to sensitive data to prevent unauthorized updates, inserts, or deletes. At the moment, there is no information about a newer version that contains a fix for this vulnerability.