native CA store conn reuse
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.21.08.20.08.19.08.18.08.17.08.16.0| No fix yet |
A flaw in libcurl makes it wrongly reuse an existing HTTPS connection setup for a given hostname even when using a different Native CA Store setting (`CURLSSLOPT_NATIVE_CA`) than when the connection was created.
From the CVE record · curl
libcurl can reuse an existing HTTPS connection to a hostname even when a later request uses a different Native CA Store setting (`CURLSSLOPT_NATIVE_CA`). The later request may therefore use a connection established under the earlier setting. The input does not specify an attacker action, authentication requirement, or user interaction.
Engineers running curl or software that uses libcurl should check whether they use different Native CA Store settings for the same hostname; affected versions are not specified.