Описание
libcurl supports pinning of the server certificate public key for HTTPS transfers. Due to an omission, this check is not performed when connecting with QUIC for HTTP/3, when the TLS backend is wolfSSL. Documentation says the option works with wolfSSL, failing to specify that it does not for QUIC and HTTP/3. Since pinning makes the transfer succeed if the pin is fine, users could unwittingly connect to an impostor server without noticing.
Релиз | Статус | Примечание |
---|---|---|
devel | not-affected | code not compiled |
esm-infra-legacy/trusty | not-affected | code not present |
esm-infra/bionic | not-affected | code not present |
esm-infra/focal | not-affected | code not present |
esm-infra/xenial | not-affected | code not present |
focal | not-affected | code not present |
jammy | not-affected | code not present |
noble | not-affected | code not present |
oracular | not-affected | code not compiled |
plucky | not-affected | code not compiled |
Показывать по
EPSS
4.8 Medium
CVSS3
Связанные уязвимости
libcurl supports *pinning* of the server certificate public key for HTTPS transfers. Due to an omission, this check is not performed when connecting with QUIC for HTTP/3, when the TLS backend is wolfSSL. Documentation says the option works with wolfSSL, failing to specify that it does not for QUIC and HTTP/3. Since pinning makes the transfer succeed if the pin is fine, users could unwittingly connect to an impostor server without noticing.
libcurl supports *pinning* of the server certificate public key for HTTPS transfers. Due to an omission, this check is not performed when connecting with QUIC for HTTP/3, when the TLS backend is wolfSSL. Documentation says the option works with wolfSSL, failing to specify that it does not for QUIC and HTTP/3. Since pinning makes the transfer succeed if the pin is fine, users could unwittingly connect to an impostor server without noticing.
libcurl supports *pinning* of the server certificate public key for HT ...
libcurl supports *pinning* of the server certificate public key for HTTPS transfers. Due to an omission, this check is not performed when connecting with QUIC for HTTP/3, when the TLS backend is wolfSSL. Documentation says the option works with wolfSSL, failing to specify that it does not for QUIC and HTTP/3. Since pinning makes the transfer succeed if the pin is fine, users could unwittingly connect to an impostor server without noticing.
EPSS
4.8 Medium
CVSS3