CVE-2019-15605: HTTP request smuggling using malformed Transfer-Encoding header

Published Feb 6, 2020
·
Updated

Affected Node.js versions can be exploited to perform HTTP desync attacks and deliver malicious payloads to unsuspecting users. The payloads can be crafted by an attacker to hijack user sessions, poison cookies, perform clickjacking, and a multitude of other attacks depending on the architecture of the underlying system.

Downloads & release details

Node.js v10.19.0 (LTS) - https://nodejs.org/en/blog/release/v10.19.0/ Node.js v12.15.0 (LTS) - https://nodejs.org/en/blog/release/v12.15.0/ Node.js v13.8.0 (LTS) - https://nodejs.org/en/blog/release/v13.8.0/

Other sources

Affected Node.js versions can be exploited to perform HTTP desync attacks and deliver malicious payloads to unsuspecting users. The payloads can be crafted by an attacker to hijack user sessions, poison cookies, perform clickjacking, and a multitude of other attacks depending on the architecture of the underlying system.

Reported by Ethan Rubinson, a software engineer at eBay.

— Node.Js

HTTP request smuggling in Node.js 10, 12, and 13 causes malicious payload delivery when transfer-encoding is malformed

— Launchpad

HTTP request smuggling using malformed Transfer-Encoding header

— Node.Js

Node.js is vulnerable to HTTP request smuggling, caused by a flaw when handling unusual Transfer-Encoding HTTP header. By sending a specially-crafted request, an attacker could exploit this vulnerability to poison the web cache, bypass web application firewall protection, and conduct XSS attacks.

— IBM

Affected Software

