CVE-2021-22940: Use after free on close http2 on stream canceling

Published Aug 11, 2021
·
Updated

A flaw was found in Node.js, where it is vulnerable to a use-after-free attack. This flaw allows an attacker to exploit memory corruption to change process behavior. The highest threat from this vulnerability is to confidentiality and integrity.

Other sources

Node.js before 16.6.1, 14.17.5, and 12.22.5 is vulnerable to a use after free attack where an attacker might be able to exploit the memory corruption, to change process behavior.

Node.js could allow a remote attacker to bypass security restrictions, caused by an incomplete fix for CVE-2021-22930 related to a use-after-free on close http2 on stream canceling. An attacker could exploit this vulnerability to corrupt memory to change process behavior.

— IBM

Node.js was vulnerable to a use after free attack where an attacker might be able to exploit memory corruption to change process behavior. The issue is a follow on to CVE-2021-22930 as the issue was not completely resolved in the fix for CVE-2021-22930.

References: https://nodejs.org/en/blog/vulnerability/aug-2021-security-releases/

— Red Hat

Node.js was vulnerable to a use after free attack where an attacker might be able to exploit memory corruption to change process behavior. The issue is a follow on to CVE-2021-22930 as the issue was not completely resolved in the fix for CVE-2021-22930.

You can read more about it in: https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2021-22940

All versions of the 16.x, 14.x, and 12.x releases lines

— Node.Js

Node.js was vulnerable to a use after free attack where an attacker might be able to exploit memory corruption to change process behavior. The issue is a follow on to CVE-2021-22930 as the issue was not completely resolved in the fix for CVE-2021-22930. You can read more about it in: https://nvd.nist.gov/vuln/detail/CVE-2021-22940

— Node.Js

Affected Software

23 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 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

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 Node.js to a version that resolves this vulnerability.

    Fixed in 16.6.1
  12. Upgrade

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

    Fixed in 14.17.5
  13. Upgrade

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

    Fixed in 12.22.5

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

Frequently Asked Questions

1

What is the vulnerability ID for this Node.js vulnerability?

The vulnerability ID for this Node.js vulnerability is CVE-2021-22940.

2

What is the severity of CVE-2021-22940?

The severity of CVE-2021-22940 is high.

3

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

CVE-2021-22940 allows a remote attacker to bypass security restrictions and corrupt memory to change process behavior in Node.js.

4

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

Versions 12.22.5, 14.17.5, and prior are affected by CVE-2021-22940.

5

How can I fix the CVE-2021-22940 vulnerability in Node.js?

To fix the CVE-2021-22940 vulnerability in Node.js, update to version 16.6.1, 14.17.5, or 12.22.5 or later.

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