wolfSSL CA-cache hit overrides callback
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 |
With the wolfSSL backend, when CA caching is enabled and an `CURLOPT_SSL_CTX_FUNCTION` callback replaces the trust store, libcurl can silently reinstall the cached store after the callback returns. A certificate trusted by the cached store but rejected by the callback-selected store is then incorrectly accepted.
From the CVE record · curl
With the wolfSSL backend, libcurl can reinstall a cached CA trust store after an CURLOPT_SSL_CTX_FUNCTION callback replaces it. When CA caching is enabled, this can cause libcurl to accept a certificate that the callback-selected store would reject during a network connection.
Engineers using curl or libcurl with the wolfSSL backend, CA caching, and an CURLOPT_SSL_CTX_FUNCTION callback that replaces the trust store should check their deployments; affected versions were not provided.