Oh no, you're thinking, yet another cookie pop-up. Well, sorry, it's the law. We measure how many people read us, and ensure you see relevant ads, by storing cookies on your device. If you're cool with that, hit “Accept all Cookies”. For more info and to customize your settings, hit “Customize Settings”.

Review and manage your consent

Here's an overview of our use of cookies, similar technologies and how to manage them. You can also change your choices at any time, by hitting the “Your Consent Options” link on the site's footer.

Manage Cookie Preferences
  • These cookies are strictly necessary so that you can navigate the site as normal and use all features. Without these cookies we cannot provide you with the service that you expect.

  • These cookies are used to make advertising messages more relevant to you. They perform functions like preventing the same ad from continuously reappearing, ensuring that ads are properly displayed for advertisers, and in some cases selecting advertisements that are based on your interests.

  • These cookies collect information in aggregate form to help us understand how our websites are being used. They allow us to count visits and traffic sources so that we can measure and improve the performance of our sites. If people say no to these cookies, we do not know how many people have visited and we cannot monitor performance.

See also our Cookie policy and Privacy policy.

This article is more than 1 year old

Xen forgets recent patches in new maintenance release

Is this any way to run a supposedly cloud-grade hypervisor?

The Xen Project has announced a new maintenance release for version 4.6.1 of its hypervisor, but along the way has admitted it forgot to add some recent patches.

“Note that …. due to two oversights the fixes for both XSA-155 and XSA-162 have only been partially applied to this release,” says the announcement of the maintenance release. The mess also applies to the recent version 4.4.4 release, the last update to the Xen 4.4.

Forgetting to add the patches is kind of a big deal, because XSA-155 has a chance of allowing “arbitrary code execution in backend” and XSA-162 allows a guest to enjoy the privileges of the Qemu process.

The accidental omission is also notable because it's the second security SNAFU in two months: last December the Xen Project ignored its own bug publishing policy and announced a bug to the world without the usual two-week embargo. That policy is designed to ensure that cloud operators using the hypervisor – notably Amazon Web Services – have time to patch bugs before they're universally known. It's thought that publicly announcing Xen bugs would have the effect of turning the millions of VMs in clouds into instant hacker honeypots.

Plenty of Xen users will diligently apply patches as they land, so the missing fixes won't be an issue. But the omission will be a trap for the unwary who make less frequent upgrades, or those installing the software for the first time. If they dare, given the project's stumbles. ®

 

Similar topics

Similar topics

Similar topics

TIP US OFF

Send us news


Other stories you might like