<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Burp on Insinuator.net - Bold Statements</title>
    <link>https://insinuator.net/tags/burp/</link>
    <description>Recent content in Burp on Insinuator.net - Bold Statements</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Mon, 06 Jun 2016 00:00:00 +0000</lastBuildDate>
    <atom:link href="https://insinuator.net/tags/burp/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>SAMLReQuest Burpsuite Extention</title>
      <link>https://insinuator.net/2016/06/samlrequest-burpsuite-extention/</link>
      <pubDate>Mon, 06 Jun 2016 00:00:00 +0000</pubDate>
      <guid>https://insinuator.net/2016/06/samlrequest-burpsuite-extention/</guid>
      <description>&lt;p&gt;Security Assertion Markup Language (SAML) is an XML standard for exchanging authentication and authorization data between a Service Provider (SP) and an  Identification Provider (IdP). SAML is used in many Single Sign-On (SSO) implementations, when a user is authenticated once by IdP to access multiple related SPs. When a user requests to access a SP, it creates a SAML Authentication Request and redirects the user to IdP to be authenticated according to this authentication request. If the user is successfully authenticated, IdP creates a SAML authentication response and sends it back to SP through the user’s browser.&lt;/p&gt;</description>
    </item>
    <item>
      <title>Getting 20k Inline-QR-Codes out of Burp</title>
      <link>https://insinuator.net/2014/12/getting-20k-inline-qr-codes-out-of-burp/</link>
      <pubDate>Fri, 19 Dec 2014 00:00:00 +0000</pubDate>
      <guid>https://insinuator.net/2014/12/getting-20k-inline-qr-codes-out-of-burp/</guid>
      <description>&lt;p&gt;Lately we had to analyze QR-Codes in a pentest. Those held some random data which was used as a token for login and we wanted to know if that data was really random.&lt;/p&gt;&#xA;&lt;p&gt;If you ever worked with the Burp Suite you may know the Burp Sequencer, which offers some statistical analysis regarding the randomness of tokens which appear in requests (you just have to tell Burp what or where the token is). In our case the QR-Code was delivered as an inline-image in HTML to the browser, like this:&lt;/p&gt;</description>
    </item>
    <item>
      <title>ERNW’s Top 9 Burp Plugins</title>
      <link>https://insinuator.net/2014/08/ernws-top-9-burp-plugins/</link>
      <pubDate>Mon, 25 Aug 2014 00:00:00 +0000</pubDate>
      <guid>https://insinuator.net/2014/08/ernws-top-9-burp-plugins/</guid>
      <description>&lt;p&gt;In the context of an internal evaluation, we recently had a look at most of the burp plugins available from the BApp store. The following overview represents our personal top 9 plugins, categorized in “Scanner Extensions”, “Manual Testing” and “Misc” in alphabetic order:&lt;/p&gt;&#xA;&lt;p&gt;&lt;strong&gt;Scanner Extensions&lt;/strong&gt;&lt;/p&gt;&#xA;&lt;p&gt;ActiveScan++&lt;/p&gt;&#xA;&lt;p&gt;This plugin adds some tests for Dynamic code injection, &lt;a href=&#34;http://carlos.bueno.org/2008/06/host-header-injection.html&#34; title=&#34;Host header attacks&#34;&gt;Host header attacks&lt;/a&gt; (&lt;a href=&#34;http://www.skeletonscribe.net/2013/05/practical-http-host-header-attacks.html&#34; title=&#34;Password reset poisoning&#34;&gt;password reset poisoning&lt;/a&gt;, &lt;a href=&#34;https://www.owasp.org/index.php/Cache_Poisoning&#34; title=&#34;cache poisoning&#34;&gt;cache poisoning&lt;/a&gt;, DNS rebinding), OS command injection and &lt;a href=&#34;http://www.thespanner.co.uk/2014/03/21/rpo/&#34; title=&#34;Relative path overwrite&#34;&gt;Relative path overwrite&lt;/a&gt;. In some internal tests, it seemed to deliver what it promises.&lt;/p&gt;</description>
    </item>
    <item>
      <title>Python Library for De- and Encoding of WCF-Binary streams</title>
      <link>https://insinuator.net/2011/12/python-library-for-de-and-encoding-of-wcf-binary-streams/</link>
      <pubDate>Fri, 23 Dec 2011 00:00:00 +0000</pubDate>
      <guid>https://insinuator.net/2011/12/python-library-for-de-and-encoding-of-wcf-binary-streams/</guid>
      <description>&lt;p&gt;In a .NET environment WCF services can use the proprietary WCF binary XML protocol described &lt;a href=&#34;https://blogs.msdn.com/b/drnick/archive/2009/09/11/binary-encoding-part-4.aspx&#34;&gt;here&lt;/a&gt;. Microsoft uses this protocol to save some time parsing the transmitted XML data. If you have to (pen-) test such services, it would be nice to read (and modify) the communication between (for example) clients and servers. One possibility is &lt;a href=&#34;http://www.fiddler2.com&#34;&gt;Fiddler&lt;/a&gt;.&lt;/p&gt;&#xA;&lt;p&gt;Fiddler’s strengths include its extensibility and its WCF binary plugins. Sadly, these plugins can only decode and display the binary content as XML text.&lt;/p&gt;</description>
    </item>
    <item>
      <title>Use Python for Burp plugins with pyBurp</title>
      <link>https://insinuator.net/2011/12/use-python-for-burp-plugins-with-pyburp/</link>
      <pubDate>Fri, 23 Dec 2011 00:00:00 +0000</pubDate>
      <guid>https://insinuator.net/2011/12/use-python-for-burp-plugins-with-pyburp/</guid>
      <description>&lt;p&gt;One of our favorite tools for conducting penetration tests (especially, but not only, web application tests) is Portswiggers’s &lt;a href=&#34;http://portswigger.net/burp/&#34; title=&#34;Burp Suite&#34;&gt;Burp Suite.&lt;/a&gt; Burp allows to extend its features by writing own plugins. But because Burp is written in Java, it only supports Java classes as plugins. Additionally, Burp only allows to use one plugin at the same time which has to be loaded on start-up.&lt;/p&gt;&#xA;&lt;p&gt;Now we have written a Burp-Python proxy (called &lt;strong&gt;pyBurp&lt;/strong&gt;) which adds some features to the plugin system:&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
