exposing HTTP/3 early data
No exploitation in the wild has been reported. EPSS puts the chance of exploitation in the next 30 days at 0%. Fixed in 8.14.2, 8.16.1, 8.20.1 and 1 more.
In this scenario, libcurl first uses a proper HTTP/3 server for the initial transfers, and when it makes a second transfer to the same site it has been replaced by the attacker's impostor machine - without a valid certificate. When libcurl returns to the hostname the second time with a cached SSL session (`CURLOPT_SSL_SESSIONID_CACHE` is not disabled) and early data enabled (the `CURLSSLOPT_EARLYDATA` bit is set in `CURLOPT_SSL_OPTIONS`), libcurl might send off the second request's bytes on that new connection *before* enforcing the certificate verification failure. Potentially leaking sensitive information.
Affected
Vendors, products and packages with version ranges
| Vendor | Product | Versions | Fixed |
|---|---|---|---|
| curl | =8.11.0, =8.11.1, =8.12.0, =8.12.1, =8.13.0, =8.14.0, =8.14.1, =8.15.0, =8.16.0, =8.17.0, =8.18.0, =8.19.0, =8.20.0, >=8.11.0 <8.14.2, >=8.15.0 <8.16.1, >=8.17.0 <8.20.1, >=962097b8dd44ed5b9e7984bc1cdffdbdd566857f <7b9613fa9b1a5e04301a3920eef58e8138dad05e | 8.14.2, 8.16.1, 8.20.1, 7b9613fa9b1a5e04301a3920eef58e8138dad05e |
Timeline
Every event on this vulnerability
Embed
A live severity badge for an advisory, README or ticket