Bug 2014057 (CVE-2021-22959)
Summary: | CVE-2021-22959 llhttp: HTTP Request Smuggling due to spaces in headers | ||
---|---|---|---|
Product: | [Other] Security Response | Reporter: | Cedric Buissart <cbuissar> |
Component: | vulnerability | Assignee: | Red Hat Product Security <security-response-team> |
Status: | CLOSED ERRATA | QA Contact: | |
Severity: | low | Docs Contact: | |
Priority: | low | ||
Version: | unspecified | CC: | bdettelb, caswilli, dkuc, fjansen, hhorak, jnakfour, jorton, kaycoth, lmorse, mrunge, nodejs-maint, nodejs-sig, sgallagh, thrcka, zsvetlik |
Target Milestone: | --- | Keywords: | Security |
Target Release: | --- | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | llhttp 6.0.6, llhttp 2.1.4, node 12.22.7, node 14.18.1, node 16.11.1 | Doc Type: | If docs needed, set a value |
Doc Text: |
An HTTP Request Smuggling (HRS) vulnerability was found in the llhttp library, used by Node.JS. Spaces as part of the header names were accepted as valid. In situations where HTTP conversations are being proxied (such as proxy, reverse-proxy, load-balancer), an attacker can use this flaw to inject arbitrary messages through the proxy. The highest threat from this vulnerability is to confidentiality and integrity.
|
Story Points: | --- |
Clone Of: | Environment: | ||
Last Closed: | 2022-02-01 22:32:13 UTC | Type: | --- |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: | |||
Bug Depends On: | 2014116, 2014117, 2014118, 2014119, 2014120, 2014121, 2014122, 2014123, 2014130, 2014131, 2014132, 2014133, 2014134, 2014499, 2027644, 2027648, 2027649, 2031773, 2086790, 2086792, 2086793, 2086794, 2087164 | ||
Bug Blocks: | 2014056 |
Description
Cedric Buissart
2021-10-14 11:56:23 UTC
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 |