OpenSSL provider use-after-free
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 |
When performing transfers via libcurl’s multi interface, pooled TLS connections can outlive their originating easy handles. In OpenSSL 3 provider configurations, libcurl attaches an allocated library context to the easy handle's state and passes it to OpenSSL without acquiring an ownership reference; destroying the easy handle prematurely frees this context while the active connection retains a dangling pointer, leading to a heap-use-after-free upon subsequent I/O or post-handshake operations.
From the CVE record · curl
In OpenSSL 3 provider configurations, a pooled TLS connection used by libcurl’s multi interface can retain a pointer to a library context freed when its originating easy handle is destroyed. Subsequent I/O or post-handshake operations can cause a heap-use-after-free; the input does not establish how an attacker could trigger it or whether authentication or user interaction is required.
Engineers using curl’s libcurl multi interface with OpenSSL 3 provider configurations should check their deployments; affected versions are not specified.