First published: Thu Feb 27 2020(Updated: )
A flaw was found in the machine-config-operator that causes an OpenShift node to become unresponsive when a container consumes a large amount of memory. An attacker could use this flaw to deny access to schedule new pods in the OpenShift cluster. This was fixed in openshift/machine-config-operator 4.4.3, openshift/machine-config-operator 4.3.25, openshift/machine-config-operator 4.2.36.
Credit: secalert@redhat.com
Affected Software | Affected Version | How to fix |
---|---|---|
redhat/openshift/machine-config-operator | <4.4.3 | 4.4.3 |
redhat/openshift/machine-config-operator | <4.3.25 | 4.3.25 |
redhat/openshift/machine-config-operator | <4.2.36 | 4.2.36 |
Redhat Machine-config-operator | >=4.2.0<4.2.36 | |
Redhat Machine-config-operator | >=4.3.0<4.3.25 | |
Redhat Machine-config-operator | >=4.4.0<4.4.3 |
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
CVE-2020-1750 is classified as a moderate severity vulnerability.
To fix CVE-2020-1750, upgrade to openshift/machine-config-operator versions 4.4.3, 4.3.25, or 4.2.36 or newer.
CVE-2020-1750 is caused by a flaw in the machine-config-operator that leads to an OpenShift node becoming unresponsive under high memory consumption by containers.
The impact of CVE-2020-1750 is that it can lead to denial of access for scheduling new pods in the OpenShift cluster.
Versions of openshift/machine-config-operator from prior to 4.4.3, 4.3.25, and 4.2.36 are affected by CVE-2020-1750.