CVE-2020-1971: The X.509 GeneralName type is a generic type for representing different types of names.

Medium CVSS 5.9

CVE id
CVE-2020-1971
Published
Last modified

Affected packages

PackageAffected versionsFixed in
MySQL
Runtimes and servers
<= 8.0.22
<= 5.7.32
>= 8.0.15, <= 8.0.22
after 5.7.32, 8.0.22
Node.js
Runtimes and servers
>= 10.0.0, <= 10.12.0
>= 10.13.0, < 10.23.1
>= 12.0.0, <= 12.12.0
>= 12.13.0, < 12.20.1
>= 14.0.0, <= 14.14.0
>= 14.15.0, < 14.15.4
>= 15.0.0, < 15.5.0
10.23.1, 12.20.1, 14.15.4, 15.5.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.32, 8.0.22).

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.23.1, 12.20.1, 14.15.4, 15.5.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 X.509 GeneralName type is a generic type for representing different types of names. One of those name types is known as EDIPartyName. OpenSSL provides a function GENERALNAMEcmp which compares different instances of a GENERALNAME to see if they are equal or not. This function behaves incorrectly when both GENERALNAMEs contain an EDIPARTYNAME. A NULL pointer dereference and a crash may occur leading to a possible denial of service attack. OpenSSL itself uses the GENERALNAMEcmp function for two purposes: 1) Comparing CRL distribution point names between an available CRL and a CRL distribution point embedded in an X509 certificate 2) When verifying that a timestamp response token signer matches the timestamp authority name (exposed via the API functions TSRESPverifyresponse and TSRESPverifytoken) If an attacker can control both items being compared then that attacker could trigger a crash. For example if the attacker can trick a client or server into checking a malicious certificate against a malicious CRL then this may occur. Note that some applications automatically download CRLs based on a URL embedded in a certificate. This checking happens prior to the signatures on the certificate and CRL being verified. OpenSSL's sserver, sclient and verify tools have support for the "-crl_download" option which implements automatic CRL downloading and this attack has been demonstrated to work against those tools. Note that an unrelated bug means that affected versions of OpenSSL cannot parse or construct correct encodings of EDIPARTYNAME. However it is possible to construct a malformed EDIPARTYNAME that OpenSSL's parser will accept and hence trigger this attack. All OpenSSL 1.1.1 and 1.0.2 versions are affected by this issue. Other OpenSSL releases are out of support and have not been checked. Fixed in OpenSSL 1.1.1i (Affected 1.1.1-1.1.1h). Fixed in OpenSSL 1.0.2x (Affected 1.0.2-1.0.2w).

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.