Improper Certificate Validation Affecting libcurl4-32bit package, versions <8.14.1-150600.4.28.1


Severity

Recommended
0.0
medium
0
10

Based on SUSE Linux Enterprise Server security rating.

Threat Intelligence

EPSS
0.01% (2nd percentile)

Do your applications use this vulnerable package?

In a few clicks we can analyze your entire application and see what components are vulnerable in your application, and suggest you quick fixes.

Test your applications
  • Snyk IDSNYK-SLES156-LIBCURL432BIT-12657480
  • published13 Sept 2025
  • disclosed12 Sept 2025

Introduced: 12 Sep 2025

CVE-2025-5025  (opens in a new tab)
CWE-295  (opens in a new tab)

How to fix?

Upgrade SLES:15.6 libcurl4-32bit to version 8.14.1-150600.4.28.1 or higher.

NVD Description

Note: Versions mentioned in the description apply only to the upstream libcurl4-32bit package and not the libcurl4-32bit package as distributed by SLES. See How to fix? for SLES:15.6 relevant fixed versions and status.

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.

CVSS Base Scores

version 3.1