RHSA-2022:6963: Important: nodejs 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.17.1).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.el9_0
16.17.1-1.el9_0
redhat/nodejs<16.17.1-1.el9_0
16.17.1-1.el9_0
redhat/nodejs-debuginfo<16.17.1-1.el9_0
16.17.1-1.el9_0
redhat/nodejs-debuginfo<16.17.1-1.el9_0
16.17.1-1.el9_0
redhat/nodejs-debugsource<16.17.1-1.el9_0
16.17.1-1.el9_0
redhat/nodejs-debugsource<16.17.1-1.el9_0
16.17.1-1.el9_0
redhat/nodejs-docs<16.17.1-1.el9_0
16.17.1-1.el9_0
redhat/nodejs-full-i18n<16.17.1-1.el9_0
16.17.1-1.el9_0
redhat/nodejs-libs<16.17.1-1.el9_0
16.17.1-1.el9_0
redhat/nodejs-libs<16.17.1-1.el9_0
16.17.1-1.el9_0
redhat/nodejs-libs-debuginfo<16.17.1-1.el9_0
16.17.1-1.el9_0
redhat/nodejs-libs-debuginfo<16.17.1-1.el9_0
16.17.1-1.el9_0
redhat/npm<8.15.0-1.16.17.1.1.el9_0
8.15.0-1.16.17.1.1.el9_0
redhat/nodejs-full-i18n<16.17.1-1.el9_0
16.17.1-1.el9_0
redhat/npm<8.15.0-1.16.17.1.1.el9_0
8.15.0-1.16.17.1.1.el9_0
redhat/nodejs<16.17.1-1.el9_0
16.17.1-1.el9_0
redhat/nodejs-debuginfo<16.17.1-1.el9_0
16.17.1-1.el9_0
redhat/nodejs-debugsource<16.17.1-1.el9_0
16.17.1-1.el9_0
redhat/nodejs-full-i18n<16.17.1-1.el9_0
16.17.1-1.el9_0
redhat/nodejs-libs<16.17.1-1.el9_0
16.17.1-1.el9_0
redhat/nodejs-libs-debuginfo<16.17.1-1.el9_0
16.17.1-1.el9_0
redhat/npm<8.15.0-1.16.17.1.1.el9_0
8.15.0-1.16.17.1.1.el9_0
redhat/nodejs<16.17.1-1.el9_0.aa
16.17.1-1.el9_0.aa
redhat/nodejs-debuginfo<16.17.1-1.el9_0.aa
16.17.1-1.el9_0.aa
redhat/nodejs-debugsource<16.17.1-1.el9_0.aa
16.17.1-1.el9_0.aa
redhat/nodejs-full-i18n<16.17.1-1.el9_0.aa
16.17.1-1.el9_0.aa
redhat/nodejs-libs<16.17.1-1.el9_0.aa
16.17.1-1.el9_0.aa
redhat/nodejs-libs-debuginfo<16.17.1-1.el9_0.aa
16.17.1-1.el9_0.aa
redhat/npm<8.15.0-1.16.17.1.1.el9_0.aa
8.15.0-1.16.17.1.1.el9_0.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.el9_0
  2. Upgrade

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

    Fixed in 16.17.1-1.el9_0
  3. Upgrade

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

    Fixed in 16.17.1-1.el9_0
  4. Upgrade

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

    Fixed in 16.17.1-1.el9_0
  5. Upgrade

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

    Fixed in 16.17.1-1.el9_0
  6. Upgrade

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

    Fixed in 16.17.1-1.el9_0
  7. Upgrade

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

    Fixed in 16.17.1-1.el9_0
  8. Upgrade

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

    Fixed in 8.15.0-1.16.17.1.1.el9_0
  9. Upgrade

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

    Fixed in 16.17.1-1.el9_0.aa
  10. Upgrade

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

    Fixed in 16.17.1-1.el9_0.aa
  11. Upgrade

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

    Fixed in 16.17.1-1.el9_0.aa
  12. Upgrade

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

    Fixed in 16.17.1-1.el9_0.aa
  13. Upgrade

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

    Fixed in 16.17.1-1.el9_0.aa
  14. Upgrade

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

    Fixed in 16.17.1-1.el9_0.aa
  15. Upgrade

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

    Fixed in 8.15.0-1.16.17.1.1.el9_0.aa
  16. Upgrade

    Upgrade nodejs to a version that resolves this vulnerability.

    Fixed in 16.17.1-1.el9_0
  17. Upgrade

    Upgrade npm to a version that resolves this vulnerability.

    Fixed in 8.15.0-1.16.17.1.1.el9_0

Event History

Jul 27, 2026
Advisory Published
via Red Hat·09:19 PM
Data Sourced
via Red Hat·09:19 PM
RemedyDescriptionAffected 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 the severity of RHSA-2022:6963?

The severity of RHSA-2022:6963 is classified as important.

2

How do I fix RHSA-2022:6963?

To fix RHSA-2022:6963, upgrade the Node.js package to version 16.17.1-1.el9_0.

3

What vulnerabilities are addressed in RHSA-2022:6963?

RHSA-2022:6963 addresses weak randomness vulnerabilities in Node.js.

4

Which versions of Node.js are affected by RHSA-2022:6963?

Versions prior to 16.17.1-1.el9_0 of Node.js are affected by RHSA-2022:6963.

5

Do I need to restart my system after fixing RHSA-2022:6963?

It is recommended to restart your system after upgrading to ensure all changes take effect.

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