<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Dizzy on Insinuator.net - Bold Statements</title>
    <link>https://insinuator.net/tags/dizzy/</link>
    <description>Recent content in Dizzy on Insinuator.net - Bold Statements</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Wed, 03 Feb 2016 00:00:00 +0000</lastBuildDate>
    <atom:link href="https://insinuator.net/tags/dizzy/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Denial of Service attacks on VoLTE</title>
      <link>https://insinuator.net/2016/02/denial-of-service-attacks-on-volte/</link>
      <pubDate>Wed, 03 Feb 2016 00:00:00 +0000</pubDate>
      <guid>https://insinuator.net/2016/02/denial-of-service-attacks-on-volte/</guid>
      <description>&lt;p&gt;Some weeks ago Hendrik explained in his blogpost &lt;a href=&#34;https://www.insinuator.net/2016/01/security-analysis-of-volte-part-1/&#34;&gt;Security Analysis of VoLTE, Part 1&lt;/a&gt; some attack vectors for Voice over LTE (VoLTE). One attack vector introduced was Denial of Service (DoS), which I also discussed in my Masterthesis “Evaluation of IMS security and Developing penetration tests of IMS”.&lt;/p&gt;&#xA;&lt;p&gt;In general, DoS attacks aim to prevent a system or a network from efficiently providing its service to legitimate users . The impact of such attacks can vary from a big degradation of quality to total blockage. DoS can occur on users level, where a user or a group of users cannot use the service. But the common conception of DoS is on the service level, where the whole service is broken, unstable or totally down. This blog post is about targeting DoS of the whole VoLTE service by attacking IMS.&lt;/p&gt;</description>
    </item>
    <item>
      <title>Fresh Meat From the Coding Front</title>
      <link>https://insinuator.net/2014/02/fresh-meat-from-the-coding-front/</link>
      <pubDate>Thu, 20 Feb 2014 00:00:00 +0000</pubDate>
      <guid>https://insinuator.net/2014/02/fresh-meat-from-the-coding-front/</guid>
      <description>&lt;p&gt;Within the last months I had some time to work on my code and today I’m releasing some of that: a new version of dizzy as well as two new loki modules.&lt;/p&gt;&#xA;&lt;h2 id=&#34;new-version-of-dizzy&#34;&gt;New version of dizzy:&lt;/h2&gt;&#xA;&lt;p&gt;Download version 0.8.2 &lt;a href=&#34;http://c0decafe.de/tools/dizzy-0.8.2.tar.bz2&#34;&gt;here&lt;/a&gt;.&lt;/p&gt;&#xA;&lt;h3 id=&#34;usb-target-support&#34;&gt;USB target support&lt;/h3&gt;&#xA;&lt;p&gt;Dizzy is able to use neighbor travis’ &lt;a href=&#34;http://goodfet.sourceforge.net/hardware/facedancer21/&#34; title=&#34;facedancer&#34;&gt;facedancer&lt;/a&gt; to emulate a client device. Two fuzzing modes are available for USB descriptor fuzzing and USB endpoint fuzzing.&lt;/p&gt;&#xA;&lt;p&gt;Here is an example cmd to start usb configuration descriptor fuzzing:&lt;/p&gt;</description>
    </item>
    <item>
      <title>Fuzzing VMDK files</title>
      <link>https://insinuator.net/2012/05/fuzzing-vmdk-files/</link>
      <pubDate>Wed, 30 May 2012 00:00:00 +0000</pubDate>
      <guid>https://insinuator.net/2012/05/fuzzing-vmdk-files/</guid>
      <description>&lt;p&gt;As announced at last week’s &lt;a href=&#34;http://conference.hitb.org/hitbsecconf2012ams/&#34;&gt;#HITB2012AMS&lt;/a&gt;, I’ll describe the fuzzing steps which were performed during our initial research. The very first step was the definition of the interfaces we wanted to test. We decided to go with the plain text VMDK file, as this is the main virtual disk description file and in most deployment scenarios user controlled, and the data part of a special kind of VMDK files, the &lt;em&gt;Host Sparse Extends&lt;/em&gt;.&lt;/p&gt;</description>
    </item>
    <item>
      <title>Releasing dizzy version 0.6</title>
      <link>https://insinuator.net/2012/05/releasing-dizzy-version-0.6/</link>
      <pubDate>Wed, 23 May 2012 00:00:00 +0000</pubDate>
      <guid>https://insinuator.net/2012/05/releasing-dizzy-version-0.6/</guid>
      <description>&lt;p&gt;Hi @all,&lt;br&gt;&#xA;today im releasing a new version of our famous fuzzing framework, dizzy. The version counts 0.6 by now and youll get some brand new features!&lt;/p&gt;&#xA;&lt;p&gt;see the CHANGELOG:&lt;br&gt;&#xA;v0.6:&lt;br&gt;&#xA;– ssl support&lt;br&gt;&#xA;– server side fuzzing mode&lt;br&gt;&#xA;– command output&lt;br&gt;&#xA;– new dizz funktions: lambda_length, csum, lambda_csum, lambda2_csum&lt;br&gt;&#xA;– recursive mutation mode&lt;br&gt;&#xA;– new dizz objects: fill&lt;br&gt;&#xA;– new interaction objects: null_dizz&lt;br&gt;&#xA;– reconnect option&lt;br&gt;&#xA;– additional fuzzing values&lt;/p&gt;</description>
    </item>
    <item>
      <title>Week of releases – dizzy</title>
      <link>https://insinuator.net/2011/07/week-of-releases-dizzy/</link>
      <pubDate>Tue, 12 Jul 2011 00:00:00 +0000</pubDate>
      <guid>https://insinuator.net/2011/07/week-of-releases-dizzy/</guid>
      <description>&lt;p&gt;I’m proud to announce, today a new fuzzing framework will see the light of day. It’s called &lt;em&gt;dizzy&lt;/em&gt; and was written because the tools we used for fuzzing in past didn’t match our requirements. Some (unique) features are:&lt;/p&gt;&#xA;&lt;ul&gt;&#xA;&lt;li&gt;Python based&lt;/li&gt;&#xA;&lt;li&gt;Fast!&lt;/li&gt;&#xA;&lt;li&gt;Can send to L2 as well as to upper layers (TCP/UDP/SCTP)&lt;/li&gt;&#xA;&lt;li&gt;Ability to work with odd length packet fields (no need to match byte borders, so even single flags or 7bit long fields can be represented and fuzzed)&lt;/li&gt;&#xA;&lt;li&gt;Very easy protocol definition syntax&lt;/li&gt;&#xA;&lt;li&gt;Ability to do multi packet state-full fuzzing with the ability to use received target data in response.&lt;/li&gt;&#xA;&lt;/ul&gt;&#xA;&lt;p&gt;We already had a lot of success using it, now you will be able to know the true promises.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
