Homepage
About Snyk

Improper Certificate Validation Affecting curl package, versions <7.67.0-r5

0.0
high

Snyk CVSS

    Attack Complexity Low
    Availability High

    Threat Intelligence

    EPSS 0.88% (83rd percentile)
Expand this section
NVD
7.5 high
Expand this section
Red Hat
7.5 high

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-ALPINE311-CURL-1533446
  • published 26 Jul 2021
  • disclosed 5 Aug 2021
Report a new vulnerability Found a mistake?

Introduced: 26 Jul 2021

CVE-2021-22926 Open this link in a new tab
CWE-295 Open this link in a new tab

How to fix?

Upgrade Alpine:3.11 curl to version 7.67.0-r5 or higher.

NVD Description

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

libcurl-using applications can ask for a specific client certificate to be used in a transfer. This is done with the CURLOPT_SSLCERT option (--cert with the command line tool).When libcurl is built to use the macOS native TLS library Secure Transport, an application can ask for the client certificate by name or with a file name - using the same option. If the name exists as a file, it will be used instead of by name.If the appliction runs with a current working directory that is writable by other users (like /tmp), a malicious user can create a file name with the same name as the app wants to use by name, and thereby trick the application to use the file based cert instead of the one referred to by name making libcurl send the wrong client certificate in the TLS connection handshake.

References