CVE-2021-44531: High severity Nodejs Node.js vulnerability

Published Jan 10, 2022
·
Updated

A flaw was found in node.js where it accepted a certificate's Subject Alternative Names (SAN) entry, as opposed to what is specified by the HTTPS protocol. This flaw allows an active person-in-the-middle to forge a certificate and impersonate a trusted host.

Other sources

Accepting arbitrary Subject Alternative Name (SAN) types, unless a PKI is specifically defined to use a particular SAN type, can result in bypassing name-constrained intermediates. Node.js < 12.22.9, < 14.18.3, < 16.13.2, and < 17.3.1 was accepting URI SAN types, which PKIs are often not defined to use. Additionally, when a protocol allows URI SANs, Node.js did not match the URI correctly.Versions of Node.js with the fix for this disable the URI SAN type when checking a certificate against a hostname. This behavior can be reverted through the --security-revert command-line option.

Accepting arbitrary Subject Alternative Name (SAN) types, unless a PKI is specifically defined to use a particular SAN type, can result in bypassing name-constrained intermediates. Node.js was accepting URI SAN types, which PKIs are often not defined to use. Additionally, when a protocol allows URI SANs, Node.js did not match the URI correctly.

Versions of Node.js with the fix for this disable the URI SAN type when checking a certificate against a hostname.

Reference: https://nodejs.org/en/blog/vulnerability/jan-2022-security-releases/

Red Hat

Node.js could allow a remote attacker to bypass security restrictions, caused by the improper handling of URI Subject Alternative Name (SAN) types. An attacker could exploit this vulnerability to bypass name-constrained intermediates.

IBM

Affected Software

24 affected componentsFixes available
redhat/rh-nodejs12-nodejs<0:12.22.12-2.el7
0:12.22.12-2.el7
redhat/rh-nodejs14-nodejs<0:14.20.1-2.el7
0:14.20.1-2.el7
debian/nodejs<=10.24.0~dfsg-1~deb10u1, <=10.24.0~dfsg-1~deb10u3
12.22.12~dfsg-1~deb11u418.13.0+dfsg1-1
Nodejs Node.js<12.22.9
Nodejs Node.js>=14.0.0<14.18.3
Nodejs Node.js>=16.0.0<16.13.2
Nodejs Node.js>=17.0.0<17.3.1
Oracle GraalVM=20.3.5
Oracle GraalVM=21.3.1
Oracle GraalVM=22.0.0.2
Oracle MySQL Connectors<=8.0.28
Oracle MySQL Enterprise Monitor<=8.0.29
Oracle MySQL Server<=5.7.37
Oracle MySQL Server>=8.0.0<=8.0.28
Oracle MySQL Workbench<=8.0.28
Oracle PeopleSoft Enterprise PeopleTools=8.58
Oracle PeopleSoft Enterprise PeopleTools=8.59
Oracle MySQL Cluster<=8.0.29
redhat/node<12.22.9
12.22.9
redhat/node<14.18.3
14.18.3
redhat/node<16.13.2
16.13.2
redhat/node<17.3.1
17.3.1
IBM Cognos Analytics<=11.2.0 - 11.2.2
IBM Cognos Analytics<=11.1.0 - 11.1.6 FP4

Event History

Jan 10, 2022
CVE Published
12:00 AM
Jan 14, 2022
Data Sourced
via Red Hat·07:28 PM
DescriptionSeverityAffected Software
Feb 24, 2022
CVE Published
via MITRE·06:27 PM
Data Sourced
via MITRE·06:27 PM
DescriptionWeakness
Feb 23, 2026
Data Sourced
via IBM·11:32 PM
DescriptionAffected Software
Free Weekly Intel

Don't miss critical vulnerabilities

Join thousands of security professionals who receive our weekly digest of trending CVEs, zero-days, and exploited vulnerabilities.

No spam. Unsubscribe anytime.

Frequently Asked Questions

1

What is CVE-2021-44531?

CVE-2021-44531 is a vulnerability in Node.js that could allow a remote attacker to bypass security restrictions.

2

How does CVE-2021-44531 impact Node.js?

CVE-2021-44531 impacts Node.js versions < 12.22.9, < 14.18.3, < 16.13.2, and < 17.3.1 by accepting arbitrary Subject Alternative Name (SAN) types, potentially bypassing name-constrained intermediates.

3

What is the severity of CVE-2021-44531?

The severity of CVE-2021-44531 is high, with a severity value of 7.4.

4

How do I fix CVE-2021-44531 in Node.js?

To fix CVE-2021-44531 in Node.js, you should update to version 12.22.9 or later, 14.18.3 or later, 16.13.2 or later, or 17.3.1 or later.

5

Where can I find more information about CVE-2021-44531?

You can find more information about CVE-2021-44531 at the following references: [link1], [link2], [link3].

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