<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>XEN on Insinuator.net - Bold Statements</title>
    <link>https://insinuator.net/tags/xen/</link>
    <description>Recent content in XEN on Insinuator.net - Bold Statements</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Thu, 17 Dec 2015 00:00:00 +0000</lastBuildDate>
    <atom:link href="https://insinuator.net/tags/xen/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Xen XSA 155: Double fetches in paravirtualized devices</title>
      <link>https://insinuator.net/2015/12/xen-xsa-155-double-fetches-in-paravirtualized-devices/</link>
      <pubDate>Thu, 17 Dec 2015 00:00:00 +0000</pubDate>
      <guid>https://insinuator.net/2015/12/xen-xsa-155-double-fetches-in-paravirtualized-devices/</guid>
      <description>&lt;p&gt;As part of my research on the security of paravirtualized devices, I reported a number of vulnerabilities to the Xen security team, which were patched &lt;a href=&#34;http://xenbits.xen.org/xsa/advisory-155.html&#34;&gt;today&lt;/a&gt;. All of them are double fetch vulnerabilities affecting the different backend components used for paravirtualized devices. While the severity and impact of these bugs varies heavily and is dependent on a lot of external factors, I would recommend patching them as soon as possible. In the rest of this blog post I’ll give a short teaser about my research with full details coming out in the first quarter of 2016 .&lt;/p&gt;</description>
    </item>
    <item>
      <title>Revisiting Xen’s x86 Emulation: Xen XSA 123</title>
      <link>https://insinuator.net/2015/03/revisiting-xens-x86-emulation-xen-xsa-123/</link>
      <pubDate>Tue, 10 Mar 2015 00:00:00 +0000</pubDate>
      <guid>https://insinuator.net/2015/03/revisiting-xens-x86-emulation-xen-xsa-123/</guid>
      <description>&lt;p&gt;In my &lt;a href=&#34;http://www.insinuator.net/2015/02/the-dangers-of-x86-emulation-xen-xsa-110-and-105/&#34; title=&#34;The Dangers of x86 Emulation: Xen XSA 110 and 105&#34;&gt;last blog post&lt;/a&gt;, I gave an overview about recent vulnerabilities discovered in the x86 emulation layer of Xen. While both of the discussed vulnerabilities only allow for guest privilege escalation, the complexity of the involved code seemed to indicate that even more interesting bugs could be discovered. So I spent some time searching for memory corruption issues and discovered a very interesting bug that resulted in &lt;a href=&#34;http://xenbits.xen.org/xsa/advisory-123.html&#34;&gt;XSA 123&lt;/a&gt; . This post gives an overview about the root cause of the bug and a short description of exploitation challenges. A follow-up post will describe possible exploitation strategies in more detail.&lt;/p&gt;</description>
    </item>
    <item>
      <title>The Dangers of x86 Emulation: Xen XSA 110 and 105</title>
      <link>https://insinuator.net/2015/02/the-dangers-of-x86-emulation-xen-xsa-110-and-105/</link>
      <pubDate>Mon, 23 Feb 2015 00:00:00 +0000</pubDate>
      <guid>https://insinuator.net/2015/02/the-dangers-of-x86-emulation-xen-xsa-110-and-105/</guid>
      <description>&lt;p&gt;&lt;img src=&#34;http://www.insinuator.net/wp-content/uploads/2015/02/xen-300x81.png&#34; alt=&#34;Xen Logo&#34;&gt;&lt;/p&gt;&#xA;&lt;p&gt;Developing a secure and feature rich hypervisor is no easy task. Recently, the open source Xen hypervisor was affected by two interesting vulnerabilities involving its x86 emulation code: &lt;a href=&#34;http://xenbits.xen.org/xsa/advisory-110.html&#34;&gt;XSA 110&lt;/a&gt; and &lt;a href=&#34;http://xenbits.xen.org/xsa/advisory-105.html&#34;&gt;XSA 105&lt;/a&gt;. Both bugs show that the attack surface of hypervisors is often larger than expected. XSA 105 was &lt;a href=&#34;//labs.bitdefender.com/wp-content/uploads/downloads/2014/10/Gaining-kernel-privileges-using-the-Xen-emulator.pdf&#34;&gt;originally reported&lt;/a&gt;) by Andrei Lutas from BitDefender. The patch adds missing privilege checks to the emulation routines of several critical system instructions including LGDT and LIDT. The vulnerable code can be reached from unprivileged user code running inside hardware virtual machine (HVM) guests and can be used to escalate guest privileges. XSA 110 was reported by Jan Beulich from SUSE and concerns insufficient checks when emulating long jumps, calls or returns.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
