Ludwig Stage

**Name of the Vulnerable Software and Affected Versions** UCI IDOL 2 versions through 2.12 **Description** An issue was discovered in the encryption mechanism used by UCI IDOL 2. Data sent between the client and server is encrypted, but the key is derived from a static string "(c)2007 UCI Software GmbH B.Boll". This key is hardcoded, allowing an attacker with access to messages to decrypt and encrypt them, thus enabling passive and active man-in-the-middle attacks. **Recommendations** For versions through 2.12, consider disabling the encryption mechanism that uses the static key until a patch is available. Restrict access to sensitive data and minimize the risk of exploitation by implementing additional security measures, such as monitoring network traffic for suspicious activity. 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** UCI IDOL 2 versions through 2.12 **Description** An issue was discovered in UCI IDOL 2 due to improper input validation, improper deserialization, and improper restriction of operations within the bounds of a memory buffer. This issue makes UCI IDOL 2 vulnerable to Denial-of-Service (DoS) attacks and possibly remote code execution. There is an access violation and EIP overwrite after five logins. **Recommendations** For UCI IDOL 2 versions through 2.12, consider disabling the login functionality until a patch is available to prevent potential Denial-of-Service (DoS) attacks and remote code execution. Restrict access to the system to minimize the risk of exploitation. Avoid using the system for critical operations 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** UCI IDOL 2 versions through 2.12 **Description** The issue is caused by improper input validation, improper deserialization, and improper restriction of operations within the bounds of a memory buffer. This makes UCI IDOL 2 vulnerable to Denial-of-Service (DoS) attacks and possibly remote code execution. A certain XmlMessage document can cause 100% CPU consumption. **Recommendations** For versions through 2.12, consider disabling the processing of XmlMessage documents until a patch is available to prevent 100% CPU consumption and potential Denial-of-Service (DoS) attacks. 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** UCI IDOL 2 versions through 2.12 **Description** An issue was discovered in UCI IDOL 2, where data is transferred over a raw socket without any authentication mechanism. Thus, communication endpoints are not verifiable. **Recommendations** For versions through 2.12, consider disabling the use of raw sockets until a patch is available. Restrict access to the communication endpoints to minimize the risk of 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** UCI IDOL 2 versions through 2.12 **Description** An issue was discovered in UCI IDOL 2 due to improper input validation, improper deserialization, and improper restriction of operations within the bounds of a memory buffer. This makes IDOL2 vulnerable to Denial-of-Service (DoS) attacks and possibly remote code execution via the `xB0x00x3c` byte sequence. **Recommendations** For versions through 2.12, consider disabling the functionality that allows deserialization of user-input data until a patch is available. Restrict access to the vulnerable module to minimize the risk of exploitation. Avoid using the vulnerable byte sequence `xB0x00x3c` in the affected API endpoint 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** Postman versions through 6.3.0 **Description** An information-disclosure issue was discovered in Postman. It validates a server's X.509 certificate and presents an error if the certificate is not valid. Unfortunately, the associated HTTPS request data is sent anyway, with only the response not being displayed. Thus, all contained information of the HTTPS request is disclosed to a man-in-the-middle attacker, for example, user credentials. **Recommendations** For Postman versions through 6.3.0, update to a version later than 6.3.0 to resolve the issue. As a temporary workaround, consider disabling HTTPS requests in Postman until a patch is available. Restrict access to sensitive information when using Postman to minimize the risk of exploitation. Avoid using Postman to send sensitive information over HTTPS until the issue is resolved.