No QUIC certificate pinning with GnuTLS
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.16.08.15.08.14.18.14.08.13.0| No fix yet |
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.
From the CVE record · curl
curl and libcurl can skip the pinned public key check on a QUIC connection when ngtcp2 is built with GnuTLS. A network attacker could pose as the server if the user has enabled public key pinning and explicitly disabled standard certificate verification.
Teams using curl or libcurl with QUIC, ngtcp2 built with GnuTLS, and public key pinning should check their installations; affected versions were not provided.