Affected Node.js versions are vulnerable to denial of service attacks when the whitelist includes “localhost6”. When “localhost6” is not present in /etc/hosts, it is just an ordinary domain that is resolved via DNS, i.e., over network. If the attacker controls the victim's DNS server or can spoof its responses, the DNS rebinding protection can be bypassed by using the “localhost6” domain. As long as the attacker uses the “localhost6” domain, they can still apply the attack described in CVE-2018-7160. Reference: https://nodejs.org/en/blog/vulnerability/february-2021-security-releases/#update-23-feb-2021-security-releases-available
Created nodejs tracking bugs for this issue: Affects: epel-all [bug 1932025] Affects: fedora-all [bug 1932029] Created nodejs:10/nodejs tracking bugs for this issue: Affects: fedora-all [bug 1932026] Created nodejs:12/nodejs tracking bugs for this issue: Affects: fedora-all [bug 1932030] Created nodejs:13/nodejs tracking bugs for this issue: Affects: fedora-all [bug 1932027] Created nodejs:14/nodejs tracking bugs for this issue: Affects: fedora-all [bug 1932028] Created nodejs:15/nodejs tracking bugs for this issue: Affects: fedora-all [bug 1932031]
Upstream Commit: https://github.com/nodejs/node/commit/1ca3f5abcb
This issue has been addressed in the following products: Red Hat Enterprise Linux 8 Via RHSA-2021:0734 https://access.redhat.com/errata/RHSA-2021:0734
This issue has been addressed in the following products: Red Hat Enterprise Linux 8 Via RHSA-2021:0735 https://access.redhat.com/errata/RHSA-2021:0735
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-22884
This issue has been addressed in the following products: Red Hat Enterprise Linux 8.1 Extended Update Support Via RHSA-2021:0739 https://access.redhat.com/errata/RHSA-2021:0739
This issue has been addressed in the following products: Red Hat Enterprise Linux 8.1 Extended Update Support Via RHSA-2021:0741 https://access.redhat.com/errata/RHSA-2021:0741
This issue has been addressed in the following products: Red Hat Enterprise Linux 8.2 Extended Update Support Via RHSA-2021:0738 https://access.redhat.com/errata/RHSA-2021:0738
This issue has been addressed in the following products: Red Hat Enterprise Linux 8.2 Extended Update Support Via RHSA-2021:0740 https://access.redhat.com/errata/RHSA-2021:0740
This issue has been addressed in the following products: Red Hat Enterprise Linux 8 Via RHSA-2021:0744 https://access.redhat.com/errata/RHSA-2021:0744
This issue has been addressed in the following products: Red Hat Software Collections for Red Hat Enterprise Linux 7 Red Hat Software Collections for Red Hat Enterprise Linux 7.6 EUS Red Hat Software Collections for Red Hat Enterprise Linux 7.7 EUS Via RHSA-2021:0827 https://access.redhat.com/errata/RHSA-2021:0827
This issue has been addressed in the following products: Red Hat Software Collections for Red Hat Enterprise Linux 7 Red Hat Software Collections for Red Hat Enterprise Linux 7.6 EUS Red Hat Software Collections for Red Hat Enterprise Linux 7.7 EUS Via RHSA-2021:0830 https://access.redhat.com/errata/RHSA-2021:0830
This issue has been addressed in the following products: Red Hat Software Collections for Red Hat Enterprise Linux 7 Red Hat Software Collections for Red Hat Enterprise Linux 7.6 EUS Red Hat Software Collections for Red Hat Enterprise Linux 7.7 EUS Via RHSA-2021:0831 https://access.redhat.com/errata/RHSA-2021:0831
Mitigation: Ensure that 'localhost6' is part of /etc/hosts. e.g.: ``` $ grep localhost6 /etc/hosts ::1 localhost localhost.localdomain localhost6 localhost6.localdomain6 ```
Statement: Red Hat Enterprise Linux ships with `localhost` and `localhost6` defined in `/etc/hosts`, and thus in general, would not be affected by this flaw, with some specific exceptions, such as : - `/etc/hosts` is disabled or has its default content (including `localhost6`) removed - the inspector is accessed using SSH tunneling from a remote computer that does not have `localhost6` statically defined Red Hat Quay from version 3.4 consumes the nodejs from RHEL, so security tracking is provided by the container health index on the customer portal [1]. Additionally there is no impact from this issue on Quay 3.3 and 3.2 because they don't use the debug option (--inspect) and nodejs is only used at build time [2]. [1] https://catalog.redhat.com/software/containers/quay/quay-rhel8/600e03aadd19c7786c43ae49?container-tabs=security [2] https://issues.redhat.com/browse/PROJQUAY-1409