Homepage

Improper Certificate Validation The advisory has been revoked - it doesn't affect any version of package mysql-server  (opens in a new tab)

Threat Intelligence

EPSS
15.14% (97th 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-RHEL8-MYSQLSERVER-1765606
  • published21 Oct 2021
  • disclosed21 Jul 2021
Report a new vulnerability Found a mistake?

Introduced: 21 Jul 2021

CVE-2021-22926  (opens in a new tab)
CWE-295  (opens in a new tab)

Amendment

The Red Hat security team deemed this advisory irrelevant for RHEL:8.

NVD Description

Note: Versions mentioned in the description apply only to the upstream mysql-server package and not the mysql-server package as distributed by RHEL.

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