<node id="469931">
  <nid>469931</nid>
  <type>event</type>
  <uid>
    <user id="27707"><![CDATA[27707]]></user>
  </uid>
  <created>1447660710</created>
  <changed>1475892890</changed>
  <title><![CDATA[MS Defense by  Kevin Flansburg]]></title>
  <body><![CDATA[<p>Hello, I would like to announce my masters thesis defense.&nbsp;</p><p>&nbsp;</p><p><strong>Name:</strong></p><p><strong>&nbsp; &nbsp; Kevin Flansburg</strong></p><p>Advisor:</p><p>&nbsp; &nbsp; Taesoo Kim</p><p>Committee Members:</p><p>&nbsp; &nbsp; Polo Chau</p><p>&nbsp; &nbsp; Manos Antonakakis</p><p>Date and Time:</p><p>&nbsp; &nbsp; November 23, 2015 11:00 AM</p><p>Location:</p><p>&nbsp; &nbsp; Klaus 3100</p><p>Title:</p><p>&nbsp;<strong> &nbsp;&nbsp;A Framework for Reproducible Exploit Testing Environments</strong></p><p>Abstract:</p><p></p><p><br />To demonstrate working exploits or vulnerabilities, people often share<br />their findings as a form of proof-of-concept (PoC) prototype. Such<br />practices are particularly useful to learn about real vulnerabilities<br />and state-of-the-art exploitation techniques.&nbsp; Unfortunately, the shared<br />PoC exploits are seldom reproducible; in part because they are often not<br />thoroughly tested, but largely because authors lack a formal way to<br />specify the tested environment or its dependencies.&nbsp; Although exploit<br />writers attempt to overcome such problems by describing their<br />dependencies or testing environments using comments, this informal way<br />of sharing PoC exploits makes it hard for exploit authors to achieve the<br />original goal of demonstration.&nbsp; More seriously, these non- or<br />hard-to-reproduce PoC exploits have limited potential to be utilized for<br />other useful research purposes such as penetration testing, or in<br />benchmark suites to evaluate defense mechanisms.</p><p></p><p>In this paper, we present XShop, a framework and infrastructure to<br />describe environments and dependencies for exploits in a formal way, and<br />to automatically resolve these constraints and construct an isolated<br />environment for development, testing, and to share with the community.<br />We show how XShop's flexible design enables new possibilities for<br />utilizing these reproducible exploits in five practical use cases: as a<br />security benchmark suite, in pen-testing, for large scale vulnerability<br />analysis, as a shared development environment, and for regression<br />testing. We design and implement such applications by extending the<br />XShop framework and demonstrate its effectiveness with twelve real<br />exploits against well-known bugs that include GHOST, Shellshock, and<br />Heartbleed.&nbsp; We believe that the proposed practice not only brings<br />immediate incentives to exploit authors but also has the potential to be<br />grown as a community-wide knowledge base.</p><p></p><p>&nbsp;</p><p><br /></p><p> </p>]]></body>
  <field_summary_sentence>
    <item>
      <value><![CDATA[A Framework for Reproducible Exploit Testing Environments]]></value>
    </item>
  </field_summary_sentence>
  <field_summary>
    <item>
      <value><![CDATA[]]></value>
    </item>
  </field_summary>
  <field_time>
    <item>
      <value><![CDATA[2015-11-23T15:00:00-05:00]]></value>
      <value2><![CDATA[2015-11-23T17:00:00-05:00]]></value2>
      <rrule><![CDATA[]]></rrule>
      <timezone><![CDATA[America/New_York]]></timezone>
    </item>
  </field_time>
  <field_fee>
    <item>
      <value><![CDATA[]]></value>
    </item>
  </field_fee>
  <field_extras>
      </field_extras>
  <field_audience>
          <item>
        <value><![CDATA[Public]]></value>
      </item>
      </field_audience>
  <field_media>
      </field_media>
  <field_contact>
    <item>
      <value><![CDATA[]]></value>
    </item>
  </field_contact>
  <field_location>
    <item>
      <value><![CDATA[]]></value>
    </item>
  </field_location>
  <field_sidebar>
    <item>
      <value><![CDATA[]]></value>
    </item>
  </field_sidebar>
  <field_phone>
    <item>
      <value><![CDATA[]]></value>
    </item>
  </field_phone>
  <field_url>
    <item>
      <url><![CDATA[]]></url>
      <title><![CDATA[]]></title>
            <attributes><![CDATA[]]></attributes>
    </item>
  </field_url>
  <field_email>
    <item>
      <email><![CDATA[]]></email>
    </item>
  </field_email>
  <field_boilerplate>
    <item>
      <nid><![CDATA[]]></nid>
    </item>
  </field_boilerplate>
  <links_related>
      </links_related>
  <files>
      </files>
  <og_groups>
          <item>221981</item>
      </og_groups>
  <og_groups_both>
          <item><![CDATA[Graduate Studies]]></item>
      </og_groups_both>
  <field_categories>
          <item>
        <tid>1788</tid>
        <value><![CDATA[Other/Miscellaneous]]></value>
      </item>
      </field_categories>
  <field_keywords>
          <item>
        <tid>111531</tid>
        <value><![CDATA[ms defense]]></value>
      </item>
      </field_keywords>
  <field_userdata><![CDATA[]]></field_userdata>
</node>
