No QUIC certificate pinning with GnuTLS
No exploitation in the wild has been reported. EPSS puts the chance of exploitation in the next 30 days at 0%. Fixed in 3d91ca8cdb3b434226e743946d428b4dd3acf2c9, 8.16.1, 8.18.0 and 1 more.
When using `CURLOPT_PINNEDPUBLICKEY` option with libcurl or `--pinnedpubkey` with the curl tool, curl should check the public key of the server certificate to verify the peer. This check was skipped in a certain condition that would then make curl allow the connection without performing the proper check, thus not noticing a possible impostor. To skip this check, the connection had to be done with QUIC with ngtcp2 built to use GnuTLS and the user had to explicitly disable the standard certificate verification.
Affected
Vendors, products and packages with version ranges
| Vendor | Product | Versions | Fixed |
|---|---|---|---|
| curl | =8.10.0, =8.10.1, =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.8.0, =8.9.0, =8.9.1, >=3210101088dfa3d6a125d213226b092f2f866722 <3d91ca8cdb3b434226e743946d428b4dd3acf2c9, >=8.15.0 <8.16.1, >=8.17.0 <8.18.0, >=8.8.0 <8.14.2 | 3d91ca8cdb3b434226e743946d428b4dd3acf2c9, 8.16.1, 8.18.0, 8.14.2 |
Timeline
Every event on this vulnerability
Embed
A live severity badge for an advisory, README or ticket