Quictester

Name of the Vulnerable Software and Affected Versions: Quicly versions up to commtit d720707 Description: Quicly is an IETF QUIC protocol implementation. It is susceptible to a denial-of-service attack. A remote attacker can exploit these bugs to trigger an assertion failure that crashes the process using quicly. Recommendations: For Quicly versions up to commtit d720707, update to a version that includes commit 2a95896104901589c495bc41460262e64ffcad5c to address the vulnerability. As a temporary workaround, consider implementing measures to prevent remote attackers from triggering assertion failures, such as restricting access to the quicly process or monitoring for suspicious activity.

Name of the Vulnerable Software and Affected Versions: Picotls versions prior to the latest release Description: The issue arises when parsing a spoofed TLS handshake message, causing picotls to attempt to free the same memory twice. This double free occurs during the disposal of multiple objects without any intervening calls to malloc. Typically, this triggers the malloc implementation to detect the error and abort the process. However, depending on the internals of malloc and the crypto backend being used, the flaw could potentially lead to a use-after-free scenario, which might allow for arbitrary code execution. Recommendations: Update to the latest release to mitigate risks. As a temporary workaround, consider restricting the use of the crypto backend until a patch is available. Avoid using the vulnerable bindings within picotls that call the crypto libraries until the issue is resolved.

**Name of the Vulnerable Software and Affected Versions** Kwik version 745fd4e2 **Description** The TLS engine does not track the current state of the connection, allowing Client Hello messages to be overwritten at any time, including after a connection has been established. **Recommendations** For version 745fd4e2, consider disabling the TLS engine until a patch is available to prevent Client Hello messages from being overwritten. Restrict access to the TLS engine to minimize the risk of exploitation. Avoid using the TLS engine for establishing connections until the issue is resolved.

**Name of the Vulnerable Software and Affected Versions** Kwik commit 745fd4e2 **Description** The issue arises from Kwik not properly discarding unused encryption keys. **Recommendations** For commit 745fd4e2, ensure that unused encryption keys are properly discarded to mitigate the issue.

**Name of the Vulnerable Software and Affected Versions** PQUIC versions prior to 5bde5bb **Description** The issue allows attackers to disrupt a connection with a PSK configuration by sending a CONNECTION CLOSE frame that is encrypted via the initial key computed. Network traffic sniffing is needed as part of exploitation. **Recommendations** For versions prior to 5bde5bb, update to a version after 5bde5bb to resolve the issue. As a temporary workaround, consider restricting the use of the initial encryption key to minimize the risk of exploitation.

**Name of the Vulnerable Software and Affected Versions** quinn-proto versions prior to 0.9.5 quinn-proto versions prior to 0.10.5 **Description** Receiving unknown QUIC frames in a QUIC packet could result in a panic. The issue was reported by the QUIC Tester research group and was not found by the fuzzing infrastructure. **Recommendations** For quinn-proto versions prior to 0.9.5, update to version 0.9.5 or later to resolve the issue. For quinn-proto versions prior to 0.10.5, update to version 0.10.5 or later to resolve the issue.