<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Birk Kauer on Insinuator.net - Bold Statements</title>
    <link>https://insinuator.net/authors/birk-kauer/</link>
    <description>Recent content in Birk Kauer on Insinuator.net - Bold Statements</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Fri, 13 Nov 2020 00:00:00 +0000</lastBuildDate>
    <atom:link href="https://insinuator.net/authors/birk-kauer/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Forklift &amp;lt;=3.3.9 and &amp;lt;=3.4 Local Privilege Escalations on macOS (CVE-2020-15349/CVE-2020-27192)</title>
      <link>https://insinuator.net/2020/11/forklift-lt3.3.9-and-lt3.4-local-privilege-escalations-on-macos-cve-2020-15349/cve-2020-27192/</link>
      <pubDate>Fri, 13 Nov 2020 00:00:00 +0000</pubDate>
      <guid>https://insinuator.net/2020/11/forklift-lt3.3.9-and-lt3.4-local-privilege-escalations-on-macos-cve-2020-15349/cve-2020-27192/</guid>
      <description>&lt;p&gt;I have started to have a look at my local installed helpers on macOS. These helpers are used as an interface for applications to perform privileged operations on the system. Thus, it is quite a nice attack surface to search for Local Privilege Escalations.&lt;/p&gt;&#xA;&lt;p&gt;Forklift is an advanced dual pane file manager for macOS. It is well known under macOS power users.&lt;/p&gt;&#xA;&lt;p&gt;As part of my investigation I identified vulnerabilities in Forklift allowing local privilege escalation.&lt;/p&gt;</description>
    </item>
    <item>
      <title>macOS Mojave Hardening Guide</title>
      <link>https://insinuator.net/2019/01/macos-mojave-hardening-guide/</link>
      <pubDate>Thu, 10 Jan 2019 00:00:00 +0000</pubDate>
      <guid>https://insinuator.net/2019/01/macos-mojave-hardening-guide/</guid>
      <description>&lt;p&gt;Due to the new release of macOS Mojave in September we updated the El Capitan hardening guide.&lt;/p&gt;&#xA;&lt;p&gt;The hardening guide received a little revamp on some chapters which are now obsolete or had to be changed due to the new features of macOS Mojave. Further, the hardening guide got extended for the new privacy features in macOS Mojave.&lt;/p&gt;&#xA;&lt;p&gt;You can check it out &lt;a href=&#34;https://github.com/ernw/hardening/blob/master/operating_system/osx/10.14/ERNW_Hardening_OS_X_Mojave.md&#34;&gt;here&lt;/a&gt;. We hope some of you might find it helpful.&lt;br&gt;&#xA;Cheers,&lt;br&gt;&#xA;Birk&lt;/p&gt;</description>
    </item>
    <item>
      <title>Spraying arbitrary objects into the non-paged pool</title>
      <link>https://insinuator.net/2018/10/spraying-arbitrary-objects-into-the-non-paged-pool/</link>
      <pubDate>Wed, 03 Oct 2018 00:00:00 +0000</pubDate>
      <guid>https://insinuator.net/2018/10/spraying-arbitrary-objects-into-the-non-paged-pool/</guid>
      <description>&lt;p&gt;Recently, I had some time to play around with HEVD [&lt;a href=&#34;https://github.com/hacksysteam/HackSysExtremeVulnerableDriver&#34;&gt;1&lt;/a&gt;], an extremly vulnerable Windows driver available for 32-bit and 64-bit systems.&lt;/p&gt;&#xA;&lt;p&gt;Since exploits for all vulnerabilities of the 32-bit variant are publically available, I was wondering why this is not the case for the 64-bit version, especially for the pool corruption and UAF vulnerabilities.&lt;/p&gt;&#xA;&lt;p&gt;After digging around a bit, it turned out that the reason is the following. HEVD uses a “special” sized object which is improperly handled such that a Use-After-Free vulnerability arises.&lt;/p&gt;</description>
    </item>
    <item>
      <title>Cloudflare Incident #Cloudbleed</title>
      <link>https://insinuator.net/2017/02/cloudflare-incident-%23cloudbleed/</link>
      <pubDate>Fri, 24 Feb 2017 00:00:00 +0000</pubDate>
      <guid>https://insinuator.net/2017/02/cloudflare-incident-%23cloudbleed/</guid>
      <description>&lt;p&gt;Exactly one week ago I noticed an “urgent” tweet from Tavis Ormandy to get in contact with the Cloudflare team.&lt;br&gt;&#xA;Normally when a tweet like this appears from Tavis, something is horribly broken. Well, today we know the background of this tweet as the &lt;a href=&#34;https://bugs.chromium.org/p/project-zero/issues/detail?id=1139&#34;&gt;bug tracker&lt;/a&gt; issue went public and it exposed quite a bug from Cloudflare.&lt;/p&gt;&#xA;&lt;p&gt;While there is some background story how Tavis found the bug, because he wasn´t actively looking into the Cloudflare infrastructure and it was rather discovered by accident when odd data appeared in his fuzzing corpus. When he looked closely he found data that was not in any mean related to the expected data from various websites.&lt;/p&gt;</description>
    </item>
    <item>
      <title>Insomni’hack pwn50 write-up</title>
      <link>https://insinuator.net/2017/01/insomnihack-pwn50-write-up/</link>
      <pubDate>Tue, 24 Jan 2017 00:00:00 +0000</pubDate>
      <guid>https://insinuator.net/2017/01/insomnihack-pwn50-write-up/</guid>
      <description>&lt;p&gt;Hi all,&lt;/p&gt;&#xA;&lt;p&gt;i´ve looked a bit at the &lt;a href=&#34;https://insomnihack.ch/?page_id=16&#34;&gt;Insomni’hack CTF&lt;/a&gt; which took place on the 21st January and lasted for 36 hours.&lt;br&gt;&#xA;For the sake of warming up a bit for our Troopers workshop &lt;a href=&#34;https://www.troopers.de/events/troopers17/728_windows_and_linux_exploitation/&#34;&gt;Windows and Linux Exploitation&lt;/a&gt;,&lt;br&gt;&#xA;I decided to create a write-up of the first pwn50 challenge.&lt;/p&gt;&#xA;&lt;p&gt;To grab your own copy of the presented files you can also find it in our &lt;a href=&#34;https://github.com/ernw/insinuator-snippets/tree/master/Insomnihack&#34;&gt;Github&lt;/a&gt; repository:&lt;/p&gt;&#xA;&lt;p&gt;When downloading the first binary, we are presented with 2 files:&lt;/p&gt;</description>
    </item>
    <item>
      <title>Day-Con X Recap</title>
      <link>https://insinuator.net/2016/10/day-con-x-recap/</link>
      <pubDate>Thu, 27 Oct 2016 00:00:00 +0000</pubDate>
      <guid>https://insinuator.net/2016/10/day-con-x-recap/</guid>
      <description>&lt;p&gt;Just a few days ago I had the pleasure of visiting &lt;a href=&#34;http://day-con.org/&#34;&gt;Day-Con X&lt;/a&gt;. I listened to some great talks in the closed and public sessions. Since the first day was the security summit (closed session) I will just name a few titles with some brief words.&lt;/p&gt;&#xA;&lt;p&gt;Captivating Security – Safety versus Passion (Josh More):&lt;br&gt;&#xA;Was quite interesting to compare the IT-World with zoos.&lt;/p&gt;&#xA;&lt;p&gt;Beyond Embedded (Brittany Postnikoff):&lt;br&gt;&#xA;Robots are fun soon :).&lt;/p&gt;</description>
    </item>
    <item>
      <title>Black Hat 2016 Summary</title>
      <link>https://insinuator.net/2016/08/black-hat-2016-summary/</link>
      <pubDate>Tue, 09 Aug 2016 00:00:00 +0000</pubDate>
      <guid>https://insinuator.net/2016/08/black-hat-2016-summary/</guid>
      <description>&lt;p&gt;Just a few days ago I had a blast again at this year’s Black Hat. Some of the talks were really worth listening to, so I wanted to point them out and give a short summary.&lt;/p&gt;&#xA;&lt;p&gt; &lt;/p&gt;&#xA;&lt;p&gt;&lt;a href=&#34;https://www.blackhat.com/us-16/briefings.html#using-undocumented-cpu-behavior-to-see-into-kernel-mode-and-break-kaslr-in-the-process&#34;&gt;USING UNDOCUMENTED CPU BEHAVIOR TO SEE INTO KERNEL MODE AND BREAK KASLR IN THE PROCESS&lt;/a&gt; – Anders Fogh &amp;amp; Daniel Gruss&lt;/p&gt;&#xA;&lt;p&gt;They had the last slot at the last day of Black Hat which resulted in a kind of empty room, but in my opinion it was an awesome talk and I even had the pleasure to meet these two guys at our ERNW dinner.&lt;/p&gt;</description>
    </item>
    <item>
      <title>Keynote #1 Troopers 2016</title>
      <link>https://insinuator.net/2016/03/keynote-%231-troopers-2016/</link>
      <pubDate>Thu, 31 Mar 2016 00:00:00 +0000</pubDate>
      <guid>https://insinuator.net/2016/03/keynote-%231-troopers-2016/</guid>
      <description>&lt;p&gt;The first Keynote directly after the Opening by Enno Rey was held by Ben Zevenbergen. At the beginning he pointed out that he is not a very technical guy rather he specialized in Information Law and a policy advisor to the European Parliament. Before he started to dive into his Keynote he talked about some rant story’s which happened to him while trying to make his point clear on previous conferences and that he came in peace to Troopers ;).&lt;/p&gt;</description>
    </item>
    <item>
      <title>Attacking Next-Generation Firewalls</title>
      <link>https://insinuator.net/2016/03/attacking-next-generation-firewalls/</link>
      <pubDate>Mon, 28 Mar 2016 00:00:00 +0000</pubDate>
      <guid>https://insinuator.net/2016/03/attacking-next-generation-firewalls/</guid>
      <description>&lt;p&gt;Felix Wilhelm presented in his talk various ways to attack his new target – The PA-500 which is produced by Palo Alto Networks.&lt;/p&gt;&#xA;&lt;p&gt;He discovered vulnerabilities in 3 different exposed aspects of the device. The first vulnerability occurred inside of an unauthenticated API from the Management-Website which could only be accessed within the Admin Network. This vulnerability was a typical off-by-one Command Injection, which could be abused by reaching out to the API with a special client=wget Request.&lt;/p&gt;</description>
    </item>
    <item>
      <title>Dynamic IDA Enrichment (aka. DIE)</title>
      <link>https://insinuator.net/2016/01/dynamic-ida-enrichment-aka.-die/</link>
      <pubDate>Thu, 28 Jan 2016 00:00:00 +0000</pubDate>
      <guid>https://insinuator.net/2016/01/dynamic-ida-enrichment-aka.-die/</guid>
      <description>&lt;p&gt;Last year on the &lt;a href=&#34;https://hex-rays.com/contests/2015/index.shtml&#34;&gt;Hex-rays plugin Contest&lt;/a&gt; the Dynamic IDA Enrichment (DIE) plugin won first place, so we decided to have a look and play around with it.&lt;/p&gt;&#xA;&lt;p&gt;DIE extends IDA to add Dynamic Data to the static analysis. So after the installation, we are able to perform the static analysis using a lot of supporting information from the actual execution of the binary under assessment.&lt;/p&gt;&#xA;&lt;p&gt;Since DIE is purely written in Python you will need at least Python 2.7 and IDA Versions prior to 6.8 won´t work. In the current version DIE will only work on Windows which will hopefully soon be available cross-platform.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
