QID 355747

Libcurl offers a feature to verify an ssh server's public key using a sha 256 hash.
When this check fails, libcurl would free the memory for the fingerprint before it returns an error message containing the (now freed) hash. this flaw risks inserting sensitive heap-based data into the error message that might be shown to users or otherwise get leaked and revealed. (
( CVE-2023-28319) curl supports matching of wildcard patterns when listed as "subject alternative name" in tls server certificates.
Curl can be built to use its own name matching function for tls rather than one provided by a tls library.
This private wildcard matching function would match idn (international domain name) hosts incorrectly and could as a result accept patterns that otherwise should mismatch. idn hostnames are converted to puny code before used for certificate checks.
Puny coded names always start with xn-- and should not be allowed to pattern match, but the wildcard check in curl could still check for x*, which would match even though the idn name most likely contained nothing even resembling an x. (cve-2023-28321) when doing http(s) transfers, libcurl might erroneously use the read callback (curlopt_readfunction) to ask for data to send, even when the curlopt_postfields option has been set, if the same handle previously was used to issue a put request which used that callback. this flaw may surprise the application and cause it to misbehave and either send off the wrong data or use memory after free or similar in the second transfer. the problem exists in the logic for a reused handle when it is (expected to be) changed from a put to a post. (
( CVE-2023-28322)

Successful exploitation of this vulnerability could lead to a securitybreach or could affect integrity, availability, and confidentiality.