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-reqd on the command line orCURLOPT_USE_SSL set to CURLUSESSL_CONTROL or CURLUSESSL_ALL withlibcurl). This requirement could be bypassed if the server would return a properly crafted but perfectly legitimate response.This flaw would then make curl silently continue its operations withoutTLS contrary to the instructions and expectations, exposing possibly sensitive data in clear text over the network.
The product does not implement a required step in a cryptographic algorithm, resulting in weaker encryption than advertised by the algorithm.
| Name | Vendor | Start Version | End Version |
|---|---|---|---|
| Curl | Haxx | 7.20.0 (including) | 7.79.0 (excluding) |
| Curl | Ubuntu | bionic | * |
| Curl | Ubuntu | devel | * |
| Curl | Ubuntu | esm-infra/xenial | * |
| Curl | Ubuntu | focal | * |
| Curl | Ubuntu | hirsute | * |
| Curl | Ubuntu | impish | * |
| Curl | Ubuntu | jammy | * |
| Curl | Ubuntu | trusty | * |
| Curl | Ubuntu | trusty/esm | * |
| Curl | Ubuntu | xenial | * |
| .NET Core on Red Hat Enterprise Linux | RedHat | rh-dotnet31-curl-0:7.61.1-22.el7_9 | * |
| Red Hat Enterprise Linux 8 | RedHat | curl-0:7.61.1-18.el8_4.2 | * |
| Red Hat Enterprise Linux 8.2 Extended Update Support | RedHat | curl-0:7.61.1-12.el8_2.4 | * |