connection reuse ignores TLS requirement
curl
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| curl curl |
| No fix yet |
| curl curl |
| No fix yet |
| curl curl |
|
curl
| Product | Affected | Fixed in |
|---|---|---|
| curl curl |
| No fix yet |
| curl curl |
| No fix yet |
| curl curl |
|
8.18.08.17.08.16.08.15.08.14.1| No fix yet |
A vulnerability exists where a connection requiring TLS incorrectly reuses an existing unencrypted connection from the same connection pool. If an initial transfer is made in clear-text (via IMAP, SMTP, or POP3), a subsequent request to that same host bypasses the TLS requirement and instead transmit data unencrypted.
From the CVE record · curl
curl can incorrectly reuse an unencrypted connection for a request that requires TLS. If an initial IMAP, SMTP, or POP3 transfer uses cleartext and a subsequent request goes to the same host, the subsequent request can transmit data without encryption. The input does not specify authentication requirements or user interaction.
Engineers running curl should check their installations; affected versions were not specified.