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.
References
Configurations
No configuration.
History
30 May 2025, 17:15
Type | Values Removed | Values Added |
---|---|---|
CVSS |
v2 : v3 : |
v2 : unknown
v3 : 4.8 |
28 May 2025, 15:01
Type | Values Removed | Values Added |
---|---|---|
Summary |
|
28 May 2025, 08:15
Type | Values Removed | Values Added |
---|---|---|
References |
|
28 May 2025, 07:15
Type | Values Removed | Values Added |
---|---|---|
New CVE |
Information
Published : 2025-05-28 07:15
Updated : 2025-05-30 17:15
NVD link : CVE-2025-5025
Mitre link : CVE-2025-5025
CVE.ORG link : CVE-2025-5025
JSON object : View
Products Affected
No product.
CWE
No CWE.