OpenSSL partial chain store policy bypass
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.16.08.15.08.14.18.14.08.13.0| No fix yet |
When doing TLS related transfers with reused easy or multi handles and altering the `CURLSSLOPT_NO_PARTIALCHAIN` option, libcurl could accidentally reuse a CA store cached in memory for which the partial chain option was reversed. Contrary to the user's wishes and expectations. This could make libcurl find and accept a trust chain that it otherwise would not.
From the CVE record · curl
During TLS transfers, libcurl can reuse a cached CA store with the opposite `CURLSSLOPT_NO_PARTIALCHAIN` setting when easy or multi handles are reused and that option is changed. This can cause libcurl to accept a trust chain it otherwise would not, potentially letting an attacker with a certificate that relies on that chain pass TLS validation. The input does not specify authentication or user-interaction requirements.
Engineers using curl or libcurl for TLS transfers with reused easy or multi handles should check whether their installed versions are affected; affected versions were not provided.