A cleartext transmission of sensitive information vulnerability exists in curl <v7.88.0 that could cause HSTS functionality to behave incorrectly when multiple URLs are requested in parallel. Using its HSTS support, curl can be instructed to use HTTPS instead of using an insecure clear-text HTTP step even when HTTP is provided in the URL. This HSTS mechanism would however surprisingly fail when multiple transfers are done in parallel as the HSTS cache file gets overwritten by the most recentlycompleted transfer. A later HTTP-only transfer to the earlier host name would then not get upgraded properly to HSTS.
The product transmits sensitive or security-critical data in cleartext in a communication channel that can be sniffed by unauthorized actors.
| Name | Vendor | Start Version | End Version |
|---|---|---|---|
| Curl | Haxx | 7.77.0 (including) | 7.88.0 (excluding) |
| JBCS httpd 2.4.51.sp2 | RedHat | jbcs-httpd24-curl | * |
| JBoss Core Services for RHEL 8 | RedHat | jbcs-httpd24-curl-0:8.0.1-1.el8jbcs | * |
| JBoss Core Services on RHEL 7 | RedHat | jbcs-httpd24-curl-0:8.0.1-1.el7jbcs | * |
| Curl | Ubuntu | devel | * |
| Curl | Ubuntu | jammy | * |
| Curl | Ubuntu | kinetic | * |
| Curl | Ubuntu | lunar | * |
| Curl | Ubuntu | trusty | * |
| Curl | Ubuntu | upstream | * |
| Curl | Ubuntu | xenial | * |