Robert Merget

**Name of the Vulnerable Software and Affected Versions** Cisco Webex Meetings (affected versions not specified) **Description** A vulnerability in the meeting-join functionality of Cisco Webex Meetings could allow an unauthenticated, network-proximate attacker to complete a meeting-join process in place of an intended user. This was due to client certificate validation issues. An attacker could exploit this by monitoring local wireless or adjacent networks for client-join requests and attempting to interrupt and complete the meeting-join flow as another user. A successful exploit could allow the attacker to join the meeting as another user. The Cisco Product Security Incident Response Team (PSIRT) is not aware of any malicious use of this vulnerability. **Recommendations** 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: Apache HTTP Server versions through 2.4.63 Description: In certain mod ssl configurations, a man-in-the-middle attacker can hijack an HTTP session through a TLS upgrade attack. This issue affects configurations utilizing “SSLEngine optional” to enable TLS upgrades. The attack is related to HTTP desynchronization. Recommendations: Upgrade to version 2.4.64, which removes support for TLS upgrade.

**Name of the Vulnerable Software and Affected Versions** Oracle Java SE versions 11.0.17, 17.0.5, 19.0.1 Oracle GraalVM Enterprise Edition versions 20.3.8, 21.3.4, 22.3.0 **Description** The issue is related to an easily exploitable vulnerability in the JSSE component of Oracle Java SE and Oracle GraalVM Enterprise Edition. This vulnerability allows an unauthenticated attacker with network access via DTLS to compromise the system, resulting in a partial denial of service. The vulnerability applies to Java deployments that load and run untrusted code, such as sandboxed Java Web Start applications or sandboxed Java applets, and rely on the Java sandbox for security. **Recommendations** For Oracle Java SE versions 11.0.17, 17.0.5, 19.0.1, update to a newer version that contains a fix for this issue. For Oracle GraalVM Enterprise Edition versions 20.3.8, 21.3.4, 22.3.0, update to a newer version that contains a fix for this issue. As a temporary workaround, consider restricting access to the DTLS protocol to minimize the risk of exploitation. Note: 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** Zyxel GS1900 series firmware versions prior to V2.70 **Description** An insufficient entropy issue, caused by the improper use of randomness sources with low entropy for RSA key pair generation, affects the web administration interface. This could allow an unauthenticated attacker to retrieve a private key by factoring the RSA modulus N in the certificate. **Recommendations** For Zyxel GS1900 series firmware versions prior to V2.70, update to version V2.70 or later to resolve the issue. As a temporary workaround, consider restricting access to the web administration interface until the update can be applied.

**Name of the Vulnerable Software and Affected Versions** Windows HTML Platforms (affected versions not specified) **Description** The issue is related to errors in privilege management within the Windows HTML Platform component of the Windows operating system. This can allow a remote attacker to bypass existing security restrictions. **Recommendations** 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** wolfSSL versions prior to 4.5.0 **Description** An issue was discovered in the DTLS handshake implementation. Clear DTLS application data messages in epoch 0 do not produce an out-of-order error, instead, these messages are returned to the application. **Recommendations** For versions prior to 4.5.0, update to version 4.5.0 or later to resolve the issue.

**Name of the Vulnerable Software and Affected Versions** Java SE versions 11.0.6 and 14 **Description** The issue is related to insufficient access control in the JSSE component of Java SE, allowing an unauthenticated attacker with network access via HTTPS to compromise Java SE. Successful attacks can result in unauthorized update, insert, or delete access to some of Java SE's accessible data, as well as unauthorized read access to a subset of Java SE's accessible data. This issue can be exploited through sandboxed Java Web Start applications, sandboxed Java applets, or by supplying data to APIs in the specified component without using sandboxed applications or applets. **Recommendations** For Java SE version 11.0.6, update to a version that includes the fix for this issue. For Java SE version 14, update to a version that includes the fix for this issue. As a temporary workaround, consider restricting access to the JSSE component until a patch is available. Avoid using the JSSE component for sensitive operations until the issue is resolved.

**Name of the Vulnerable Software and Affected Versions** Oracle Solaris version 11 **Description** The issue is related to inadequate access control in the Consolidation Infrastructure component of Oracle Solaris, allowing a low-privileged attacker with logon access to the infrastructure to compromise Oracle Solaris. Successful attacks require human interaction from a person other than the attacker and can significantly impact additional products, potentially resulting in the takeover of Oracle Solaris. **Recommendations** For Oracle Solaris version 11, consider restricting access to the Consolidation Infrastructure component 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** Java SE versions 11.0.5 and 13.0.1 **Description** The issue is related to a vulnerability in the Java Secure Socket Extension (JSSE) component of Oracle Java SE, which is difficult to exploit and allows an unauthenticated attacker with network access via HTTPS to compromise Java SE. This can result in unauthorized update, insert, or delete access to some of Java SE's accessible data, as well as unauthorized read access to a subset of Java SE's accessible data. The vulnerability applies to Java deployments that load and run untrusted code and rely on the Java sandbox for security. It can also be exploited by using APIs in the specified component. **Recommendations** For Java SE version 11.0.5, update to a version that contains a fix for this issue. For Java SE version 13.0.1, update to a version that contains a fix for this issue. As a temporary workaround, consider restricting access to the JSSE component until a patch is available. Avoid using the JSSE component for client authentication until the issue is resolved.

**Name of the Vulnerable Software and Affected Versions** Ruby versions 2.4.7 and earlier, 2.5.x through 2.5.6, and 2.6.x through 2.6.4 **Description** The issue allows code injection if the first argument to `Shell#[]` or `Shell#test` in lib/shell.rb is untrusted data. An attacker can exploit this to call an arbitrary Ruby method. This is due to incorrect neutralization of special elements in output used by an incoming component. **Recommendations** For Ruby versions 2.4.7 and earlier, update to version 2.4.8. For Ruby versions 2.5.x through 2.5.6, update to version 2.5.7. For Ruby versions 2.6.x through 2.6.4, update to version 2.6.5. As a temporary workaround, consider validating and sanitizing the first argument to `Shell#[]` and `Shell#test` to prevent code injection.