Kurohiro

**Name of the Vulnerable Software and Affected Versions** curl (affected versions not specified) **Description** The issue is related to a flaw in curl where it inadvertently keeps the SSL session ID for connections in its cache even when the verify status (OCSP stapling) test failed. This allows a subsequent transfer to the same hostname to succeed if the session ID cache is still fresh, skipping the verify status check. There is no information provided about the estimated number of potentially affected devices worldwide or real-world incidents where this issue was exploited. **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** curl versions prior to 8.1.0 **Description** An information disclosure issue exists when doing HTTP(S) transfers, where libcurl might erroneously use the read callback (`CURLOPT READFUNCTION`) to ask for data to send, even when the `CURLOPT POSTFIELDS` option has been set. This occurs if the same handle previously was used to issue a `PUT` request which used that callback. The flaw may cause the application to misbehave, sending off the wrong data or using memory after free in the second transfer. The problem exists in the logic for a reused handle when it is changed from a `PUT` to a `POST`. **Recommendations** For versions prior to 8.1.0, update to version 8.1.0 or later to resolve the issue. As a temporary workaround, consider avoiding the reuse of handles for `PUT` and `POST` requests, or disabling the `CURLOPT READFUNCTION` callback when switching from `PUT` to `POST` to minimize the risk of exploitation.

**Name of the Vulnerable Software and Affected Versions** curl versions prior to 7.87.0 MySQL Server versions 5.7.41 and earlier, 8.0.32 and earlier **Description** A vulnerability exists in the HSTS check of curl that could be bypassed to trick it into keeping using HTTP. The HSTS mechanism could be bypassed if the host name in the given URL first uses IDN characters that get replaced to ASCII counterparts as part of the IDN conversion. This could allow a remote attacker to gain unauthorized access to protected information. The issue is related to the storage of IDN encoded information but looking for it IDN decoded, leading to a clear text transfer in subsequent requests. **Recommendations** For curl versions prior to 7.87.0, update to version 7.87.0 or later to resolve the issue. For MySQL Server versions 5.7.41 and earlier, 8.0.32 and earlier, update to a version that includes the fix for this vulnerability. As a temporary workaround, consider disabling the HSTS support in curl until a patch is available. Restrict access to the vulnerable curl functionality to minimize the risk of exploitation.

**Name of the Vulnerable Software and Affected Versions** curl versions prior to 7.86.0 **Description** The issue is related to an error in parsing the .netrc file for credentials, which can lead to a denial-of-service. If a malicious user can provide a custom .netrc file to an application or otherwise affect its contents, this flaw could be used to cause the application to crash or experience other unexpected behavior. The .netrc file can be crafted to contain a line with 4095 consecutive non-white space letters and no newline, causing the application to read past the end of the stack-based buffer and potentially write a zero byte beyond its boundary. **Recommendations** Update to curl version 7.86.0 or later to resolve the issue. As a temporary workaround, consider restricting access to custom .netrc files or validating their contents to prevent malicious input. Avoid using .netrc files with untrusted or unvalidated contents until the issue is resolved.