CVE-2023-23919: Node.js OpenSSL error handling issues in nodejs crypto library

Published Feb 16, 2023
·
Updated

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.

Other sources

In some cases Node.js 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.

— Red Hat

Node.js is vulnerable to a denial of service, caused by not clear the OpenSSL error stack after operations. By sending specially-crafted cryptographic operations, a remote attacker could exploit this vulnerability to cause a denial of service condition.

— IBM

Affected Software

17 affected componentsFixes available
redhat/nodejs<18-9020020230327152102.rhel9
18-9020020230327152102.rhel9
IBM Cognos Controller<=11.0.0 - 11.0.1
Nodejs Node.js>=14.0.0<=14.14.0
Nodejs Node.js>=14.0.0<14.21.3
Nodejs Node.js>=16.0.0<=16.12.0
Nodejs Node.js>=16.0.0<16.19.1
Nodejs Node.js>=18.0.0<=18.11.0
Nodejs Node.js>=18.0.0<18.14.1
Nodejs Node.js>=19.0.0<19.2.0
redhat/node.js<19.2.0
19.2.0
redhat/node.js<18.14.1
18.14.1
redhat/node.js<16.19.1
16.19.1
Node.js Node.js>=14.0.0<14.21.3, >=16.0.0<16.19.1, >=18.0.0<18.14.1, >=19.0.0<19.2.0
14.21.316.19.118.14.119.2.0
Node.js Node.js>=16.0.0<16.19.1
16.19.1
Node.js Node.js>=18.0.0<18.14.1
18.14.1
Node.js Node.js>=19.0.0<19.6.1
19.6.1
debian/nodejs
18.20.4+dfsg-1~deb12u218.20.4+dfsg-1~deb12u320.19.2+dfsg-1+deb13u220.19.2+dfsg-1+deb13u324.21.0+dfsg+~cs24.13.4-124.22.2+dfsg+~cs24.19.2-1

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Upgrade

    Upgrade redhat/nodejs to a version that resolves this vulnerability.

    Fixed in 18-9020020230327152102.rhel9
  2. Upgrade

    Upgrade redhat/Node.js to a version that resolves this vulnerability.

    Fixed in 19.2.0
  3. Upgrade

    Upgrade redhat/Node.js to a version that resolves this vulnerability.

    Fixed in 18.14.1
  4. Upgrade

    Upgrade redhat/Node.js to a version that resolves this vulnerability.

    Fixed in 16.19.1
  5. Upgrade

    Upgrade to a fixed release to a version that resolves this vulnerability.

    Fixed in 14.21.3Fixed in 16.19.1Fixed in 18.14.1Fixed in 19.2.0
  6. Upgrade

    Upgrade to a fixed release to a version that resolves this vulnerability.

    Fixed in 16.19.1
  7. Upgrade

    Upgrade to a fixed release to a version that resolves this vulnerability.

    Fixed in 18.14.1
  8. Upgrade

    Upgrade to a fixed release to a version that resolves this vulnerability.

    Fixed in 19.6.1
  9. Upgrade

    Upgrade debian/nodejs to a version that resolves this vulnerability.

    Fixed in 18.20.4+dfsg-1~deb12u2Fixed in 18.20.4+dfsg-1~deb12u3Fixed in 20.19.2+dfsg-1+deb13u2Fixed in 20.19.2+dfsg-1+deb13u3Fixed in 24.21.0+dfsg+~cs24.13.4-1Fixed in 24.22.2+dfsg+~cs24.19.2-1
  10. Upgrade

    Upgrade Node.js to a version that resolves this vulnerability.

    Fixed in 19.2.0
  11. Upgrade

    Upgrade Node.js to a version that resolves this vulnerability.

    Fixed in 18.14.1
  12. Upgrade

    Upgrade Node.js to a version that resolves this vulnerability.

    Fixed in 16.19.1
  13. Upgrade

    Upgrade Node.js to a version that resolves this vulnerability.

    Fixed in 14.21.3

Event History

Feb 16, 2023
CVE Published
12:00 AM
Data Sourced
via Node.js·09:00 PM
DescriptionSeverity
Data Sourced
via Node.js·10:16 PM
Affected Software
Feb 21, 2023
Data Sourced
via Red Hat·03:42 PM
DescriptionSeverityAffected Software
Feb 23, 2023
CVE Published
via MITRE·12:00 AM
Data Sourced
via MITRE·12:00 AM
DescriptionWeakness
Data Sourced
via OSV·12:00 AM
DescriptionSeverityWeakness
Data Sourced
via NVD·08:15 PM
RemedyDescriptionSeverityWeaknessAffected Software

Parent advisories

This vulnerability appears in the following advisories.

Frequently Asked Questions

1

What is CVE-2023-23919?

CVE-2023-23919 is a cryptographic vulnerability in Node.js versions <19.2.0, <18.14.1, <16.19.1, <14.21.3 that may lead to false positive errors during subsequent cryptographic operations.

2

How does CVE-2023-23919 affect Node.js?

CVE-2023-23919 affects Node.js versions <19.2.0, <18.14.1, <16.19.1, <14.21.3.

3

What is the severity of CVE-2023-23919?

CVE-2023-23919 has a severity rating of 7.5 (high).

4

Which versions of Node.js are affected by CVE-2023-23919?

Node.js versions <19.2.0, <18.14.1, <16.19.1, and <14.21.3 are affected by CVE-2023-23919.

5

How can I fix CVE-2023-23919?

To fix CVE-2023-23919, update Node.js to version 19.2.0 or later, version 18.14.1 or later, version 16.19.1 or later, or version 14.21.3 or later.

Company

Resources

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203