CVE-2021-22939: Incomplete validation of rejectUnauthorized parameter

Published Aug 11, 2021
·
Updated

A flaw was found in Node.js. If the Node.js HTTPS API is used incorrectly and "undefined" is passed for the "rejectUnauthorized" parameter, no error is returned, and the connections to servers with an expired certificate are accepted. The highest threat from this vulnerability is to integrity.

Other sources

If the Node.js https API was used incorrectly and "undefined" was in passed for the "rejectUnauthorized" parameter, no error was returned and connections to servers with an expired certificate would have been accepted.

Node.js could allow a remote attacker to bypass security restrictions. If the https API was used incorrectly and "undefined" was in passed for the "rejectUnauthorized" parameter, an attacker could exploit this vulnerability to connect to servers using an expired certificate.

— IBM

Affected Software

49 affected componentsFixes available
redhat/rh-nodejs14-nodejs<0:14.17.5-1.el7
0:14.17.5-1.el7
redhat/rh-nodejs12-nodejs<0:12.22.5-1.el7
0:12.22.5-1.el7
redhat/rh-nodejs12-nodejs-nodemon<0:2.0.3-5.el7
0:2.0.3-5.el7
redhat/nodejs<12.22.5
12.22.5
redhat/nodejs<14.17.5
14.17.5
redhat/nodejs<16.6.2
16.6.2
IBM Cognos Controller<=11.0.0 - 11.0.1
Nodejs Node.js>=12.0.0<12.22.5
Nodejs Node.js>=14.0.0<14.17.5
Nodejs Node.js>=16.0.0<16.6.2
Oracle GraalVM=20.3.3
Oracle GraalVM=21.2.0
Oracle JD Edwards EnterpriseOne Tools<=9.2.6.1
Oracle MySQL Cluster<=8.0.26
Oracle PeopleSoft Enterprise PeopleTools=8.57
Oracle PeopleSoft Enterprise PeopleTools=8.58
Oracle PeopleSoft Enterprise PeopleTools=8.59
NetApp Nextgen Api
Siemens Sinec Infrastructure Network Services<1.0.1.1
Debian Debian Linux=10.0
Node.js Node.js>=12.0.0<12.22.5, >=14.0.0<14.17.5, >=16.0.0<16.6.2
12.22.514.17.516.6.2
Node.js Node.js>=12.0.0<12.22.5
12.22.5
Node.js Node.js>=14.0.0<14.17.5
14.17.5
Node.js Node.js>=16.0.0<16.6.2
16.6.2
alpine/nodejs<12.22.5-r0
12.22.5-r0
alpine/nodejs<12.22.5-r0
12.22.5-r0
alpine/nodejs<14.17.5-r0
14.17.5-r0
alpine/nodejs<14.17.5-r0
14.17.5-r0
alpine/nodejs<14.17.5-r0
14.17.5-r0
alpine/nodejs<14.17.5-r0
14.17.5-r0
alpine/nodejs<14.17.5-r0
14.17.5-r0
alpine/nodejs<14.17.5-r0
14.17.5-r0
alpine/nodejs<14.17.5-r0
14.17.5-r0
alpine/nodejs<14.17.5-r0
14.17.5-r0
alpine/nodejs<14.17.5-r0
14.17.5-r0
alpine/nodejs<14.17.5-r0
14.17.5-r0
alpine/nodejs<14.17.5-r0
14.17.5-r0
alpine/nodejs<14.17.5-r0
14.17.5-r0
alpine/nodejs-current<16.11.1-r0
16.11.1-r0
alpine/nodejs-current<16.6.2-r0
16.6.2-r0
alpine/nodejs-current<16.6.2-r0
16.6.2-r0
alpine/nodejs-current<16.6.2-r0
16.6.2-r0
alpine/nodejs-current<16.6.2-r0
16.6.2-r0
alpine/nodejs-current<16.6.2-r0
16.6.2-r0
alpine/nodejs-current<16.6.2-r0
16.6.2-r0
alpine/nodejs-current<16.6.2-r0
16.6.2-r0
alpine/nodejs-current<16.6.2-r0
16.6.2-r0
alpine/nodejs-current<16.6.2-r0
16.6.2-r0
alpine/nodejs-current<16.6.2-r0
16.6.2-r0

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Upgrade

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

    Fixed in 0:14.17.5-1.el7
  2. Upgrade

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

    Fixed in 0:12.22.5-1.el7
  3. Upgrade

    Upgrade redhat/rh-nodejs12-nodejs-nodemon to a version that resolves this vulnerability.

    Fixed in 0:2.0.3-5.el7
  4. Upgrade

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

    Fixed in 12.22.5
  5. Upgrade

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

    Fixed in 14.17.5
  6. Upgrade

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

    Fixed in 16.6.2
  7. Upgrade

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

    Fixed in 12.22.5Fixed in 14.17.5Fixed in 16.6.2
  8. Upgrade

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

    Fixed in 12.22.5
  9. Upgrade

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

    Fixed in 14.17.5
  10. Upgrade

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

    Fixed in 16.6.2
  11. Upgrade

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

    Fixed in 12.22.5-r0
  12. Upgrade

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

    Fixed in 14.17.5-r0
  13. Upgrade

    Upgrade alpine/nodejs-current to a version that resolves this vulnerability.

    Fixed in 16.11.1-r0
  14. Upgrade

    Upgrade alpine/nodejs-current to a version that resolves this vulnerability.

    Fixed in 16.6.2-r0

Event History

Aug 11, 2021
CVE Published
12:00 AM
Data Sourced
via Node.js·04:00 PM
DescriptionSeverity
Data Sourced
via Node.js·04:41 PM
Affected Software
Aug 16, 2021
CVE Published
via MITRE·12:00 AM
Data Sourced
via MITRE·12:00 AM
DescriptionWeakness
Data Sourced
via NVD·07:15 PM
RemedyDescriptionSeverityWeaknessAffected Software
Data Sourced
via OSV·07:15 PM
DescriptionSeverityAffected Software

Parent advisories

This vulnerability appears in the following advisories.

Frequently Asked Questions

1

What is CVE-2021-22939?

CVE-2021-22939 is a vulnerability in Node.js where if the HTTPS API is used incorrectly and "undefined" is passed for the "rejectUnauthorized" parameter, connections to servers with an expired certificate are accepted.

2

What is the severity of CVE-2021-22939?

The severity of CVE-2021-22939 is low with a CVSS score of 3.7.

3

How does CVE-2021-22939 affect Node.js?

CVE-2021-22939 allows connections to servers with an expired certificate to be accepted if the HTTPS API is used incorrectly.

4

Which versions of Node.js are affected by CVE-2021-22939?

Node.js versions 12.22.5, 14.17.5, and 16.6.2 are affected by CVE-2021-22939.

5

How do I fix CVE-2021-22939?

To fix CVE-2021-22939, upgrade Node.js to version 12.22.5, 14.17.5, or 16.6.2.

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