RHSA-2022:6964: Important: nodejs:16 security update

Published Oct 17, 2022
·
Updated

Node.js is a software development platform for building fast and scalable network applications in the JavaScript programming language. The following packages have been upgraded to a later upstream version: nodejs 16.Security Fix(es): nodejs: weak randomness in WebCrypto keygen (CVE-2022-35255) nodejs: HTTP Request Smuggling due to incorrect parsing of header fields (CVE-2022-35256) For more details about the security issue(s), including the impact, a CVSS score, acknowledgments, and other related information, refer to the CVE page(s) listed in the References section.

Affected Software

29 affected componentsFixes available
redhat/nodejs<16.17.1-1.module+el8.6.0+16848+a483195a
16.17.1-1.module+el8.6.0+16848+a483195a
redhat/nodejs-nodemon<2.0.19-2.module+el8.6.0+16240+7ca51420
2.0.19-2.module+el8.6.0+16240+7ca51420
redhat/nodejs-packaging<25-1.module+el8.5.0+10992+fac5fe06
25-1.module+el8.5.0+10992+fac5fe06
redhat/nodejs-docs<16.17.1-1.module+el8.6.0+16848+a483195a
16.17.1-1.module+el8.6.0+16848+a483195a
redhat/nodejs-nodemon<2.0.19-2.module+el8.6.0+16240+7ca51420
2.0.19-2.module+el8.6.0+16240+7ca51420
redhat/nodejs-packaging<25-1.module+el8.5.0+10992+fac5fe06
25-1.module+el8.5.0+10992+fac5fe06
redhat/nodejs<16.17.1-1.module+el8.6.0+16848+a483195a
16.17.1-1.module+el8.6.0+16848+a483195a
redhat/nodejs-debuginfo<16.17.1-1.module+el8.6.0+16848+a483195a
16.17.1-1.module+el8.6.0+16848+a483195a
redhat/nodejs-debugsource<16.17.1-1.module+el8.6.0+16848+a483195a
16.17.1-1.module+el8.6.0+16848+a483195a
redhat/nodejs-devel<16.17.1-1.module+el8.6.0+16848+a483195a
16.17.1-1.module+el8.6.0+16848+a483195a
redhat/nodejs-full-i18n<16.17.1-1.module+el8.6.0+16848+a483195a
16.17.1-1.module+el8.6.0+16848+a483195a
redhat/npm<8.15.0-1.16.17.1.1.module+el8.6.0+16848+a483195a
8.15.0-1.16.17.1.1.module+el8.6.0+16848+a483195a
redhat/nodejs-debuginfo<16.17.1-1.module+el8.6.0+16848+a483195a
16.17.1-1.module+el8.6.0+16848+a483195a
redhat/nodejs-debugsource<16.17.1-1.module+el8.6.0+16848+a483195a
16.17.1-1.module+el8.6.0+16848+a483195a
redhat/nodejs-devel<16.17.1-1.module+el8.6.0+16848+a483195a
16.17.1-1.module+el8.6.0+16848+a483195a
redhat/nodejs-full-i18n<16.17.1-1.module+el8.6.0+16848+a483195a
16.17.1-1.module+el8.6.0+16848+a483195a
redhat/npm<8.15.0-1.16.17.1.1.module+el8.6.0+16848+a483195a
8.15.0-1.16.17.1.1.module+el8.6.0+16848+a483195a
redhat/nodejs<16.17.1-1.module+el8.6.0+16848+a483195a
16.17.1-1.module+el8.6.0+16848+a483195a
redhat/nodejs-debuginfo<16.17.1-1.module+el8.6.0+16848+a483195a
16.17.1-1.module+el8.6.0+16848+a483195a
redhat/nodejs-debugsource<16.17.1-1.module+el8.6.0+16848+a483195a
16.17.1-1.module+el8.6.0+16848+a483195a
redhat/nodejs-devel<16.17.1-1.module+el8.6.0+16848+a483195a
16.17.1-1.module+el8.6.0+16848+a483195a
redhat/nodejs-full-i18n<16.17.1-1.module+el8.6.0+16848+a483195a
16.17.1-1.module+el8.6.0+16848+a483195a
redhat/npm<8.15.0-1.16.17.1.1.module+el8.6.0+16848+a483195a
8.15.0-1.16.17.1.1.module+el8.6.0+16848+a483195a
redhat/nodejs<16.17.1-1.module+el8.6.0+16848+a483195a.aa
16.17.1-1.module+el8.6.0+16848+a483195a.aa
redhat/nodejs-debuginfo<16.17.1-1.module+el8.6.0+16848+a483195a.aa
16.17.1-1.module+el8.6.0+16848+a483195a.aa
redhat/nodejs-debugsource<16.17.1-1.module+el8.6.0+16848+a483195a.aa
16.17.1-1.module+el8.6.0+16848+a483195a.aa
redhat/nodejs-devel<16.17.1-1.module+el8.6.0+16848+a483195a.aa
16.17.1-1.module+el8.6.0+16848+a483195a.aa
redhat/nodejs-full-i18n<16.17.1-1.module+el8.6.0+16848+a483195a.aa
16.17.1-1.module+el8.6.0+16848+a483195a.aa
redhat/npm<8.15.0-1.16.17.1.1.module+el8.6.0+16848+a483195a.aa
8.15.0-1.16.17.1.1.module+el8.6.0+16848+a483195a.aa

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Upgrade

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

    Fixed in 16.17.1-1.module+el8.6.0+16848+a483195a
  2. Upgrade

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

    Fixed in 2.0.19-2.module+el8.6.0+16240+7ca51420
  3. Upgrade

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

    Fixed in 25-1.module+el8.5.0+10992+fac5fe06
  4. Upgrade

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

    Fixed in 16.17.1-1.module+el8.6.0+16848+a483195a
  5. Upgrade

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

    Fixed in 16.17.1-1.module+el8.6.0+16848+a483195a
  6. Upgrade

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

    Fixed in 16.17.1-1.module+el8.6.0+16848+a483195a
  7. Upgrade

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

    Fixed in 16.17.1-1.module+el8.6.0+16848+a483195a
  8. Upgrade

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

    Fixed in 16.17.1-1.module+el8.6.0+16848+a483195a
  9. Upgrade

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

    Fixed in 8.15.0-1.16.17.1.1.module+el8.6.0+16848+a483195a
  10. Upgrade

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

    Fixed in 16.17.1-1.module+el8.6.0+16848+a483195a.aa
  11. Upgrade

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

    Fixed in 16.17.1-1.module+el8.6.0+16848+a483195a.aa
  12. Upgrade

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

    Fixed in 16.17.1-1.module+el8.6.0+16848+a483195a.aa
  13. Upgrade

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

    Fixed in 16.17.1-1.module+el8.6.0+16848+a483195a.aa
  14. Upgrade

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

    Fixed in 16.17.1-1.module+el8.6.0+16848+a483195a.aa
  15. Upgrade

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

    Fixed in 8.15.0-1.16.17.1.1.module+el8.6.0+16848+a483195a.aa
  16. Upgrade

    Upgrade nodejs to a version that resolves this vulnerability.

    Fixed in 16

Event History

Apr 21, 2024
Advisory Published
via Red Hat·01:33 AM

Frequently Asked Questions

1

What is the severity of RHSA-2022:6964?

The severity of RHSA-2022:6964 is categorized as important.

2

How do I fix RHSA-2022:6964?

To fix RHSA-2022:6964, upgrade the affected Node.js packages to version 16.17.1-1.module+el8.6.0+16848+a483195a.

3

Which packages are affected by RHSA-2022:6964?

The affected packages in RHSA-2022:6964 include nodejs, nodejs-nodemon, and npm among others.

4

Is there a workaround for RHSA-2022:6964?

There is no specific workaround for RHSA-2022:6964, and upgrading to the fixed package version is recommended.

5

What vulnerability does RHSA-2022:6964 address?

RHSA-2022:6964 addresses weak randomness in WebCrypto which can potentially lead to security vulnerabilities.

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