OpenSSL pinning bypass
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 `CURLOPT_PINNEDPUBLICKEY` is configured alongside options that disable standard peer verification (`CURLOPT_SSL_VERIFYPEER = 0` and `CURLOPT_SSL_VERIFYHOST = 0`), libcurl fails to enforce public key pinning on connections established without a presented server certificate. Bypassing the pinning check under these disabled-verification conditions allows unauthenticated connections to succeed when they should be rejected.
From the CVE record · curl
libcurl fails to enforce public key pinning when `CURLOPT_PINNEDPUBLICKEY` is set, both standard peer-verification options are disabled, and the server presents no certificate. Under these conditions, a connection that should be rejected can succeed without server authentication. No user interaction is described.
Engineers using libcurl with public key pinning and both `CURLOPT_SSL_VERIFYPEER` and `CURLOPT_SSL_VERIFYHOST` set to 0 should check their configurations; affected versions were not specified.