Node hang via mmap-driven container memory exhaustion
Published Jun 7, 2021 · Updated Aug 4, 2024
Resource exhaustion in Red Hat OpenShift Machine Config Operator allows remote authenticated users to hang nodes with memory-heavy containers. Red Hat has not published the faulty code path; the documented trigger is an mmap-heavy container consuming enough memory to leave its node unresponsive. The attacker must be able to run a container in the cluster, and the resulting node hang prevents new pods from being scheduled.
Summary
What happened
Resource exhaustion in Red Hat OpenShift Machine Config Operator allows remote authenticated users to hang nodes with memory-heavy containers. Red Hat has not published the faulty code path; the documented trigger is an mmap-heavy container consuming enough memory to leave its node unresponsive. The attacker must be able to run a container in the cluster, and the resulting node hang prevents new pods from being scheduled.
The record
- CVE
- CVE-2020-1750
- Published
- Jun 7, 2021
- Updated
- Aug 4, 2024
- Vendor
- Red Hat
- Product
- OpenShift Machine Config Operator
- Classifications
- CWE-400, T1499.004
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Jun 7, 2021CVE publishedPublication date reported by the CVE source.
- Aug 4, 2024Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=openshift/machine-config-operator 4.4.3, openshift/machine-config-operator 4.3.25, openshift/machine-config-operator 4.2.36
What conditions does exploitation require?
What is affected?
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo