Curl

Curl

26 Schwachstellen gefunden.

Hinweis: Diese Liste kann unvollständig sein. Daten werden ohne Gewähr im Ursprungsformat bereitgestellt.
Exploit
  • EPSS 0.07%
  • Veröffentlicht 07.06.2025 07:49:09
  • Zuletzt bearbeitet 30.07.2025 19:41:33

Due to a mistake in libcurl's WebSocket code, a malicious server can send a particularly crafted packet which makes libcurl get trapped in an endless busy-loop. There is no other way for the application to escape or exit this loop other than killing...

Exploit
  • EPSS 0.05%
  • Veröffentlicht 28.05.2025 06:29:51
  • Zuletzt bearbeitet 30.07.2025 19:41:37

libcurl supports *pinning* of the server certificate public key for HTTPS transfers. Due to an omission, this check is not performed when connecting with QUIC for HTTP/3, when the TLS backend is wolfSSL. Documentation says the option works with wolfS...

Exploit
  • EPSS 0.04%
  • Veröffentlicht 28.05.2025 06:29:34
  • Zuletzt bearbeitet 26.06.2025 15:08:21

libcurl accidentally skips the certificate verification for QUIC connections when connecting to a host specified as an IP address in the URL. Therefore, it does not detect impostors or man-in-the-middle attacks.

Exploit
  • EPSS 2.08%
  • Veröffentlicht 05.02.2025 10:15:22
  • Zuletzt bearbeitet 27.06.2025 19:24:08

When libcurl is asked to perform automatic gzip decompression of content-encoded HTTP responses with the `CURLOPT_ACCEPT_ENCODING` option, **using zlib 1.2.0.3 or older**, an attacker-controlled integer overflow would make libcurl perform a buffer ov...

Exploit
  • EPSS 2.81%
  • Veröffentlicht 05.02.2025 10:15:22
  • Zuletzt bearbeitet 30.07.2025 19:41:22

libcurl would wrongly close the same eventfd file descriptor twice when taking down a connection channel after having completed a threaded name resolve.

Exploit
  • EPSS 0.22%
  • Veröffentlicht 05.02.2025 10:15:22
  • Zuletzt bearbeitet 30.07.2025 19:41:45

When asked to use a `.netrc` file for credentials **and** to follow HTTP redirects, curl could leak the password used for the first host to the followed-to host under certain circumstances. This flaw only manifests itself if the netrc file has a `de...

Exploit
  • EPSS 0.79%
  • Veröffentlicht 11.12.2024 08:15:05
  • Zuletzt bearbeitet 03.11.2025 21:16:04

When asked to both use a `.netrc` file for credentials and to follow HTTP redirects, curl could leak the password used for the first host to the followed-to host under certain circumstances. This flaw only manifests itself if the netrc file has an e...

Exploit
  • EPSS 0.41%
  • Veröffentlicht 11.09.2024 10:15:02
  • Zuletzt bearbeitet 30.07.2025 19:42:16

When curl is told to use the Certificate Status Request TLS extension, often referred to as OCSP stapling, to verify that the server certificate is valid, it might fail to detect some OCSP problems and instead wrongly consider the response as fine. ...

Exploit
  • EPSS 0.22%
  • Veröffentlicht 27.03.2024 08:15:41
  • Zuletzt bearbeitet 30.07.2025 19:42:21

libcurl did not check the server certificate of TLS connections done to a host specified as an IP address, when built to use mbedTLS. libcurl would wrongly avoid using the set hostname function when the specified hostname was given as an IP address,...

Exploit
  • EPSS 2.23%
  • Veröffentlicht 27.03.2024 08:15:41
  • Zuletzt bearbeitet 30.07.2025 19:42:27

When an application tells libcurl it wants to allow HTTP/2 server push, and the amount of received headers for the push surpasses the maximum allowed limit (1000), libcurl aborts the server push. When aborting, libcurl inadvertently does not free all...