HTTP/2 stream-dependency tree UAF
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 |
A use-after-free vulnerability exists in libcurl when an application configures an HTTP/2 stream-dependency tree via `CURLOPT_STREAM_DEPENDS` or `CURLOPT_STREAM_DEPENDS_E`, subsequently invokes `curl_easy_reset()`, and finally terminates the handle with `curl_easy_cleanup()`. During this final cleanup phase, libcurl attempts to access and modify an internal structure that was already freed during the reset operation.
From the CVE record · curl
libcurl has a use-after-free when an application configures an HTTP/2 stream-dependency tree, calls curl_easy_reset(), and then calls curl_easy_cleanup(). During cleanup, libcurl accesses and modifies a structure freed during the reset. The input does not identify an attacker route or specify network access, authentication, or user-interaction requirements.
Engineers running curl or applications that use libcurl should check their deployments; affected versions are not specified.