https://github.com/curl/curl
51 vulnérabilités publiées citent ce produit.
Tel que les CNA l’écrivent dans leurs fiches CVE (éditeur et produit) ; les versions sont les leurs.
| CVE | Versions vulnérables | Titre | Sévérité | Publiée | EPSS | Exploitation |
|---|---|---|---|---|---|---|
| CVE-2023-28322 | Fixed in 8.1.0 | An information disclosure vulnerability exists in curl <v8.1.0 when doing HTTP(S) transfers, libcurl might erroneously use the read callback | MEDIUM 5.3 | 2.2 % | ||
| CVE-2023-28321 | Fixed in 8.1.0 | An improper certificate validation vulnerability exists in curl <v8.1.0 in the way it supports matching of wildcard patterns when listed as | MEDIUM 5.9 | 1.8 % | ||
| CVE-2023-28320 | Fixed in 8.1.0 | A denial of service vulnerability exists in curl <v8.1.0 in the way libcurl provides several different backends for resolving host names, se | MEDIUM 5.9 | 2.7 % | ||
| CVE-2023-28319 | Fixed in 8.1.0 | A use after free vulnerability exists in curl <v8.1.0 in the way libcurl offers a feature to verify an SSH server's public key using a SHA 2 | HIGH 7.5 | 2.5 % | ||
| CVE-2023-27538 | Fixed in 8.0.0 | An authentication bypass vulnerability exists in libcurl prior to v8.0.0 where it reuses a previously established SSH connection despite the | HIGH 7.7 | 1.5 % | ||
| CVE-2023-27537 | Fixed in 8.0.0 | A double free vulnerability exists in libcurl <8.0.0 when sharing HSTS data between separate "handles". This sharing was introduced without | MEDIUM 5.9 | 1.9 % | ||
| CVE-2023-27536 | Fixed in 8.0.0 | An authentication bypass vulnerability exists libcurl <8.0.0 in the connection reuse feature which can reuse previously established connecti | MEDIUM 5.9 | 1.8 % | ||
| CVE-2023-27535 | Fixed in 8.0.0 | An authentication bypass vulnerability exists in libcurl <8.0.0 in the FTP connection reuse feature that can result in wrong credentials bei | MEDIUM 5.9 | 1.8 % | ||
| CVE-2023-27534 | Fixed in 8.0.0 | A path traversal vulnerability exists in curl <8.0.0 SFTP implementation causes the tilde (~) character to be wrongly replaced when used as | HIGH 8.8 | 2.4 % | ||
| CVE-2023-27533 | Fixed in 8.0.0 | A vulnerability in input validation exists in curl <8.0 during communication using the TELNET protocol may allow an attacker to pass on mali | CRITICAL 9.8 | 2.2 % | ||
| CVE-2023-23916 | Fixed in 7.88.0 | An allocation of resources without limits or throttling vulnerability exists in curl <v7.88.0 based on the "chained" HTTP compression algori | MEDIUM 6.5 | 1.7 % | ||
| CVE-2023-23915 | Fixed in 7.88.0 | A cleartext transmission of sensitive information vulnerability exists in curl <v7.88.0 that could cause HSTS functionality to behave incorr | MEDIUM 6.5 | 0.9 % | ||
| CVE-2023-23914 | Fixed in 7.88.0 | A cleartext transmission of sensitive information vulnerability exists in curl <v7.88.0 that could cause HSTS functionality fail when multip | CRITICAL 9.1 | 0.9 % | ||
| CVE-2022-43552 | Fixed in curl 7.87.0 | A use after free vulnerability exists in curl <7.87.0. Curl can be asked to *tunnel* virtually all protocols it supports through an HTTP pro | MEDIUM 5.9 | 2.7 % | ||
| CVE-2022-43551 | Fixed in curl 7.87.0 | A vulnerability exists in curl <7.87.0 HSTS check that could be bypassed to trick it to keep using HTTP. Using its HSTS support, curl can be | HIGH 7.5 | 17 % | ||
| CVE-2022-35260 | Fixed in 7.86.0 | curl can be told to parse a `.netrc` file for credentials. If that file endsin a line with 4095 consecutive non-white space letters and no n | MEDIUM 6.5 | 2.7 % | ||
| CVE-2022-32221 | Fixed in 7.86.0 | When doing HTTP(S) transfers, libcurl might erroneously use the read callback (`CURLOPT_READFUNCTION`) to ask for data to send, even when th | CRITICAL 9.8 | 5.1 % | ||
| CVE-2022-35252 | Fixed in curl 7.85.0 | When curl is used to retrieve and parse cookies from a HTTP(S) server, itaccepts cookies using control codes that when later are sent back t | LOW 3.7 | 3.8 % | ||
| CVE-2022-32208 | Fixed in 7.84.0 | When curl < 7.84.0 does FTP transfers secured by krb5, it handles message verification failures wrongly. This flaw makes it possible for a M | MEDIUM 5.9 | 8.4 % | ||
| CVE-2022-32207 | Fixed in 7.84.0 | When curl < 7.84.0 saves cookies, alt-svc and hsts data to local files, it makes the operation atomic by finalizing the operation with a ren | CRITICAL 9.8 | 12 % | ||
| CVE-2022-32206 | Fixed in 7.84.0 | curl < 7.84.0 supports "chained" HTTP compression algorithms, meaning that a serverresponse can be compressed multiple times and potentially | MEDIUM 6.5 | 36 % | ||
| CVE-2022-32205 | Fixed in 7.84.0 | A malicious server can serve excessive amounts of `Set-Cookie:` headers in a HTTP response to curl and curl < 7.84.0 stores all of them. A s | MEDIUM 4.3 | 31 % | ||
| CVE-2022-27778 | fixed in 7.83.1 | A use of incorrectly resolved name vulnerability fixed in 7.83.1 might remove the wrong file when `--no-clobber` is used together with `--re | HIGH 8.1 | 3.8 % | ||
| CVE-2022-30115 | Fixed in 7.83.1 | Using its HSTS support, curl can be instructed to use HTTPS directly insteadof using an insecure clear-text HTTP step even when HTTP is prov | MEDIUM 4.3 | 1.4 % | ||
| CVE-2022-27782 | Fixed in 7.83.1 | libcurl would reuse a previously created connection even when a TLS or SSHrelated option had been changed that should have prohibited reuse. | HIGH 7.5 | 3.1 % | ||
| CVE-2022-27781 | Fixed in 7.83.1 | libcurl provides the `CURLOPT_CERTINFO` option to allow applications torequest details to be returned about a server's certificate chain.Due | HIGH 7.5 | 2.9 % | ||
| CVE-2022-27780 | Fixed in 7.83.1 | The curl URL parser wrongly accepts percent-encoded URL separators like '/'when decoding the host name part of a URL, making it a *different | HIGH 7.5 | 2.5 % | ||
| CVE-2022-27779 | Fixed in 7.83.1 | libcurl wrongly allows cookies to be set for Top Level Domains (TLDs) if thehost name is provided with a trailing dot.curl can be told to re | MEDIUM 5.3 | 2.8 % | ||
| CVE-2022-27776 | fixed in curl 7.83.0 | A insufficiently protected credentials vulnerability in fixed in curl 7.83.0 might leak authentication or cookie header data on HTTP redirec | MEDIUM 6.5 | 4.1 % | ||
| CVE-2022-27775 | curl 7.65.0 to 7.82.0 are vulnerable | An information disclosure vulnerability exists in curl 7.65.0 to 7.82.0 are vulnerable that by using an IPv6 address that was in the connect | HIGH 7.5 | 3.3 % | ||
| CVE-2022-27774 | curl 4.9 to and include curl 7.82.0 are affected | An insufficiently protected credentials vulnerability exists in curl 4.9 to and include curl 7.82.0 are affected that could allow an attacke | MEDIUM 5.7 | 2.0 % | ||
| CVE-2022-22576 | Fixed in curl 7.83.0 | An improper authentication vulnerability exists in curl 7.33.0 to and including 7.82.0 which might allow reuse OAUTH2-authenticated connecti | HIGH 8.1 | 2.5 % | ||
| CVE-2021-22947 | curl 7.20.0 to and including 7.78.0 | When curl >= 7.20.0 and <= 7.78.0 connects to an IMAP or POP3 server to retrieve data using STARTTLS to upgrade to TLS security, the server | MEDIUM 5.9 | 3.0 % | ||
| CVE-2021-22946 | curl 7.20.0 to and including 7.78.0 | A user can tell curl >= 7.20.0 and <= 7.78.0 to require a successful upgrade to TLS when speaking to an IMAP, POP3 or FTP server (`--ssl-req | HIGH 7.5 | 4.5 % | ||
| CVE-2021-22945 | curl 7.73.0 to and including 7.78.0 | When sending data to an MQTT server, libcurl <= 7.73.0 and 7.78.0 could in some circumstances erroneously keep a pointer to an already freed | CRITICAL 9.1 | 6.7 % | ||
| CVE-2021-22924 | curl 7.10.4 to and include curl 7.77.0 | libcurl keeps previously used connections in a connection pool for subsequenttransfers to reuse, if one of them matches the setup.Due to err | LOW 3.7 | 6.3 % | ||
| CVE-2021-22926 | curll 7.33.0 to and include 7.77.0 | libcurl-using applications can ask for a specific client certificate to be used in a transfer. This is done with the `CURLOPT_SSLCERT` optio | HIGH 7.5 | 15 % | ||
| CVE-2021-22925 | curl 7.7 to and including 7.77.0 | curl supports the `-t` command line option, known as `CURLOPT_TELNETOPTIONS`in libcurl. This rarely used option is used to send variable=con | MEDIUM 5.3 | 5.4 % | ||
| CVE-2021-22923 | curl 7.27.0 to and including 7.77.0 | When curl is instructed to get content using the metalink feature, and a user name and password are used to download the metalink XML file, | MEDIUM 5.3 | 2.0 % | ||
| CVE-2021-22922 | curl 7.27.0 to and including 7.77.0 | When curl is instructed to download content using the metalink feature, thecontents is verified against a hash provided in the metalink XML | MEDIUM 6.5 | 4.3 % | ||
| CVE-2021-22901 | 7.75.0 through 7.76.1 | curl 7.75.0 through 7.76.1 suffers from a use-after-free vulnerability resulting in already freed memory being used when a TLS 1.3 session t | HIGH 8.1 | 64 % | ||
| CVE-2021-22897 | 7.61.0 through 7.76.1 | curl 7.61.0 through 7.76.1 suffers from exposure of data element to wrong session due to a mistake in the code for CURLOPT_SSL_CIPHER_LIST w | MEDIUM 5.3 | 4.3 % | ||
| CVE-2021-22898 | 7.7 through 7.76.1 | curl 7.7 through 7.76.1 suffers from an information disclosure when the `-t` command line option, known as `CURLOPT_TELNETOPTIONS` in libcur | LOW 3.1 | 4.5 % | ||
| CVE-2021-22890 | 7.63.0 to and including 7.75.0 | curl 7.63.0 to and including 7.75.0 includes vulnerability that allows a malicious HTTPS proxy to MITM a connection due to bad handling of T | MEDIUM 4.3 | 3.1 % | ||
| CVE-2021-22876 | 7.1.1 to and including 7.75.0 | curl 7.1.1 to and including 7.75.0 is vulnerable to an "Exposure of Private Personal Information to an Unauthorized Actor" by leaking creden | MEDIUM 5.3 | 5.3 % | ||
| CVE-2020-8177 | curl 7.20.0 to and including 7.70.0 | curl 7.20.0 through 7.70.0 is vulnerable to improper restriction of names for files and other resources that can lead too overwriting a loca | HIGH 7.8 | 1.3 % | ||
| CVE-2020-8169 | libcurl 7.62.0 to and including 7.70.0 | curl 7.62.0 through 7.70.0 is vulnerable to an information disclosure vulnerability that can lead to a partial password being leaked over th | HIGH 7.5 | 3.9 % | ||
| CVE-2020-8286 | 7.41.0 to and including 7.73.0 | curl 7.41.0 through 7.73.0 is vulnerable to an improper check for certificate revocation due to insufficient verification of the OCSP respon | HIGH 7.5 | 4.6 % | ||
| CVE-2020-8231 | libcurl 7.29.0 to and including 7.71.1 | Due to use of a dangling pointer, libcurl 7.29.0 through 7.71.1 can use the wrong connection when sending data. | HIGH 7.5 | 5.3 % | ||
| CVE-2020-8285 | libcurl 7.21.0 to and including 7.73.0 | curl 7.21.0 to and including 7.73.0 is vulnerable to uncontrolled recursion due to a stack overflow issue in FTP wildcard match parsing. | HIGH 7.5 | 9.8 % | ||
| CVE-2020-8284 | 7.73.0 and earlier | A malicious server can use the FTP PASV response to trick curl 7.73.0 and earlier into connecting back to a given IP address and port, and t | LOW 3.7 | 3.9 % |