Question

Is DO aware of the VENOM vulnerability?

A friend linked me to an article earlier detailing a new vulnerability that was released that could allow attackers access to VM’s that are next to each other on any given host. The details are here: http://venom.crowdstrike.com/

From that site: "The bug is in QEMU’s virtual Floppy Disk Controller (FDC). This vulnerable FDC code is used in numerous virtualization platforms and appliances, notably Xen, KVM, and the native QEMU client.

VMware, Microsoft Hyper-V, and Bochs hypervisors are not impacted by this vulnerability."

Any information available from a DO rep about this?

Subscribe
Share

Also concerned about the Venom bug and how it affects DO servers.

Adding myself to the list of people who would like to hear DO say something about this :)

All who wants an answer, please do hit the LOVE button there in below the user name of the topic creator…

I am too looking for a statement of DO…

I’d also like an answer to this question! DO, please issue a statement of some kind.

Wondering this also.


Submit an answer
You can type!ref in this text area to quickly search our full set of tutorials, documentation & marketplace offerings and insert the link!

These answers are provided by our Community. If you find them useful, show some love by clicking the heart. If you run into issues leave a comment, or add your own answer to help others.

After performing a thorough audit of our infrastructure, we have published a blog update detailing the steps we taken concerning the vulnerability. As discussed there, a small number of our hypervisors will require a reboot. The team is currently working to schedule this in the least disruptive manner. If you have any additional questions, please reach out to the support team:

https://cloud.digitalocean.com/support

After performing a thorough audit of our infrastructure, we have published a blog update detailing the steps we taken concerning the vulnerability. As discussed there, a small number of our hypervisors will require a reboot. The team is currently working to schedule this in the least disruptive manner. If you have any additional questions, please reach out to the support team:

https://cloud.digitalocean.com/support

After performing a thorough audit of our infrastructure, we have published a blog update detailing the steps we taken concerning the vulnerability. As discussed there, a small number of our hypervisors will require a reboot. The team is currently working to schedule this in the least disruptive manner. If you have any additional questions, please reach out to the support team:

https://cloud.digitalocean.com/support

After performing a thorough audit of our infrastructure, we have published a blog update detailing the steps we taken concerning the vulnerability. As discussed there, a small number of our hypervisors will require a reboot. The team is currently working to schedule this in the least disruptive manner. If you have any additional questions, please reach out to the support team:

https://cloud.digitalocean.com/support

After performing a thorough audit of our infrastructure, we have published a blog update detailing the steps we taken concerning the vulnerability. As discussed there, a small number of our hypervisors will require a reboot. The team is currently working to schedule this in the least disruptive manner. If you have any additional questions, please reach out to the support team:

https://cloud.digitalocean.com/support

This was just posted by DO regarding this vulnerability.

https://www.digitalocean.com/company/blog/update-on-CVE-2015-3456/

This was just posted by DO regarding this vulnerability.

https://www.digitalocean.com/company/blog/update-on-CVE-2015-3456/