CVE-2022-35256: HTTP Request Smuggling Due to Incorrect Parsing of Header Fields

Published Sep 23, 2022
·
Updated

A vulnerability was found in NodeJS due to improper validation of HTTP requests. The llhttp parser in the HTTP module in Node.js does not correctly handle header fields that are not terminated with CLRF. This issue may result in HTTP Request Smuggling. This flaw allows a remote attacker to send a specially crafted HTTP request to the server and smuggle arbitrary HTTP headers.

Other sources

Node.js is vulnerable to HTTP request smuggling, caused by the failure to correctly handle header fields that are not terminated with CLRF by the llhttp parser in the http module. A remote attacker could send a specially-crafted request to lead to HTTP Request Smuggling (HRS). An attacker could exploit this vulnerability to poison the web cache, bypass web application firewall protection, and conduct XSS attacks.

— IBM

The llhttp parser in the http module in Node v18.7.0 does not correctly handle header fields that are not terminated with CLRF. This may result in HTTP Request Smuggling.

The llhttp parser in the http module in Node.js v18.7.0 does not correctly handle header fields that are not terminated with CLRF. This may result in HTTP Request Smuggling.

— Node.Js

Affected Software

49 affected componentsFixes available
redhat/nodejs<1:16.17.1-1.el9_0
1:16.17.1-1.el9_0
redhat/nodejs<1:16.18.1-3.el9_1
1:16.18.1-3.el9_1
redhat/rh-nodejs14-nodejs<0:14.20.1-2.el7
0:14.20.1-2.el7
redhat/nodejs<14.20.1
14.20.1
redhat/nodejs<16.17.1
16.17.1
redhat/nodejs<18.9.1
18.9.1
redhat/llhttp<6.0.10
6.0.10
IBM Cognos Controller<=11.0.0 - 11.0.1
Nodejs Node.js>=14.0.0<=14.14.0
Nodejs Node.js>=14.15.0<14.20.1
Nodejs Node.js>=16.0.0<=16.12.0
Nodejs Node.js>=16.13.0<16.17.1
Nodejs Node.js>=18.0.0<18.9.1
llhttp Llhttp Node.js<6.0.10
Siemens Sinec Ins<1.0
Siemens Sinec Ins=1.0
Siemens Sinec Ins=1.0-sp1
Siemens Sinec Ins=1.0-sp2
Debian Debian Linux=11.0
Node.js Node.js>=14.0.0<14.20.1, >=16.0.0<16.17.1, >=18.0.0<18.9.1
14.20.116.17.118.9.1
Node.js Node.js>=14.0.0<14.20.1
14.20.1
Node.js Node.js>=16.0.0<16.17.1
16.17.1
Node.js Node.js>=18.0.0<18.9.1
18.9.1
debian/nodejs<18.10.0+dfsg-1
18.10.0+dfsg-1
debian/nodejs<18.10.0+dfsg-1
18.10.0+dfsg-1
debian/nodejs<18.10.0+dfsg-1
18.10.0+dfsg-1
debian/llhttp
9.4.3+~cs12.11.9-2
debian/nodejs
18.20.4+dfsg-1~deb12u218.20.4+dfsg-1~deb12u320.19.2+dfsg-1+deb13u220.19.2+dfsg-1+deb13u324.21.0+dfsg+~cs24.13.4-124.22.2+dfsg+~cs24.19.2-1
alpine/nodejs<14.20.1-r0
14.20.1-r0
alpine/nodejs<14.20.1-r0
14.20.1-r0
alpine/nodejs<16.17.1-r0
16.17.1-r0
alpine/nodejs<16.17.1-r0
16.17.1-r0
alpine/nodejs<16.17.1-r0
16.17.1-r0
alpine/nodejs<16.17.1-r0
16.17.1-r0
alpine/nodejs<16.17.1-r0
16.17.1-r0
alpine/nodejs<16.17.1-r0
16.17.1-r0
alpine/nodejs<16.17.1-r0
16.17.1-r0
alpine/nodejs<16.17.1-r0
16.17.1-r0
alpine/nodejs<16.17.1-r0
16.17.1-r0
alpine/nodejs<16.17.1-r0
16.17.1-r0
alpine/nodejs-current<18.9.1-r0
18.9.1-r0
alpine/nodejs-current<18.9.1-r0
18.9.1-r0
alpine/nodejs-current<18.9.1-r0
18.9.1-r0
alpine/nodejs-current<18.9.1-r0
18.9.1-r0
alpine/nodejs-current<18.9.1-r0
18.9.1-r0
alpine/nodejs-current<18.9.1-r0
18.9.1-r0
alpine/nodejs-current<18.9.1-r0
18.9.1-r0
alpine/nodejs-current<18.9.1-r0
18.9.1-r0
alpine/nodejs-current<18.9.1-r0
18.9.1-r0

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Upgrade

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

    Fixed in 1:16.17.1-1.el9_0
  2. Upgrade

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

    Fixed in 1:16.18.1-3.el9_1
  3. Upgrade

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

    Fixed in 0:14.20.1-2.el7
  4. Upgrade

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

    Fixed in 14.20.1
  5. Upgrade

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

    Fixed in 16.17.1
  6. Upgrade

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

    Fixed in 18.9.1
  7. Upgrade

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

    Fixed in 6.0.10
  8. Upgrade

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

    Fixed in 14.20.1Fixed in 16.17.1Fixed in 18.9.1
  9. Upgrade

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

    Fixed in 14.20.1
  10. Upgrade

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

    Fixed in 16.17.1
  11. Upgrade

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

    Fixed in 18.9.1
  12. Upgrade

    Upgrade debian/llhttp to a version that resolves this vulnerability.

    Fixed in 9.4.3+~cs12.11.9-2
  13. Upgrade

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

    Fixed in 18.20.4+dfsg-1~deb12u2Fixed in 18.20.4+dfsg-1~deb12u3Fixed in 20.19.2+dfsg-1+deb13u2Fixed in 20.19.2+dfsg-1+deb13u3Fixed in 24.21.0+dfsg+~cs24.13.4-1Fixed in 24.22.2+dfsg+~cs24.19.2-1
  14. Upgrade

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

    Fixed in 14.20.1-r0
  15. Upgrade

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

    Fixed in 16.17.1-r0
  16. Upgrade

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

    Fixed in 18.9.1-r0
  17. Upgrade

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

    Fixed in 18.10.0+dfsg-1
  18. Upgrade

    Upgrade llhttp to a version that resolves this vulnerability.

    Fixed in 6.0.10

