On Wednesday, Jan. 3, security researchers publicly detailed three potential vulnerabilities named “Meltdown” and “Spectre.” A pretty detailed description of the vulnerabilities can be found on Stratechery and a pretty good explanation for non-technical audience can be found on the Cloudflare blog.
|Public Vulnerability Name||Silicon Microcode Update Required on Host|
|Spectre||CVE-2017-5753||Variant 1||Bounds Check Bypass||No|
|Spectre||CVE-2017-5715||Variant 2||Branch Target Injection||Yes|
|Meltdown||CVE-2017-5754||Variant 3||Rogue Data Cache Load||No|
In an environment where multiple servers are sharing capabilities (for example virtual machines hosted in a cloud or on premise environment ), these vulnerabilities could mean it is possible for someone to access information in one virtual machine from another.
Below I tried to collect various statements from public cloud providers explaining how they protect their infrastructure from the above mentioned vulnerabilities and what are the recommended actions for their customers.
The infrastructure that runs Azure and isolates customer workloads from each other is protected. This means that other customers running on Azure cannot attack your application using these vulnerabilities.
While an OS update is not required to isolate your applications running on Azure from other customers running on Azure, it is always a best practice to keep your OS versions up-to-date.
In the following offerings, here are our recommended actions to update your Operating System:
Azure Cloud Services Enable auto update or ensure you are running the newest Guest OS. Azure Linux Virtual Machines Install updates from your operating system provider when available. Azure Windows Virtual Machines Verify that you are running a supported antivirus application before you install OS updates. Contact your antivirus software vendor for compatibility information.
Install the January security rollup.
Other Azure PaaS Services There is no action needed for customers using these services. Azure automatically keeps your OS versions up-to-date.
For Windows Server, administrators should ensure they have mitigations in place at the physical server level to ensure they can isolate virtualized workloads running on the server. For on-premises servers, this can be done by applying the appropriate microcode update to the physical server, and if you are running using Hyper-V updating it using our recent Windows Update release. If you are running on Azure, you do not need to take any steps to achieve virtualized isolation as we have already applied infrastructure updates to all servers in Azure that ensure your workloads are isolated from other customers running in our cloud. This means that other customers running on Azure cannot attack your VMs or applications using these vulnerabilities.
Amazon Web Services
All instances across the Amazon EC2 fleet are protected from all known instance-to-instance concerns of the CVEs previously listed. Instance-to-instance concerns assume an untrusted neighbor instance could read the memory of another instance or the AWS hypervisor. This issue has been addressed for AWS hypervisors, and no instance can read the memory of another instance, nor can any instance read AWS hypervisor memory. We have not observed meaningful performance impact for the overwhelming majority of EC2 workloads.
Recommended Customer Actions for AWS Batch, Amazon EC2, Amazon Elastic Beanstalk, Amazon Elastic Container Service, Amazon Elastic MapReduce, and Amazon Lightsail
While all customer instances are protected as described above, we recommend that customers patch their instance operating systems to isolate software running within the same instance and mitigate process-to-process concerns of CVE-2017-5754. For more details, refer to specific vendor guidance on patch availability and deployment
Google Cloud Platform
The infrastructure that runs Google Cloud products and isolates customer workloads from each other is protected. Some Cloud products require that customers also patch/update their runtime environments and applications.
Check link above for more details about which products and runtime environments need patching.
Oracle Cloud Platform
At time of writing, I did not find any information about how Oracle Cloud Platform may be affected by the above mentioned Spectre and Meltdown vulnerabilities. There are some ongoing discussions in Oracle community here and here but nothing specific to Oracle Cloud Platform.
SAP Cloud Platform
SAP as well did not publish information specific to their SAP cloud offerings yet. There exists a blog post where they recommend all customers to apply all fixes related to Windows operating systems.