incomplete mTLS config matching in 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.19.08.18.08.17.08.16.08.15.0| No fix yet |
libcurl would reuse a previously created connection even when some mTLS config related option had been changed that should have prohibited reuse.
libcurl keeps previously used connections in a connection pool for subsequent transfers to reuse if one of them matches the setup. However, some TLS settings related to client certificates were left out from the configuration match checks, making them match too easily. In particular options related to the private key.
From the CVE record · curl
libcurl can reuse a pooled connection after a client-certificate TLS setting has changed, because its connection-matching checks omit some private-key-related options. This can cause a subsequent transfer to use a connection that should not have been reused; the input does not specify an attacker action or authentication requirement.
Engineers running curl or using libcurl should check affected versions in the vendor advisory; no version range was provided.