News for hackers. Stuff that matters.
Re:Escaping VMware Workstation Through COM1 by ams6110 on Saturday June 20, 2015 @08:53PM (#9751638)
You are absolutely deluded, if not stupid, if you think that a worldwide collection of software engineers who can't write operating systems or applications without security holes, can then turn around and suddenly write virtualization layers without security holes. -- Theo de Raadt
Re:Escaping VMware Workstation Through COM1 by PhantomGremlin on Saturday June 20, 2015 @04:32PM (#9750967)
Virtualization is a great tool for using "well behaved" programs. It's foolhardy to expect it to defend against sophisticated malicious software.

About 40 years ago IBM studied the security of their own VM technology. They found many exploitable bugs, and this was on a codebase that was probably less than 1% the size of VMware. I wrote more about IBM's findings on HN about 3 months ago:

https://news.ycombinator.com/item?id=9241807

Re:Escaping VMware Workstation Through COM1 by cbd1984 on Saturday June 20, 2015 @06:09PM (#9751206)
Remind me: Are modern hypervisors meant to securely contain guests? Because they advertise their presence pretty loudly, and there's nothing which motivates a jail-break like reminding the inmate they're in a cell.
Re:Escaping VMware Workstation Through COM1 by mey on Saturday June 20, 2015 @06:29PM (#9751266)
This is why I'm not a fan of public cloud virtualization for high security systems (PCI-DSS/HIPPA/etc).

In addition to the escapes, you need to contend with side channel timing observation and resource contention.

Re:Escaping VMware Workstation Through COM1 by jimrandomh on Sunday June 21, 2015 @09:45PM (#9755743)
Yes, they are. A common use case of hypervisors is to split up a large server between multiple renters, who demand a hypervisor which won't let other renters hack them.
Re:Escaping VMware Workstation Through COM1 by pimlottc on Saturday June 20, 2015 @04:02PM (#9750887)

    COM1
Man, I haven't even /thought/ about that term in years...
Re:Escaping VMware Workstation Through COM1 by SFjulie1 on Saturday June 20, 2015 @04:40PM (#9750990)
That's not the only place that has poor isolation: clocks, cache, devices ...

virtualization comes with the lie of hardware isolation while devices are views on common peripherals that are isolated at application level by an incorrect abstraction.

jails and virtual machines alike are jails made of a strong but viciously brittling glass.

Re:Escaping VMware Workstation Through COM1 by Rangi42 on Saturday June 20, 2015 @05:54PM (#9751160)
I disable any hardware in VMware guests that I don't need, like printers, speakers, or USB devices, to avoid exploits like this.
Re:Escaping VMware Workstation Through COM1 by wwarren on Monday June 22, 2015 @07:08AM (#9757460)
The VENOM vulnerability that affected the Floppy Drive didn't require that you had it enabled to be exploited: http://news.softpedia.com/news/11-Year-Old-Bug-in-Virtual-Fl...
Re:Escaping VMware Workstation Through COM1 by smegel on Saturday June 20, 2015 @07:31PM (#9751423)
Well I suppose a guest with access the internet could also deploy malware to a website which is then visited by the host computer and downloads a hack that patches vmware to allow full host control from the guest.

Depends on what you mean by "escape".

Re:Escaping VMware Workstation Through COM1 by gnu8 on Sunday June 21, 2015 @12:30AM (#9752183)
Is this a bug in VMware or a bug in Windows?
Re:Escaping VMware Workstation Through COM1 by flyryan on Sunday June 21, 2015 @01:27AM (#9752314)
VMWare. It takes advantage of the fact that VMWare links guest VMs to the host's printers by default and takes advantage of that link. The patch from VMWare even applied to VMWare Fusion even though there hasn't been anything published on getting this to work in OSX.
Re:Escaping VMware Workstation Through COM1 by simcop2387 on Saturday June 20, 2015 @03:30PM (#9750809)
Anyone know why some of the images are incredibly low resolution?
Re:Escaping VMware Workstation Through COM1 by miander on Saturday June 20, 2015 @03:36PM (#9750823)
If you look at the non-mobile version at https://docs.google.com/document/d/1sIYgqrytPK-CFWfqDntraA_F... you'll see that the images have been resized to the width of the page, probably from much larger images, causing the text to be very small and fuzzy.