CVE-2022-32214: HTTP Request Smuggling - Improper Delimiting of Header Fields

Published Jul 7, 2022
·
Updated

A vulnerability was found in NodeJS due to the llhttp parser in the http module not strictly using the CRLF sequence to delimit HTTP requests. This issue can lead to HTTP Request Smuggling (HRS). This flaw allows an attacker to send a specially crafted HTTP request to the server and smuggle arbitrary HTTP headers, causing web cache poisoning, and conducting XSS attacks.

Other sources

CVE-2022-32214

The llhttp parser in the http module does not strictly use the CRLF sequence to delimit HTTP requests. This can lead to HTTP Request Smuggling (HRS).

More details will be available at CVE-2022-32214 after publication.

Thank you to Zeyu Zhang (@zeyu2001) for reporting this vulnerability.

Impacts:

All versions of the 18.x, 16.x, and 14.x releases lines. llhttp v6.0.7 and llhttp v2.1.5 contains the fixes that were updated inside Node.js

— Red Hat

Node.js is vulnerable to HTTP request smuggling, caused by the failure to strictly use the CRLF sequence to delimit HTTP requests 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 <v14.20.1, <v16.17.1 and <v18.9.1 in the http module in Node.js does not strictly use the CRLF sequence to delimit HTTP requests. This can lead to HTTP Request Smuggling (HRS).

The llhttp parser in the http module does not strictly use the CRLF sequence to delimit HTTP requests. This can lead to HTTP Request Smuggling (HRS).

More details will be available at CVE-2022-32214 after publication.

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

llhttp v6.0.7 and llhttp v2.1.5 contains the fixes that were updated inside Node.js

— Node.Js

The llhttp parser in the http module in Node.js does not strictly use the CRLF sequence to delimit HTTP requests. This can lead to HTTP Request Smuggling (HRS).

— Node.Js

Affected Software

42 affected componentsFixes available
redhat/nodejs<1:16.16.0-1.el9_0
1:16.16.0-1.el9_0
redhat/rh-nodejs14-nodejs<0:14.20.0-2.el7
0:14.20.0-2.el7
redhat/nodejs<14.20.0
14.20.0
redhat/nodejs<16.20.0
16.20.0
redhat/nodejs<18.5.0
18.5.0
IBM Cognos Controller<=11.0.0 - 11.0.1
llhttp Llhttp Node.js<2.1.5
llhttp Llhttp Node.js>=6.0.0<6.0.7
Nodejs Node.js>=14.0.0<=14.14.0
Nodejs Node.js>=14.15.0<14.20.0
Nodejs Node.js>=16.0.0<=16.12.0
Nodejs Node.js>=16.13.0<16.16.0
Nodejs Node.js>=18.0.0<18.5.0
Debian Debian Linux=11.0
Stormshield Stormshield Management Center<3.3.0
Node.js Node.js>=14.0.0<14.20.0, >=16.0.0<16.20.0, >=18.0.0<18.5.0
14.20.016.20.018.5.0
debian/nodejs<18.6.0+dfsg-3
18.6.0+dfsg-3
debian/nodejs<18.6.0+dfsg-3
18.6.0+dfsg-3
debian/nodejs<18.6.0+dfsg-3
18.6.0+dfsg-3
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.6.0-r0
18.6.0-r0
alpine/nodejs-current<18.6.0-r0
18.6.0-r0
alpine/nodejs-current<18.6.0-r0
18.6.0-r0
alpine/nodejs-current<18.6.0-r0
18.6.0-r0
alpine/nodejs-current<18.6.0-r0
18.6.0-r0
alpine/nodejs-current<18.6.0-r0
18.6.0-r0
alpine/nodejs-current<18.6.0-r0
18.6.0-r0
alpine/nodejs-current<18.6.0-r0
18.6.0-r0
alpine/nodejs-current<18.6.0-r0
18.6.0-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.16.0-1.el9_0
  2. Upgrade

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

    Fixed in 0:14.20.0-2.el7
  3. Upgrade

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

    Fixed in 14.20.0
  4. Upgrade

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

    Fixed in 16.20.0
  5. Upgrade

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

    Fixed in 18.5.0
  6. Upgrade

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

    Fixed in 14.20.0Fixed in 16.20.0Fixed in 18.5.0
  7. Upgrade

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

    Fixed in 9.4.3+~cs12.11.9-2
  8. 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
  9. Upgrade

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

    Fixed in 14.20.1-r0
  10. Upgrade

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

    Fixed in 16.17.1-r0
  11. Upgrade

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

    Fixed in 18.6.0-r0
  12. Upgrade

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

    Fixed in 18.6.0+dfsg-3
  13. Upgrade

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

    Fixed in 14.20.1
  14. Upgrade

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

    Fixed in 16.17.1
  15. Upgrade

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

    Fixed in 18.9.1
  16. Upgrade

    Upgrade llhttp to a version that resolves this vulnerability.

    Fixed in 6.0.7
  17. Upgrade

    Upgrade llhttp to a version that resolves this vulnerability.

    Fixed in 2.1.5

Event History

Jul 7, 2022
CVE Published
via Node.js·04:00 PM
Data Sourced
via Node.js·04:00 PM
DescriptionSeverity
Jul 14, 2022
CVE Published
via MITRE·12:00 AM
Data Sourced
via MITRE·12:00 AM
DescriptionWeakness
Data Sourced
via NVD·03:15 PM
RemedyDescriptionSeverityWeaknessAffected Software
Data Sourced
via OSV·03:15 PM
DescriptionSeverityAffected Software

Parent advisories

This vulnerability appears in the following advisories.

Frequently Asked Questions

1

What is CVE-2022-32214?

CVE-2022-32214 is a vulnerability found in Node.js due to the llhttp parser in the http module not strictly using the CRLF sequence to delimit HTTP requests.

2

What is the severity of CVE-2022-32214?

The severity of CVE-2022-32214 is medium (6.5).

3

How does CVE-2022-32214 relate to HTTP Request Smuggling (HRS)?

CVE-2022-32214 can lead to HTTP Request Smuggling (HRS) as it allows an attacker to send a specially crafted HTTP request to the server and smuggle arbitrary data.

4

Which versions of Node.js are affected by CVE-2022-32214?

Node.js versions <v14.20.1, <v16.17.1, and <v18.9.1 are affected by CVE-2022-32214.

5

How can I mitigate CVE-2022-32214?

To mitigate CVE-2022-32214, update Node.js to versions 14.20.1, 16.17.1, or 18.9.1 or later.

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