66 affected componentsFixes available
redhat/nodejs<10.19.0
10.19.0
redhat/nodejs<12.15.0
12.15.0
redhat/nodejs<13.8.0
13.8.0
redhat/http-parser<2.9.3
2.9.3
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
Nodejs Node.js>=10.0.0<10.19.0
Nodejs Node.js>=12.0.0<12.15.0
Nodejs Node.js>=13.0.0<13.8.0
Debian Debian Linux=10.0
Fedoraproject Fedora=30
openSUSE Leap=15.1
redhat Software Collections=1.0
redhat Enterprise Linux=8.0
redhat Enterprise Linux Desktop=7.0
redhat Enterprise Linux Eus=7.7
redhat Enterprise Linux Eus=8.1
redhat Enterprise Linux Eus=8.2
redhat Enterprise Linux Eus=8.4
redhat Enterprise Linux Eus=8.6
redhat Enterprise Linux Server=7.0
redhat Enterprise Linux Server Aus=7.7
redhat Enterprise Linux Server Aus=8.2
redhat Enterprise Linux Server Aus=8.4
redhat Enterprise Linux Server Aus=8.6
redhat Enterprise Linux Server Tus=7.7
redhat Enterprise Linux Server Tus=8.2
redhat Enterprise Linux Server Tus=8.4
redhat Enterprise Linux Server Tus=8.6
redhat Enterprise Linux Workstation=7.0
Oracle GraalVM=19.3.1
Oracle GraalVM=20.0.0
Nodejs Node.js>=13.0.0<13.8.0
Node.js Node.js>=10.0.0<10.19.0, >=12.0.0<12.15.0, >=13.0.0<13.8.0
10.19.012.15.013.8.0
Node.js Node.js>=10.0.0<10.19.0
10.19.0
Node.js Node.js>=12.0.0<12.15.0
12.15.0
Node.js Node.js>=13.0.0<13.8.0
13.8.0
alpine/nodejs<10.19.0-r0
10.19.0-r0
alpine/nodejs<12.15.0-r0
12.15.0-r0
alpine/nodejs<12.15.0-r0
12.15.0-r0
alpine/nodejs<12.15.0-r0
12.15.0-r0
alpine/nodejs<12.15.0-r0
12.15.0-r0
alpine/nodejs<12.15.0-r0
12.15.0-r0
alpine/nodejs<12.15.0-r0
12.15.0-r0
alpine/nodejs<12.15.0-r0
12.15.0-r0
alpine/nodejs<12.15.0-r0
12.15.0-r0
alpine/nodejs<12.15.0-r0
12.15.0-r0
alpine/nodejs<12.15.0-r0
12.15.0-r0
alpine/nodejs<12.15.0-r0
12.15.0-r0
alpine/nodejs<12.15.0-r0
12.15.0-r0
alpine/nodejs<12.15.0-r0
12.15.0-r0
alpine/nodejs<12.15.0-r0
12.15.0-r0
alpine/nodejs<10.19.0-r0
10.19.0-r0
alpine/nodejs-current<13.11.0-r0
13.11.0-r0
alpine/nodejs-current<13.11.0-r0
13.11.0-r0
alpine/nodejs-current<13.11.0-r0
13.11.0-r0
alpine/nodejs-current<13.11.0-r0
13.11.0-r0
alpine/nodejs-current<13.11.0-r0
13.11.0-r0
alpine/nodejs-current<13.11.0-r0
13.11.0-r0
alpine/nodejs-current<13.11.0-r0
13.11.0-r0
alpine/nodejs-current<13.11.0-r0
13.11.0-r0
alpine/nodejs-current<13.11.0-r0
13.11.0-r0
alpine/nodejs-current<13.11.0-r0
13.11.0-r0
alpine/nodejs-current<13.11.0-r0
13.11.0-r0
alpine/nodejs-current<13.11.0-r0
13.11.0-r0
alpine/nodejs-current<13.11.0-r0
13.11.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 10.19.0
  2. Upgrade

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

    Fixed in 12.15.0
  3. Upgrade

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

    Fixed in 13.8.0
  4. Upgrade

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

    Fixed in 2.9.3
  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 to a fixed release to a version that resolves this vulnerability.

    Fixed in 10.19.0Fixed in 12.15.0Fixed in 13.8.0
  8. Upgrade

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

    Fixed in 10.19.0
  9. Upgrade

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

    Fixed in 12.15.0
  10. Upgrade

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

    Fixed in 13.8.0
  11. Upgrade

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

    Fixed in 10.19.0-r0
  12. Upgrade

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

    Fixed in 12.15.0-r0
  13. Upgrade

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

    Fixed in 13.11.0-r0
  14. Upgrade

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

    Fixed in 10.19.0
  15. Upgrade

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

    Fixed in 12.15.0
  16. Upgrade

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

    Fixed in 13.8.0

Event History

Feb 6, 2020
CVE Published
via Node.js·03:11 AM
Data Sourced
via Node.js·03:11 AM
SeverityAffected Software
Data Sourced
via Node.js·12:00 PM
Description
Feb 7, 2020
CVE Published
via MITRE·02:55 PM
Data Sourced
via MITRE·02:55 PM
DescriptionWeakness
Data Sourced
via NVD·03:15 PM
RemedyDescriptionSeverityWeaknessAffected Software
Data Sourced
via OSV·03:15 PM
DescriptionSeverityAffected Software
Jun 1, 2020
Data Sourced
via IBM·12:00 AM
DescriptionSeverityAffected Software

Frequently Asked Questions

1

What is the vulnerability ID for this Node.js HTTP request smuggling vulnerability?

The vulnerability ID for this Node.js HTTP request smuggling vulnerability is CVE-2019-15605.

2

What is the severity of CVE-2019-15605?

CVE-2019-15605 has a severity level of high.

3

Which versions of Node.js are affected by CVE-2019-15605?

Versions 10, 12, and 13 of Node.js are affected by CVE-2019-15605.

4

What is the potential impact of CVE-2019-15605?

CVE-2019-15605 can allow for malicious payload delivery when the transfer-encoding is malformed, potentially leading to unauthorized access or other security breaches.

5

How can I fix CVE-2019-15605 in Node.js?

To fix CVE-2019-15605 in Node.js, you should update to the recommended versions provided by the relevant software sources.

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