CVE-2020-8287: HTTP Request Smuggling in nodejs

Published Jan 4, 2021
·
Updated

A flaw was found in nodejs. Affected versions of Node.js allow two copies of a header field in an HTTP request. The first header field is recognized while the second is ignored leading to HTTP request smuggling. The highest threat from this vulnerability is to data confidentiality and integrity.

Other sources

Affected versions of Node.js allow two copies of a header field in a http request. For example, two Transfer-Encoding header fields. In this case Node.js identifies the first header field and ignores the second. This can lead to HTTP Request Smuggling (https://cwe.mitre.org/data/definitions/444.html).

All versions of the 15.x, 14.x, 12.x and 10.x releases lines

— Node.Js

Affected versions of Node.js allow two copies of a header field in a http request. For example, two Transfer-Encoding header fields. In this case Node.js identifies the first header field and ignores the second. This can lead to HTTP Request Smuggling.

Reference: https://nodejs.org/en/blog/vulnerability/january-2021-security-releases/

— Red Hat

HTTP Request Smuggling in nodejs - Affected versions of Node.js allow two copies of a header field in a http request. For example, two Transfer-Encoding header fields. In this case Node.js identifies the first header field and ignores the second. This can lead to HTTP Request Smuggling (https://cwe.mitre.org/data/definitions/444.html)

— Node.Js

Node.js is vulnerable to HTTP request smuggling. By sending specially crafted HTTP request headers, an attacker could exploit this vulnerability to poison the web cache, bypass web application firewall protection, and conduct XSS attacks.

— IBM

Node.js versions before 10.23.1, 12.20.1, 14.15.4, 15.5.1 allow two copies of a header field in an HTTP request (for example, two Transfer-Encoding header fields). In this case, Node.js identifies the first header field and ignores the second. This can lead to HTTP Request Smuggling.

Affected Software

56 affected componentsFixes available
redhat/rh-nodejs14-nodejs<0:14.15.4-2.el7
0:14.15.4-2.el7
redhat/rh-nodejs12-nodejs<0:12.20.1-1.el7
0:12.20.1-1.el7
redhat/rh-nodejs12-nodejs-nodemon<0:2.0.3-1.el7
0:2.0.3-1.el7
redhat/rh-nodejs10-nodejs<0:10.23.1-2.el7
0:10.23.1-2.el7
debian/http-parser
2.9.4-4+deb11u12.9.4-52.9.4-6
debian/nodejs
12.22.12~dfsg-1~deb11u412.22.12~dfsg-1~deb11u518.19.0+dfsg-6~deb12u218.19.0+dfsg-6~deb12u120.17.0+dfsg-2
IBM Cloud Pak for Security (CP4S)<=1.6.0.1
IBM Cloud Pak for Security (CP4S)<=1.6.0.0
IBM Cloud Pak for Security (CP4S)<=1.5.0.1
IBM Cloud Pak for Security (CP4S)<=1.5.0.0
IBM Cloud Pak for Security (CP4S)<=1.4.0.0
Nodejs Node.js>=10.0.0<10.23.1
Nodejs Node.js>=12.0.0<12.20.1
Nodejs Node.js>=14.0.0<14.15.4
Nodejs Node.js>=15.0.0<15.5.1
Debian Debian Linux=10.0
Fedoraproject Fedora=32
Fedoraproject Fedora=33
Oracle GraalVM=19.3.4
Oracle GraalVM=20.3.0
Siemens Sinec Infrastructure Network Services<1.0.1.1
redhat/node<10.23.1
10.23.1
redhat/node<12.20.1
12.20.1
redhat/node<14.15.4
14.15.4
redhat/node<15.5.1
15.5.1
Node.js Node.js>=10.0.0<10.23.1, >=12.0.0<12.20.1, >=14.0.0<14.15.4, >=15.0.0<15.5.1
10.23.112.20.114.15.415.5.1
Node.js Node.js>=10.0.0<10.23.1
10.23.1
Node.js Node.js>=12.0.0<12.20.1
12.20.1
Node.js Node.js>=14.0.0<14.15.4
14.15.4
Node.js Node.js>=15.0.0<15.5.1
15.5.1
alpine/nodejs<12.20.1-r0
12.20.1-r0
alpine/nodejs<12.20.1-r0
12.20.1-r0
alpine/nodejs<14.15.4-r0
14.15.4-r0
alpine/nodejs<14.15.4-r0
14.15.4-r0
alpine/nodejs<14.15.4-r0
14.15.4-r0
alpine/nodejs<14.15.4-r0
14.15.4-r0
alpine/nodejs<14.15.4-r0
14.15.4-r0
alpine/nodejs<14.15.4-r0
14.15.4-r0
alpine/nodejs<14.15.4-r0
14.15.4-r0
alpine/nodejs<14.15.4-r0
14.15.4-r0
alpine/nodejs<14.15.4-r0
14.15.4-r0
alpine/nodejs<14.15.4-r0
14.15.4-r0
alpine/nodejs<14.15.4-r0
14.15.4-r0
alpine/nodejs<14.15.4-r0
14.15.4-r0
alpine/nodejs-current<15.5.1-r0
15.5.1-r0
alpine/nodejs-current<15.5.1-r0
15.5.1-r0
alpine/nodejs-current<15.5.1-r0
15.5.1-r0
alpine/nodejs-current<15.5.1-r0
15.5.1-r0
alpine/nodejs-current<15.5.1-r0
15.5.1-r0
alpine/nodejs-current<15.5.1-r0
15.5.1-r0
alpine/nodejs-current<15.5.1-r0
15.5.1-r0
alpine/nodejs-current<15.5.1-r0
15.5.1-r0
alpine/nodejs-current<15.5.1-r0
15.5.1-r0
alpine/nodejs-current<15.5.1-r0
15.5.1-r0
alpine/nodejs-current<15.5.1-r0
15.5.1-r0
alpine/nodejs-current<15.5.1-r0
15.5.1-r0

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Upgrade

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

    Fixed in 0:14.15.4-2.el7
  2. Upgrade

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

    Fixed in 0:12.20.1-1.el7
  3. Upgrade

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

    Fixed in 0:2.0.3-1.el7
  4. Upgrade

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

    Fixed in 0:10.23.1-2.el7
  5. Upgrade

    Upgrade debian/http-parser to a version that resolves this vulnerability.

    Fixed in 2.9.4-4+deb11u1Fixed in 2.9.4-5Fixed in 2.9.4-6
  6. Upgrade

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

    Fixed in 12.22.12~dfsg-1~deb11u4Fixed in 12.22.12~dfsg-1~deb11u5Fixed in 18.19.0+dfsg-6~deb12u2Fixed in 18.19.0+dfsg-6~deb12u1Fixed in 20.17.0+dfsg-2
  7. Upgrade

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

    Fixed in 10.23.1
  8. Upgrade

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

    Fixed in 12.20.1
  9. Upgrade

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

    Fixed in 14.15.4
  10. Upgrade

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

    Fixed in 15.5.1
  11. Upgrade

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

    Fixed in 10.23.1Fixed in 12.20.1Fixed in 14.15.4Fixed in 15.5.1
  12. Upgrade

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

    Fixed in 10.23.1
  13. Upgrade

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

    Fixed in 12.20.1
  14. Upgrade

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

    Fixed in 14.15.4
  15. Upgrade

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

    Fixed in 15.5.1
  16. Upgrade

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

    Fixed in 12.20.1-r0
  17. Upgrade

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

    Fixed in 14.15.4-r0
  18. Upgrade

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

    Fixed in 15.5.1-r0
  19. Upgrade

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

    Fixed in 10.23.1
  20. Upgrade

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

    Fixed in 12.20.1
  21. Upgrade

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

    Fixed in 14.15.4
  22. Upgrade

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

    Fixed in 15.5.1

Event History

Jan 4, 2021
CVE Published
12:00 AM
Data Sourced
via Node.js·06:15 PM
SeverityAffected Software
Data Sourced
via Node.js·07:30 PM
Description
Jan 5, 2021
Exploit Published
via GitHub·02:09 AM
Data Sourced
via Red Hat·01:16 PM
DescriptionSeverityAffected Software
Jan 6, 2021
CVE Published
via MITRE·12:00 AM
Data Sourced
via MITRE·12:00 AM
DescriptionWeakness
Data Sourced
via NVD·09:15 PM
RemedyDescriptionSeverityWeaknessAffected Software
Data Sourced
via OSV·09:15 PM
DescriptionSeverityAffected Software

Parent advisories

This vulnerability appears in the following advisories.

Frequently Asked Questions

1

What is the vulnerability ID for this Node.js vulnerability?

The vulnerability ID for this Node.js vulnerability is CVE-2020-8287.

2

What is the severity of CVE-2020-8287?

The severity of CVE-2020-8287 is medium.

3

How does CVE-2020-8287 affect Node.js?

CVE-2020-8287 allows two copies of a header field in an HTTP request, leading to HTTP request smuggling and posing a threat to data confidentiality and integrity.

4

Which versions of Node.js are affected by CVE-2020-8287?

Node.js versions before 10.23.1, 12.20.1, 14.15.4, and 15.5.1 are affected by CVE-2020-8287.

5

How can I fix CVE-2020-8287?

To fix CVE-2020-8287, upgrade to Node.js versions 10.23.1, 12.20.1, 14.15.4, or 15.5.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