CVE-2022-32213: bypass via obs-fold mechanic

Published Jul 8, 2022
·
Updated

A vulnerability was found in NodeJS due to improper validation of HTTP requests. The llhttp parser in the http module does not correctly parse and validate Transfer-Encoding headers. This issue can lead to HTTP Request Smuggling (HRS), causing web cache poisoning, and conducting XSS attacks.

Other sources

CVE-2022-32213

The llhttp parser in the http module does not correctly parse and validate Transfer-Encoding headers. This can lead to HTTP Request Smuggling (HRS).

More details will be available at CVE-2022-32213 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 correctly parse and validate Transfer-Encoding headers 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 fix for CVE-2022-32213 can be bypassed using an obs-fold, which the Node.js HTTP parser supports. If the Node.js HTTP module is used as a proxy, then it incorrectly parses the transfer-encoding header as indicative of chunked request, while folding the headers and hence forwarding Transfer-Encoding: chunked abc which is not a valid transfer-encoding header to the downstream server. As such this can lead to HTTP request smuggling as indicated by CVE-2022-32213.

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

llhttp v6.0.10 contains the fixes that were updated inside Node.js

— Node.Js

The llhttp parser <v14.20.1, <v16.17.1 and <v18.9.1 in the http module in Node.js does not correctly parse and validate Transfer-Encoding headers and can lead to HTTP Request Smuggling (HRS).

The llhttp parser in the http module in Node.js does not correctly parse and validate Transfer-Encoding headers. This can lead to HTTP Request Smuggling (HRS).

— Node.Js

Affected Software

51 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
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.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
Fedoraproject Fedora=35
Fedoraproject Fedora=36
Fedoraproject Fedora=37
Siemens Sinec Ins=1.0
Siemens Sinec Ins=1.0-sp1
Siemens Sinec Ins=1.0-sp2
Debian Debian Linux=11.0
Stormshield Stormshield Management Center<3.3.2
redhat/nodejs<14.20.0
14.20.0
redhat/nodejs<16.20.0
16.20.0
redhat/nodejs<18.5.0
18.5.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.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.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.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.1Fixed in 16.17.1Fixed in 18.9.1
  7. Upgrade

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

    Fixed in 14.20.1
  8. Upgrade

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

    Fixed in 16.17.1
  9. Upgrade

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

    Fixed in 18.9.1
  10. Upgrade

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

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

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

    Fixed in 14.20.1-r0
  13. Upgrade

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

    Fixed in 16.17.1-r0
  14. Upgrade

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

    Fixed in 18.9.1-r0
  15. Upgrade

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

    Fixed in 18.6.0+dfsg-3
  16. Upgrade

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

    Fixed in 14.20.1
  17. Upgrade

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

    Fixed in 16.17.1
  18. Upgrade

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

    Fixed in 18.9.1
  19. Upgrade

    Upgrade llhttp to a version that resolves this vulnerability.

    Fixed in 6.0.10

Event History

Jul 8, 2022
CVE Published
12:00 AM
Data Sourced
via Red Hat·06:47 PM
DescriptionSeverityAffected Software
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
Sep 23, 2022
Data Sourced
via Node.js·12:00 AM
DescriptionSeverity
Data Sourced
via Node.js·04:13 PM
Affected Software

Parent advisories

This vulnerability appears in the following advisories.

Frequently Asked Questions

1

What is CVE-2022-32213?

CVE-2022-32213 is a vulnerability found in NodeJS due to improper validation of HTTP requests.

2

How does CVE-2022-32213 impact web applications?

CVE-2022-32213 can lead to HTTP Request Smuggling (HRS), causing web cache poisoning, and conducting XSS attacks.

3

What software versions are affected by CVE-2022-32213?

Versions of llhttp <v14.20.1, <v16.17.1, and <v18.9.1 in the http module in Node.js are affected.

4

What is the severity of CVE-2022-32213?

CVE-2022-32213 has a severity rating of 6.5 (medium).

5

How can I fix CVE-2022-32213?

To fix CVE-2022-32213, update Node.js to a version equal to or above v14.20.1, v16.17.1, or v18.9.1.

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