Venom – A security vulnerability in virtual floppy drive code

Re:Venom – A security vulnerability in virtual floppy drive ... by rlpb on Wednesday May 13, 2015 @09:24AM (#9538674)

The vulnerability is in floppy drive emulator code. It isn't clear to me whether all users are vulnerable or only hosts that have floppy drive devices defined [in their guests] are vulnerable.

If the latter, perhaps Amazon was never vulnerable anyway?

[ Parent | on HN ]

Re:Venom – A security vulnerability in virtual floppy drive ... by brohee on Wednesday May 13, 2015 @09:27AM (#9538718)

The disclosure states that due to another bug, even floppy less hosts were vulnerable...

[ Parent | on HN ]

Re:Venom – A security vulnerability in virtual floppy drive ... by mhayden on Wednesday May 13, 2015 @09:27AM (#9538715)

The exploit affects VM's whether or not they have a floppy controller or disk attached.

[ Parent | on HN ]

Re:Venom – A security vulnerability in virtual floppy drive ... by duaneb on Wednesday May 13, 2015 @09:37AM (#9538793)

If I were amazon, I would have done an audit of the hyperv software and removed the floppy driver code entirely if unused for precisely this reason. This strikes me as a basic, "no-brainer" hardening step for my billion dollar(s) hosting business.

[ Parent | on HN ]

Re:Venom – A security vulnerability in virtual floppy drive ... by jpgvm on Wednesday May 13, 2015 @09:43AM (#9538834)

They use Xen, not Hyper-V and yes they already remove/replace large portions of Xen.

[ Parent | on HN ]

Re:Venom – A security vulnerability in virtual floppy drive ... by justincormack on Wednesday May 13, 2015 @09:45AM (#9538851)

Their PV domains are not affected anyway. Quite possibly they are running qemu in stub domains for HVM as well, rather than on dom0, but you may well be right about the floppy code too.

[ Parent | on HN ]