The llhttp parser in the http module in Node v20.2.0 does not strictly use the CRLF sequence to delimit HTTP requests. This can lead to HTTP Request Smuggling (HRS). The CR character (without LF) is sufficient to delimit HTTP header fields in the llhttp parser. According to RFC7230 section 3, only the CRLF sequence should delimit each header-field. This impacts all Node.js active versions: v16, v18, and, v20
History

Thu, 13 Feb 2025 17:00:00 +0000

Type Values Removed Values Added
Description The llhttp parser in the http module in Node v20.2.0 does not strictly use the CRLF sequence to delimit HTTP requests. This can lead to HTTP Request Smuggling (HRS). The CR character (without LF) is sufficient to delimit HTTP header fields in the llhttp parser. According to RFC7230 section 3, only the CRLF sequence should delimit each header-field. This impacts all Node.js active versions: v16, v18, and, v20 The llhttp parser in the http module in Node v20.2.0 does not strictly use the CRLF sequence to delimit HTTP requests. This can lead to HTTP Request Smuggling (HRS). The CR character (without LF) is sufficient to delimit HTTP header fields in the llhttp parser. According to RFC7230 section 3, only the CRLF sequence should delimit each header-field. This impacts all Node.js active versions: v16, v18, and, v20

cve-icon MITRE

Status: PUBLISHED

Assigner: hackerone

Published:

Updated: 2025-02-13T16:49:32.084Z

Reserved: 2023-04-13T01:00:12.086Z

Link: CVE-2023-30589

cve-icon Vulnrichment

No data.

cve-icon NVD

Status : Modified

Published: 2023-07-01T00:15:10.293

Modified: 2025-02-13T17:16:25.090

Link: CVE-2023-30589

cve-icon Redhat

Severity : Moderate

Publid Date: 2023-06-20T00:00:00Z

Links: CVE-2023-30589 - Bugzilla