In etcd before versions 3.3.23 and 3.4.10, the etcd gateway is a simple TCP proxy to allow for basic service discovery and access. However, it is possible to include the gateway address as an endpoint. This results in a denial of service, since the endpoint can become stuck in a loop of requesting itself until there are no more available file descriptors to accept connections on the gateway. References: https://github.com/etcd-io/etcd/security/advisories/GHSA-2xhq-gv6c-p224
Created etcd tracking bugs for this issue: Affects: fedora-all [bug 1868875]
External References: https://github.com/etcd-io/etcd/security/advisories/GHSA-2xhq-gv6c-p224
FTR the etcd gateway is a v2 solution that is not used by OCP3 or OCP4 directly. This would limit exposure to RHEL7 consumers outside of OpenShift.
Upstream patch seems to be: https://github.com/etcd-io/etcd/commit/47001f28bd8ee3d11a9d5be24ecbdc7f01b99449
Statement: In Red Hat OpenShift Container Platform (RHOCP) the vulnerable ectd is used in the ose-etcd-container. The etcd gateway uses version 2 API which is not used by OCP, hence the impact by this vulnerability is Low. In Red Hat OpenStack Platform (RHOSP) does not use the etcd gateway and as well iits use is limited to within the internal API network, which is not accessible to any OpenStack tenants.
This issue has been addressed in the following products: Red Hat OpenStack Platform 16.1 Via RHSA-2021:0916 https://access.redhat.com/errata/RHSA-2021:0916
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-2020-15114
This issue has been addressed in the following products: Red Hat OpenShift Container Platform 4.8 Via RHSA-2021:2438 https://access.redhat.com/errata/RHSA-2021:2438