Xen Security Issue Patched 41
An anonymous reader sends in word of a privilege escalation security issue identified in the open source Xen hypervisor. Xen has issued a hotfix and urged all users to install it. The problem was disclosed by Secunia last week. A user of a guest domain with root privileges could execute arbitrary commands in domain 0 via specially crafted entries in grub.conf when the guest system is booted.
Already fixed in some distributions (Score:3, Informative)
https://rhn.redhat.com/errata/RHSA-2007-0323.html [redhat.com]
CentOS already carries this fix too.
Re: (Score:1)
Re: (Score:3, Insightful)
Re: (Score:2)
Re: (Score:2)
Re: (Score:1)
No. When the Debian Xen packages are installed no guests are created.
For pygrub to be used you must have it explicitly enabled in the configuration files for the Xen guest, located beneath /etc/xen.
It will only be used if you've manually created a new Xen guest and chosen to use pygrub. Many (most?) Debian users create their new Xen guests via my xen-tools [xen-tools.org] software and that doesn't even support pygrub setups at the moment...
If you see no mention of pygrub in /etc/xen/* then you're almost certainly saf
Re: (Score:2)
The summary in Haiku (Score:1)
and then it was fixed
slow news day
Re:Oughtta teach 'em (Score:4, Informative)
In an environment where you can't directly mess with physical memory, you can't really have a bootloader, since a bootloader pulls data from the disk (the kernel, initrd, etc.), using either some BIOS calls or direct hardware access (which will be limited to whatever the bootloader knows how to deal with), places that data in memory, and jumps into it. This sounds like a possible disadvantage, but it has the possible benefit of not requiring anyone to mess with setting up real-/protected-mode, dealing with funky BIOS issues (which may differ among different PC models), and having to use BIOS calls to set up the environment before the real kernel boot.
In the Xen-VM world, hardware access is abstracted, and the kernel and other necessary code is already loaded for the guest VM, by the host OS.
Someone correct me if I'm wrong about this (especially the first part about physical memory access)... I can't find the documentation at the moment.
Use emulation? (Score:2)
Then switch to "native" once you hit the kernel stuff etc.
Probably a lot more work tho.
Re: (Score:2)
VMware does not do any CPU emulatation at all. The physical CPU underlying it is visible to any guest, including all of the CPU's capabilities (i.e. MMX, SSE, etc). VMware is acts as scheduler for the CPU, each of the guest VM's are merely programs running inside VMware. VMware additionally does emulate particular pieces of the hardware: bios, motherboard, NIC, cdro
Re: (Score:1)
I believe that recent versions of VMWare and Xen support the virtualisation features of the latest Intel and AMD CPUs so they can run un
Xen rooted (Score:2, Funny)
Xen and the art of powercycle maintenance.
Goodbye Gordan! (Score:1, Funny)
Have there been many issues with ESX? (Score:1)
The XenSource code base (well, some of it at least) is Open. Its competitor, ESX from VMware, isn't. Philosophy aside, how has ESX been doing on the security front?
Re: (Score:3, Informative)
Re: (Score:2)
What if virtual machine uses Plan9 and attack is initiated from remote machine across the network, would that count as remote hole? :) I'm not sure if that's even possible though...
Re: (Score:2)
Re: (Score:2)
but but yesterday... (Score:1)
Now that that pdf from both Xen and VMWare read like someone trying hard to sell a product is another thing.
Wow, that's amazing! (Score:2)
That's amazing. Chalk another victory up for the pocket-protector crowd. Is there anything they can't do?
xensource.com uses IIS - How lame! (Score:1)
Server Microsoft-IIS/6.0
X-Powered-By ASP.NET
Re: (Score:2)
BLACK MESA CORPORATE EMAIL (Score:1)
Customer of mine... (Score:5, Informative)
As a plus point, I let them boot their own kernels (I trust my custommers). Next thing I know, he tells me to check my
Oh don't bother to check out my business' website, it's not translated yet in English... (I'm Dutch).
why would a domU have grub anyway? (Score:3, Interesting)
Its only an HVM domU that would need a boot loader and its own kernel.
I've read through TFA and the Xen mailing list and I can't see anything that says whether this affects both paravirtualised *and* HVM or just one or the other...?
In the case of paravirtualised, why on earth would the creating the domU even *look* for a
Re: (Score:2)
Re: (Score:2)
And so dom0 gets to run a script against content in a file in domU...
My God thats just insane and is *asking* for trouble!!!
What *moron* thought this would be a Good Idea???
...words..stuff... (Score:1, Insightful)
Seriously, guys, Star Trek:TNG is off the air. You can stop writing like this now.
Avoid PyGrub and everything is fine (Score:2, Interesting)
I run my Xen DomU's with a single virtual disk per filesystem, no partition tables (the DomU mounts