What Red Hat OpenShift Online and OpenShift Dedicated customers should know about Fallout and RIDL/ZombieLoad/MDS
May 16, 2019 | by
Earlier this week, details were made public about four CVEs related to microprocessor flaws that impact systems hosting Red Hat OpenShift Online (Starter and Pro) and Red Hat OpenShift Dedicated. Some organizations are referring to these as “Fallout”, “ZombieLoad”, “RIDL”, or collectively as MDS (Microarchitectural Data Sampling). Read additional technical details at these links (CVE-2018-12127, CVE-2018-12126, CVE-2018-11091 and CVE-2018-12130), and a more general explanation here.
The purpose of this blog is to notify our customers, and the community, of the actions Red Hat and the OpenShift SRE team have taken to patch and protect OpenShift Online and OpenShift Dedicated services.
On May 14, 2019, at approximately 17:00 UTC, Intel publicly announced the details of the flaws and remediations.
Shortly thereafter, OpenShift SRE initiated remediation on internal staging clusters and proceeded to the first Starter cluster at 21:00 (UTC).
Remediation on the remaining Starter and Pro clusters began the same day, finishing on May 15, after which further verification and validation was performed.
Remediation on all Dedicated clusters is in-progress, based on the preferred maintenance time-zones for each customer.
Any questions about the vulnerabilities or patches should be directed to Red Hat Support.
At Red Hat, the safety and security of our customers’ software and data is of utmost importance. Thank you for your continued trust and confidence in working with Red Hat.
This page will be updated with additional information as it becomes available.
Linux Containers continue to rapidly proliferate in the software industry. With the vast amount of solutions pertaining to containers out there, it is important to note the various security features ...
On April 2, 2020, details were made public about a security flaw that impacts systems running the HAProxy component when HTTP/2 support is enabled. Before the flaws were publicly disclosed, Red Hat ...