CVE-2021-3450: The X509_V_FLAG_X509_STRICT flag enables additional security checks of the certificates present in a certificate chain.

High CVSS 7.4

CVE id
CVE-2021-3450
Published
Last modified

Affected packages

PackageAffected versionsFixed in
MySQL
Runtimes and servers
<= 5.7.33
>= 8.0.15, <= 8.0.23
after 5.7.33, 8.0.23
Node.js
Runtimes and servers
>= 10.0.0, < 10.24.1
>= 12.0.0, < 12.22.1
>= 14.0.0, < 14.16.1
>= 15.0.0, < 15.14.0
10.24.1, 12.22.1, 14.16.1, 15.14.0

How to fix it

MySQL (Runtimes and servers)

Upgrade MySQL to a release newer than the last affected update of the line you run (5.7.33, 8.0.23).

mysqld --version
  • Install the patched MySQL release of your series (the mysql image tag or the MySQL packages) and restart the server.

Node.js (Runtimes and servers)

Upgrade Node.js to the fixed release of the line you run: 10.24.1, 12.22.1, 14.16.1, 15.14.0.

node --version
  • Install the patched Node.js release of your major line (nvm install, or the node image tag) everywhere the app runs and builds.

A free AIssue account reads the runtime versions your repositories pin (version files, Dockerfiles, build files) and tells you when one is affected.

Details

The X509VFLAGX509STRICT flag enables additional security checks of the certificates present in a certificate chain. It is not set by default. Starting from OpenSSL version 1.1.1h a check to disallow certificates in the chain that have explicitly encoded elliptic curve parameters was added as an additional strict check. An error in the implementation of this check meant that the result of a previous check to confirm that certificates in the chain are valid CA certificates was overwritten. This effectively bypasses the check that non-CA certificates must not be able to issue other certificates. If a "purpose" has been configured then there is a subsequent opportunity for checks that the certificate is a valid CA. All of the named "purpose" values implemented in libcrypto perform this check. Therefore, where a purpose is set the certificate chain will still be rejected even when the strict flag has been used. A purpose is set by default in libssl client and server certificate verification routines, but it can be overridden or removed by an application. In order to be affected, an application must explicitly set the X509VFLAGX509STRICT verification flag and either not set a purpose for the certificate verification or, in the case of TLS client or server applications, override the default purpose. OpenSSL versions 1.1.1h and newer are affected by this issue. Users of these versions should upgrade to OpenSSL 1.1.1k. OpenSSL 1.0.2 is not impacted by this issue. Fixed in OpenSSL 1.1.1k (Affected 1.1.1h-1.1.1j).

References

Am I affected?

Upload or paste your lockfile. We check every package version in it against OSV.dev, this advisory included, and email you the vulnerable ones with the version that fixes them. Free, and no account needed.

or paste its content

Needed when you paste. package.json and pyproject.toml only have version ranges: use the lockfile next to them.

Only package names and versions are checked; the file itself is not kept. We use your email to send this report and nothing else unless you tick the box above. Privacy policy.

About this data

Source: National Vulnerability Database (NVD) (public domain). Severity comes from the advisory's own rating when it has one, else from its CVSS score.