QID 354255

a vulnerability was found in curl.
This security flaw allows reusing oauth2-authenticated connections without properly ensuring that the connection was authenticated with the same credentials set for this transfer.
This issue leads to an authentication bypass, either by mistake or by a malicious actor. (
( CVE-2022-22576) a vulnerability was found in curl.
This security flaw allows leaking credentials to other servers when it follows redirects from auth-protected http(s) urls to other protocols and port numbers. (
( CVE-2022-27774) a vulnerability was found in curl.
This security flaw allows leak authentication or cookie header data on http redirects to the same host but another port number.
Sending the same set of headers to a server on a different port number is a problem for applications that pass on custom `authorization:` or `cookie:`headers.
Those headers often contain privacy-sensitive information or data. (
( CVE-2022-27776) a vulnerability was found in curl.
This issue occurs due to an erroneous function.
A malicious server could make curl within network security services (nss) get stuck in a never-ending busy loop when trying to retrieve that information.
This flaw allows an infinite loop, affecting system availability. (
( CVE-2022-27781) a vulnerability was found in curl.
This issue occurs because curl can reuse a previously created connection even when a tls or ssh-related option is changed that should have prohibited reuse.
This flaw leads to an authentication bypass, either by mistake or by a malicious actor. (
( CVE-2022-27782) a vulnerability was found in curl.
This flaw leads to a denial of service, either by mistake or by a malicious actor. (

Note: The preceding description block is extracted directly from the security advisory. Using automation, we have attempted to clean and format it as much as possible without introducing additional issues.

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