4 ms·

Has anybody launched this in a VM under Xen and/or EC2 to see if AWS is vulnerable? If this can mangle the Dom0 over a paravirt DomU, this would be awfully inte

Has anybody launched this in a VM under Xen and/or EC2 to see if AWS is vulnerable? If this can mangle the Dom0 over a paravirt DomU, this would be awfully interesting. /me off to test... update: Would be nastier if it forked cpux2 times or something at startup. My test server is running fine for 15 minutes with it active. A bit slow, but still responsive and accepting new SSH connections. Server is Centos 5.5 with 2.6.18-194.26.1.el5 Proc net unix seems stable as below, maybe slowly growing now. [root@xenpig net]# cat /proc/net/unix | wc -l 153406 I have kill -9 that process several times though, and it ain't dying, so that is an issue.

deutronium 16y ago
You can cap the amount of CPU utilization for VMs, so I don't think you could bring the server to a crawl, only the VM.
switch007 16y ago
I ran it on a domU and it seemed to have no affect at all on the host machine (Xen 3.3)
SaltwaterC 16y ago
As for other virtualization products, I tried in inside an OpenVZ setup (Proxmox 1.6). A container almost took down the hardware node. It was very slow, although responsive. "vzctl stop" timed out. Just a reboot brought back that machine. Therefore, I am living under the impression that any container based virtualization technology is vulnerable due to the usage of the same kernel for all the available virtual machines. Proxmox ran inside a VirtualBox instance. All the allocated memory to the virtual machine was taken by the exploit. Even more, after rebooting the VirtualBox machine, it leaked the whole memory used by the affected Proxmox. The only way I could get it back was to stop the VirtualBox machine.