llhttp allows HTTP Request Smuggling via Improper Delimiting of Header Fields
The llhttp parser in the http module in Node.js does not strictly use the CRLF sequence to delimit HTTP requests. The LF character (without CR) is sufficient to delimit HTTP header fields in the lihttp parser. According to RFC7230 section 3, only the CRLF sequence should delimit each header-field. This can lead to HTTP Request Smuggling (HRS).
01
describes (1)
Related CVEs.
| ID | severity | exploitable | ||
|---|---|---|---|---|
| CVE-2022-32214US | medium6.5 | — | ||
The llhttp parser <v14.20.1, <v16.17.1 and <v18.9.1 in the http module in Node.js does not strictly use the CRLF sequence to delimit HTTP requests. This can lead to HTTP Request Sm… | ||||
02
references
External citations — patches, advisories, analysis.
- https://datatracker.ietf.org/doc/html/rfc7230#section-3WEB
- https://github.com/nodejs/llhttp/commit/18a4afc7ffb4e49dc9e2daebc50588199a6d1dbbWEB
- https://hackerone.com/reports/1524692WEB
- https://nodejs.org/en/blog/vulnerability/july-2022-security-releasesWEB
- https://nvd.nist.gov/vuln/detail/CVE-2022-32214ADVISORY
- https://security.netapp.com/advisory/ntap-20220915-0001WEB
- https://www.debian.org/security/2023/dsa-5326WEB
scry
Advisories like this name the exposed products attackers go after on your perimeter. See what is exposed on your perimeter with a free passive scan.
Free scan