Event History

Sep 23, 2022
CVE Published
via Node.js·12:00 AM
Data Sourced
via Node.js·12:00 AM
DescriptionSeverity
Data Sourced
via Node.js·04:13 PM
Affected Software
Dec 5, 2022
CVE Published
via MITRE·12:00 AM
Data Sourced
via MITRE·12:00 AM
DescriptionWeakness
Data Sourced
via NVD·10:15 PM
DescriptionSeverityWeaknessAffected Software
Data Sourced
via OSV·10:15 PM
DescriptionSeverityAffected Software

Parent advisories

This vulnerability appears in the following advisories.

Frequently Asked Questions

1

What is the vulnerability ID of this NodeJS vulnerability?

The vulnerability ID of this NodeJS vulnerability is CVE-2022-35256.

2

What is the severity of CVE-2022-35256?

The severity of CVE-2022-35256 is medium.

3

What is the affected software for CVE-2022-35256?

The affected software for CVE-2022-35256 is NodeJS versions 16.17.1-1.el9_0, 16.18.1-3.el9_1, 14.20.1, 16.17.1, and 18.9.1.

4

What is the description of CVE-2022-35256?

CVE-2022-35256 is a vulnerability in NodeJS due to improper validation of HTTP requests, allowing a remote attacker to send a potentially malicious request.

5

How can I fix CVE-2022-35256?

To fix CVE-2022-35256, it is recommended to update NodeJS to a version that includes the necessary security patches.

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