CVE-2023-23919: A cryptographic vulnerability exists in Node.js <19.2.0, <18.14.1, <16.19.1, <14.21.3 that in some cases did does not clear the OpenSSL error stack after operations that may set it.

High CVSS 7.5

CVE id
CVE-2023-23919
Published
Last modified

Affected packages

PackageAffected versionsFixed in
Node.js
Runtimes and servers
>= 14.0.0, <= 14.14.0
>= 14.0.0, < 14.21.3
>= 16.0.0, <= 16.12.0
>= 16.0.0, < 16.19.1
>= 18.0.0, <= 18.11.0
>= 18.0.0, < 18.14.1
>= 19.0.0, < 19.2.0
14.21.3, 16.19.1, 18.14.1, 19.2.0

How to fix it

Upgrade Node.js to the fixed release of the line you run: 14.21.3, 16.19.1, 18.14.1, 19.2.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

A cryptographic vulnerability exists in Node.js <19.2.0, <18.14.1, <16.19.1, <14.21.3 that in some cases did does not clear the OpenSSL error stack after operations that may set it. This may lead to false positive errors during subsequent cryptographic operations that happen to be on the same thread. This in turn could be used to cause a denial of service.

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.