Native CA trust persist
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 |
|
| No fix yet |
libcurl keeps previously used connections in a connection pool for subsequent transfers to reuse if one of them matches the setup.
An easy handle that first uses default native CA trust can continue trusting the native platform store after the application switches that same handle to custom CA material for a later transfer.
From the CVE record · curl
When an application reuses a libcurl easy handle that first used the default native CA trust, later transfers may continue to trust the native platform store even after the application switches the handle to custom CA material. This could let a network attacker present a certificate trusted by the native store but not by the custom CA material. The issue requires that sequence of handle use; the input does not specify authentication or user-interaction requirements.
Engineers using curl or libcurl should check applications that reuse easy handles and switch them from native CA trust to custom CA material; affected versions were not provided.