3 ms·
Earlier this year: > Our team has been working around-the-clock to find ways to minimize the impact for those requiring a reboot. We're happy to share that we'
by dangrossman 11y ago
Earlier this year:
> Our team has been working around-the-clock to find ways to minimize the impact for those requiring a reboot. We're happy to share that we'll now be able to live-update the vast majority of our older hardware for this Xen Security Advisory.
https://aws.amazon.com/premiumsupport/maintenance-2015-03/ https://aws.amazon.com/premiumsupport/maintenance-2015-03/
There's been a few subsequent articles mentioning Amazon's ability to hot-patch Xen without a reboot. They didn't perform a reboot for this vulnerability.
- samstave 11y agoOut of the 1,000+ instances I had running in AWS during that last major reboot -- there were only a handful of hosts affected. Sadly, some of them were the very primary core DBs -- but in general, it was still only a handful. Luckily, many people also converted to HVM over PV already. IIRC it was largely PV instances in EC2 classic... but I can't be sure.
- sn 11y agoMemories are short. What about VENOM https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2015-3456 https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2015-3456 which affected both Xen HVM and KVM? Then there was http://xenbits.xen.org/xsa/advisory-110.html http://xenbits.xen.org/xsa/advisory-110.html which is privilege escalation in HVM mode. Regardless of the virtualization technology, you need to keep on top of disclosures. Any public provider running xen should be on the disclosure list by now http://www.xenproject.org/security-policy.html http://www.xenproject.org/security-policy.html