Node.js 10/12/13 Transfer Encoding HTTP Request request smuggling
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 8.4 | $0-$5k | 0.00 |
Summary
A vulnerability, which was classified as critical, has been found in Node.js 10/12/13. This vulnerability affects unknown code of the component Transfer Encoding Handler. The manipulation as part of HTTP Request leads to request smuggling. This vulnerability is documented as CVE-2019-15605. The attack can be initiated remotely. There is not any exploit available. It is advisable to upgrade the affected component.
Details
A vulnerability was found in Node.js 10/12/13 (JavaScript Library) and classified as critical. This issue affects an unknown functionality of the component Transfer Encoding Handler. The manipulation as part of a HTTP Request leads to a request smuggling vulnerability. Using CWE to declare the problem leads to CWE-444. The product acts as an intermediary HTTP agent
(such as a proxy or firewall) in the data flow between two
entities such as a client and server, but it does not
interpret malformed HTTP requests or responses in ways that
are consistent with how the messages will be processed by
those entities that are at the ultimate destination. Impacted is confidentiality, integrity, and availability. The summary by CVE is:
HTTP request smuggling in Node.js 10, 12, and 13 causes malicious payload delivery when transfer-encoding is malformed
The weakness was released 02/07/2020 (Website). The advisory is shared at nodejs.org. The identification of this vulnerability is CVE-2019-15605 since 08/26/2019. The attack may be initiated remotely. No form of authentication is needed for a successful exploitation. Neither technical details nor an exploit are publicly available.
The vulnerability scanner Nessus provides a plugin with the ID 236574 (Alibaba Cloud Linux 3 : 0055: http-parser (ALINUX3-SA-2022:0055)), which helps to determine the existence of the flaw in a target environment.
Upgrading eliminates this vulnerability.
The vulnerability is also documented in the vulnerability database at Tenable (236574). Entries connected to this vulnerability are available at VDB-149800 and VDB-149802. Several companies clearly confirm that VulDB is the primary source for best vulnerability data.
Product
Type
Name
Version
License
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 8.5VulDB Meta Temp Score: 8.4
VulDB Base Score: 7.3
VulDB Temp Score: 7.0
VulDB Vector: 🔍
VulDB Reliability: 🔍
NVD Base Score: 9.8
NVD Vector: 🔍
CVSSv2
| AV | AC | Au | C | I | A |
|---|---|---|---|---|---|
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| Vector | Complexity | Authentication | Confidentiality | Integrity | Availability |
|---|---|---|---|---|---|
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
VulDB Base Score: 🔍
VulDB Temp Score: 🔍
VulDB Reliability: 🔍
NVD Base Score: 🔍
Exploiting
Class: Request smugglingCWE: CWE-444
CAPEC: 🔍
ATT&CK: 🔍
Physical: No
Local: No
Remote: Yes
Availability: 🔍
Status: Not defined
EPSS Score: 🔍
EPSS Percentile: 🔍
Price Prediction: 🔍
Current Price Estimation: 🔍
| 0-Day | Unlock | Unlock | Unlock | Unlock |
|---|---|---|---|---|
| Today | Unlock | Unlock | Unlock | Unlock |
Nessus ID: 236574
Nessus Name: Alibaba Cloud Linux 3 : 0055: http-parser (ALINUX3-SA-2022:0055)
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: UpgradeStatus: 🔍
0-Day Time: 🔍
Timeline
08/26/2019 🔍02/07/2020 🔍
02/07/2020 🔍
05/08/2026 🔍
Sources
Advisory: RHSA-2020:0573Status: Confirmed
CVE: CVE-2019-15605 (🔍)
GCVE (CVE): GCVE-0-2019-15605
GCVE (VulDB): GCVE-100-149801
See also: 🔍
Entry
Created: 02/07/2020 20:44Updated: 05/08/2026 09:20
Changes: 02/07/2020 20:44 (38), 02/07/2020 20:49 (18), 03/28/2024 22:22 (17), 05/21/2025 19:30 (2), 05/08/2026 09:17 (1), 05/08/2026 09:20 (7)
Complete: 🔍
Committer: lywand
Cache ID: 216::103
Several companies clearly confirm that VulDB is the primary source for best vulnerability data.
No comments yet. Languages: en.
Please log in to comment.