Hide Forgot
The http parser accepts requests with a space (SP) right after the header name before the colon. This can lead to HTTP Request Smuggling (HRS). The fix for this is included in llhttp v2.1.4 and v6.0.6. Impacts: All versions of the 16.x, 14.x, and 12.x releases lines.
Created nodejs tracking bugs for this issue: Affects: epel-all [bug 2014116] Affects: fedora-all [bug 2014117] Created nodejs:10/nodejs tracking bugs for this issue: Affects: fedora-all [bug 2014118] Created nodejs:12/nodejs tracking bugs for this issue: Affects: fedora-all [bug 2014119] Created nodejs:13/nodejs tracking bugs for this issue: Affects: fedora-all [bug 2014120] Created nodejs:14/nodejs tracking bugs for this issue: Affects: fedora-all [bug 2014121] Created nodejs:15/nodejs tracking bugs for this issue: Affects: fedora-all [bug 2014122] Created nodejs:16/nodejs tracking bugs for this issue: Affects: fedora-all [bug 2014123]
HackerOne report (currently private) : https://hackerone.com/reports/1238099
Upstream fixes for Node.JS : node 12 : https://github.com/nodejs/node/commit/21a2e554e3eaa325abbdb28f366928d0ccc0a0f0 node 14 : https://github.com/nodejs/node/commit/8c254ca7e4693fb778d808fa835b095de6c9fdd4 node 16 : https://github.com/nodejs/node/commit/af488f8dc82d69847992ea1cd2f53dc8082b3b91 Upstream fixes for llhttp : v.6 : https://github.com/nodejs/llhttp/commit/ca84b6f903bc853c791ad14007a42f40ae34999e v.2.1.x : https://github.com/nodejs/llhttp/commit/15ecd206262481bb87f2f9cfbf377278f5513787
This issue has been addressed in the following products: Red Hat Enterprise Linux 8 Via RHSA-2021:5171 https://access.redhat.com/errata/RHSA-2021:5171
This issue has been addressed in the following products: Red Hat Software Collections for Red Hat Enterprise Linux 7 Via RHSA-2022:0041 https://access.redhat.com/errata/RHSA-2022:0041
This issue has been addressed in the following products: Red Hat Enterprise Linux 8.4 Extended Update Support Via RHSA-2022:0246 https://access.redhat.com/errata/RHSA-2022:0246
This issue has been addressed in the following products: Red Hat Enterprise Linux 8 Via RHSA-2022:0350 https://access.redhat.com/errata/RHSA-2022:0350
This bug is now closed. Further updates for individual products will be reflected on the CVE page(s): https://access.redhat.com/security/cve/cve-2021-22959
Will there be a fix for NodeJS 12?
(In reply to Laurie Morse from comment #17) > Will there be a fix for NodeJS 12? This CVE is rated as LOW, so there are not immediate plans to fix this. But it is quite likely we will be updating Node.js 12 around its EOL (as we did for Node.js 8 / 10), which should include the fix in the worst case. Please contact Red Hat support should you need to help prioritize the fix.
This issue has been addressed in the following products: Red Hat Software Collections for Red Hat Enterprise Linux 7 Via RHSA-2022:4914 https://access.redhat.com/errata/RHSA-2022:4914