Описание
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
Релиз | Статус | Примечание |
---|---|---|
bionic | ignored | end of standard support |
devel | not-affected | 18.19.1+dfsg-2ubuntu4 |
esm-apps/bionic | not-affected | code not present |
esm-apps/focal | not-affected | code not present |
esm-apps/jammy | not-affected | code not present |
esm-apps/noble | not-affected | 18.19.1+dfsg-2ubuntu4 |
esm-apps/xenial | not-affected | code not present |
esm-infra-legacy/trusty | not-affected | code not present |
focal | not-affected | code not present |
jammy | not-affected | code not present |
Показывать по
EPSS
7.5 High
CVSS3
Связанные уязвимости
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
The llhttp parser in the http module in Node v20.2.0 does not strictly ...
EPSS
7.5 High
CVSS3