Improper Certificate Validation Affecting libcurl package, versions <0:7.61.1-30.el8_8.3



    Attack Complexity High
    Integrity High

    Threat Intelligence

    EPSS 0.08% (32nd percentile)
Expand this section
5.9 medium
Expand this section
4.3 medium
Expand this section
Red Hat
5.9 medium

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 ID SNYK-ORACLE8-LIBCURL-5838150
  • published 3 Aug 2023
  • disclosed 26 May 2023

How to fix?

Upgrade Oracle:8 libcurl to version 0:7.61.1-30.el8_8.3 or higher.
This issue was patched in ELSA-2023-4523.

NVD Description

Note: Versions mentioned in the description apply only to the upstream libcurl package and not the libcurl package as distributed by Oracle. See How to fix? for Oracle:8 relevant fixed versions and status.

An improper certificate validation vulnerability exists in curl <v8.1.0 in the way it supports matching of wildcard patterns when listed as "Subject Alternative Name" in TLS server certificates. curl can be built to use its own name matching function for TLS rather than one provided by a TLS library. This private wildcard matching function would match IDN (International Domain Name) hosts incorrectly and could as a result accept patterns that otherwise should mismatch. IDN hostnames are converted to puny code before used for certificate checks. Puny coded names always start with xn-- and should not be allowed to pattern match, but the wildcard check in curl could still check for x*, which would match even though the IDN name most likely contained nothing even resembling an x.