<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Oliver Matula on Insinuator.net - Bold Statements</title>
    <link>https://insinuator.net/authors/oliver-matula/</link>
    <description>Recent content in Oliver Matula on Insinuator.net - Bold Statements</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Thu, 24 Mar 2022 00:00:00 +0000</lastBuildDate>
    <atom:link href="https://insinuator.net/authors/oliver-matula/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>A Tale of an OFTP2 Vulnerability</title>
      <link>https://insinuator.net/2022/03/a-tale-of-an-oftp2-vulnerability/</link>
      <pubDate>Thu, 24 Mar 2022 00:00:00 +0000</pubDate>
      <guid>https://insinuator.net/2022/03/a-tale-of-an-oftp2-vulnerability/</guid>
      <description>&lt;p&gt;This is a guest post from Thomas Smits.&lt;/p&gt;&#xA;&lt;h2 id=&#34;a-long-time-ago-in-a-galaxy-far-far-away&#34;&gt;A long time ago in a galaxy far, far away….&lt;/h2&gt;&#xA;&lt;p&gt;In my ordinary life, I teach computer science at the University of Applied&#xA;Sciences in Mannheim but for some months, I was an intern at ERNW learning a lot&#xA;about IT security and penetration testing. One of these learnings is that old&#xA;protocols can be fun and breaking them even more. But let’s start at the&#xA;beginning of the story…&lt;/p&gt;</description>
    </item>
    <item>
      <title>XSS Vulnerability in Froala WYSIWYG HTML Editor</title>
      <link>https://insinuator.net/2020/11/xss-vulnerability-in-froala-wysiwyg-html-editor/</link>
      <pubDate>Wed, 18 Nov 2020 00:00:00 +0000</pubDate>
      <guid>https://insinuator.net/2020/11/xss-vulnerability-in-froala-wysiwyg-html-editor/</guid>
      <description>&lt;p&gt;Recently, I had a brief look at the Froala WYSIWYG HTML Editor (v3.2.0) as there was a &lt;a href=&#34;https://www.mail-archive.com/fulldisclosure@seclists.org/msg06788.html&#34;&gt;post&lt;/a&gt; about it on the Full Disclosure mailing list.&lt;/p&gt;&#xA;&lt;p&gt;When targeting a HTML Editor, I guess one of the first things that everybody does is to check for XSS vulnerabilities. So I tried the usual XSS payloads (a great resource for XSS payloads is the &lt;a href=&#34;https://portswigger.net/web-security/cross-site-scripting/cheat-sheet&#34;&gt;XSS cheat sheet&lt;/a&gt; by PortSwigger) within the editor’s code view, but did not have much luck with the common payloads as they were filtered. However, using the HTML object tag, it was possible to trigger an XSS.&lt;/p&gt;</description>
    </item>
    <item>
      <title>OpenSIS Vulnerabilities</title>
      <link>https://insinuator.net/2020/10/opensis-vulnerabilities/</link>
      <pubDate>Thu, 15 Oct 2020 00:00:00 +0000</pubDate>
      <guid>https://insinuator.net/2020/10/opensis-vulnerabilities/</guid>
      <description>&lt;p&gt;&lt;a href=&#34;https://opensis.com/&#34;&gt;OpenSIS&lt;/a&gt; is an open source student information system. Recently, it was affected by several vulnerabilities such as SQL injections, local file inclusions and incorrect access controls (&lt;a href=&#34;https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-13380&#34;&gt;CVE-2020-13380&lt;/a&gt;, &lt;a href=&#34;https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-13381&#34;&gt;CVE-2020-13381&lt;/a&gt;, &lt;a href=&#34;https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-13382&#34;&gt;CVE-2020-13382&lt;/a&gt;, &lt;a href=&#34;https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-13383&#34;&gt;CVE-2020-13383&lt;/a&gt;). That is why I got interested and also had a quick look at the application.&lt;/p&gt;&#xA;&lt;p&gt;As part of this investigation, I discovered two vulnerabilities, an XSS vulnerability (CVE-2020-27409) in the file SideForStudent.php that got quickly fixed after being reported (see commit &lt;a href=&#34;https://github.com/OS4ED/openSIS-Responsive-Design/commit/edca0855e7bc27d5b28dcb2d16f057ada865e282&#34;&gt;edca085&lt;/a&gt; for the details; the commit is included in release v7.5) and some incorrect (i.e. non-existent) access controls for the password change functionality (CVE-2020-27408). In this blog post, I would like to focus on the second vulnerability and describe the tedious disclosure process that – in the end – lead to nothing but the implementation of some ineffective obfuscation mechanism.&lt;/p&gt;</description>
    </item>
    <item>
      <title>QEMU, Unicorn, Zelos, and AFL</title>
      <link>https://insinuator.net/2020/07/qemu-unicorn-zelos-and-afl/</link>
      <pubDate>Wed, 15 Jul 2020 00:00:00 +0000</pubDate>
      <guid>https://insinuator.net/2020/07/qemu-unicorn-zelos-and-afl/</guid>
      <description>&lt;p&gt;I should start by telling you that this post does not contain anything fundamentally new. Hence, if you already know the tools mentioned in the title, this post may probably not be for you. However, if you are not too familiar with these tools and want to understand a little bit more on how they work together, you should keep on reading.&lt;/p&gt;&#xA;&lt;p&gt;First, let us get a high-level overview of the different tools. We begin with QEMU. &lt;a href=&#34;https://www.qemu.org/&#34;&gt;QEMU&lt;/a&gt; is a piece of software to emulate hardware such as processors. Imagine, for example, that you are running an operating system such as Linux or Windows on a x86-64 machine and that you would like to analyze a binary that has been compiled for an ARM or MIPS processor. Of course, you can use static analysis on the binary, but if you want to find out more about the runtime behavior, well, it would be good to have a corresponding runtime environment.&lt;/p&gt;</description>
    </item>
    <item>
      <title>How to break out of restricted shells with tcpdump</title>
      <link>https://insinuator.net/2019/07/how-to-break-out-of-restricted-shells-with-tcpdump/</link>
      <pubDate>Mon, 29 Jul 2019 00:00:00 +0000</pubDate>
      <guid>https://insinuator.net/2019/07/how-to-break-out-of-restricted-shells-with-tcpdump/</guid>
      <description>&lt;p&gt;During security assessments we sometimes obtain access to a restricted shell on a target system. To advance further and gain complete control of the system, the next step is usually to break out of this shell. If the restricted shell provides access to certain system binaries, these binaries can often be exploited to perform such a break out. Here we would like to show an interesting example of such a break out by using the tcpdump binary.&lt;/p&gt;</description>
    </item>
    <item>
      <title>Security Advisories for Cisco ACI</title>
      <link>https://insinuator.net/2019/07/security-advisories-for-cisco-aci/</link>
      <pubDate>Thu, 04 Jul 2019 00:00:00 +0000</pubDate>
      <guid>https://insinuator.net/2019/07/security-advisories-for-cisco-aci/</guid>
      <description>&lt;p&gt;Again, Cisco released security advisories for their software-defined networking (SDN) solution called Application Centric Infrastructure (ACI). As before (see blog post &lt;a href=&#34;https://insinuator.net/2019/05/security-advisory-for-cisco-nexus-9000-series-fabric-switches-in-aci-mode/&#34;&gt;here&lt;/a&gt;), the published advisories originated from research performed in our ACI lab.&lt;/p&gt;&#xA;&lt;p&gt;The following advisories have been published:&lt;/p&gt;&#xA;&lt;p&gt;Cisco Nexus 9000 Series Fabric Switches ACI Mode Fabric Infrastructure VLAN Unauthorized Access Vulnerability&lt;br&gt;&#xA;&lt;a href=&#34;https://tools.cisco.com/security/center/content/CiscoSecurityAdvisory/cisco-sa-20190703-n9kaci-bypass&#34;&gt;https://tools.cisco.com/security/center/content/CiscoSecurityAdvisory/cisco-sa-20190703-n9kaci-bypass&lt;/a&gt;&lt;br&gt;&#xA;CVSS Base Score: 7.4&lt;/p&gt;&#xA;&lt;p&gt;Cisco Application Policy Infrastructure Controller REST API Privilege Escalation Vulnerability&lt;br&gt;&#xA;&lt;a href=&#34;https://tools.cisco.com/security/center/content/CiscoSecurityAdvisory/cisco-sa-20190703-ccapic-restapi&#34;&gt;https://tools.cisco.com/security/center/content/CiscoSecurityAdvisory/cisco-sa-20190703-ccapic-restapi&lt;/a&gt;&lt;br&gt;&#xA;CVSS Base Score: 7.2&lt;/p&gt;</description>
    </item>
    <item>
      <title>Security Advisory for Cisco Nexus 9000 Series Fabric Switches in ACI mode</title>
      <link>https://insinuator.net/2019/05/security-advisory-for-cisco-nexus-9000-series-fabric-switches-in-aci-mode/</link>
      <pubDate>Thu, 02 May 2019 00:00:00 +0000</pubDate>
      <guid>https://insinuator.net/2019/05/security-advisory-for-cisco-nexus-9000-series-fabric-switches-in-aci-mode/</guid>
      <description>&lt;p&gt;Yesterday, Cisco released a number of security advisories. Three of the advisories originated from research performed by us for the Cisco Nexus 9000 Series Fabric Switches / Cisco Application Centric Infrastructure (ACI).&lt;/p&gt;&#xA;&lt;p&gt;More specifically, these advisories are the following:&lt;/p&gt;&#xA;&lt;p&gt;Cisco Nexus 9000 Series Fabric Switches Application Centric Infrastructure Mode Default SSH Key Vulnerability&lt;br&gt;&#xA;&lt;a href=&#34;https://tools.cisco.com/security/center/content/CiscoSecurityAdvisory/cisco-sa-20190501-nexus9k-sshkey&#34;&gt;https://tools.cisco.com/security/center/content/CiscoSecurityAdvisory/cisco-sa-20190501-nexus9k-sshkey&lt;/a&gt;&lt;br&gt;&#xA;CVSS Base Score: 9.8&lt;/p&gt;&#xA;&lt;p&gt;Cisco Nexus 9000 Series Fabric Switches Application Centric Infrastructure Mode Root Privilege Escalation Vulnerability&lt;br&gt;&#xA;&lt;a href=&#34;https://tools.cisco.com/security/center/content/CiscoSecurityAdvisory/cisco-sa-20190501-nexus9k-rpe&#34;&gt;https://tools.cisco.com/security/center/content/CiscoSecurityAdvisory/cisco-sa-20190501-nexus9k-rpe&lt;/a&gt;&lt;br&gt;&#xA;CVSS Base Score: 7.8&lt;/p&gt;</description>
    </item>
    <item>
      <title>TROOPERS19 Training Teaser: Windows &amp;amp; Linux Binary Exploitation</title>
      <link>https://insinuator.net/2019/01/troopers19-training-teaser-windows-amp-linux-binary-exploitation/</link>
      <pubDate>Mon, 14 Jan 2019 00:00:00 +0000</pubDate>
      <guid>https://insinuator.net/2019/01/troopers19-training-teaser-windows-amp-linux-binary-exploitation/</guid>
      <description>&lt;p&gt;Once again Troopers will have its Windows &amp;amp; Linux Binary Exploitation workshop. Its main focus are the ever-present stack-based buffer overflows still found in software today (e.g. CVE-2018-5002, CVE-2018-1459, and CVE-2018-12897) and their differences with regard to exploitation on Windows and Linux systems. If you ever wanted to know the details of the exploit development process for these systems then this workshop is for you.&lt;/p&gt;&#xA;&lt;p&gt;After initial exercises involving the exploitation of classic stack-based buffer overflows, modern defense mechanism such as Stack Cookies, DEP, and ASLR are presented and analyzed for weaknesses. The participants will learn how these defense mechanisms can be bypassed and will develop exploits targeting real world applications such as the Foxit Reader Plugin for Firefox, Wireshark, and nginx.&lt;/p&gt;</description>
    </item>
    <item>
      <title>Security Advisory for VMware vRealize Automation Center</title>
      <link>https://insinuator.net/2018/04/security-advisory-for-vmware-vrealize-automation-center/</link>
      <pubDate>Fri, 13 Apr 2018 00:00:00 +0000</pubDate>
      <guid>https://insinuator.net/2018/04/security-advisory-for-vmware-vrealize-automation-center/</guid>
      <description>&lt;p&gt;During a recent customer project we identified several vulnerabilities in the VMware vRealize Automation Center such as a DOM-based cross-site scripting and a missing renewal of session tokens during the login. The vulnerabilities have been disclosed to VMware on November 20th, 2017. A security advisory for the vulnerabilities has been made available &lt;a href=&#34;https://www.vmware.com/security/advisories/VMSA-2018-0009.html&#34;&gt;here&lt;/a&gt; on April 12th, 2018.&lt;/p&gt;&#xA;&lt;p&gt;Just a few words regarding the cross-site scripting vulnerability. This vulnerability is present within a GET request to the URL &lt;em&gt;/vcac/gadgets/ifr&lt;/em&gt; because of certain URL parameters whose values are directly passed to an &lt;em&gt;eval&lt;/em&gt; function call. The vulnerable parameters are &lt;em&gt;gwt:onLoadErrorFn&lt;/em&gt; and &lt;em&gt;gwt:onPropertyErrorFn&lt;/em&gt;. It seems that these parameters are actually never used by the application and we only found them by looking at the source code.&lt;/p&gt;</description>
    </item>
    <item>
      <title>Information About SAP Security Note 2336795</title>
      <link>https://insinuator.net/2017/03/information-about-sap-security-note-2336795/</link>
      <pubDate>Tue, 14 Mar 2017 00:00:00 +0000</pubDate>
      <guid>https://insinuator.net/2017/03/information-about-sap-security-note-2336795/</guid>
      <description>&lt;p&gt;Last year I encountered a slight variation of an internal port scan vulnerability for the CrystalReports component of SAP Business Objects. The original vulnerability was presented and disclosed by rapid7 in the talk “Hacking SAP Business Objects”. The corresponding slides can be found &lt;a href=&#34;http://spl0it.org/files/talks/source_barcelona10/Hacking%20SAP%20BusinessObjects.pdf&#34;&gt;here&lt;/a&gt;.&lt;/p&gt;&#xA;&lt;p&gt;Basically, the original vulnerability allowed port scanning of (internal) systems via the URL http://hostname/CrystalReports/viewrpt.cwr?id=$ID&amp;amp;wid=$WID&amp;amp;apstoken=ip:port@$TOKEN. By accessing this URL, different responses were received depending on if the port (parameter port in the URL) of the system (parameter ip in the URL) was in the state “open” or “closed”. The original vulnerability has been fixed a long time ago (SAP security note 1432881), but the fix did allow for a slight variation to make the attack work again.&lt;/p&gt;</description>
    </item>
    <item>
      <title>31c0n 2017 in Auckland, New Zealand</title>
      <link>https://insinuator.net/2017/03/31c0n-2017-in-auckland-new-zealand/</link>
      <pubDate>Fri, 03 Mar 2017 00:00:00 +0000</pubDate>
      <guid>https://insinuator.net/2017/03/31c0n-2017-in-auckland-new-zealand/</guid>
      <description>&lt;p&gt;Last week we gave a talk at the very first &lt;a href=&#34;https://www.31c0n.co.nz/&#34;&gt;31c0n&lt;/a&gt; in Auckland, New Zealand. The talk focused mainly on the methodology that we use to assess security products.&lt;/p&gt;&#xA;&lt;p&gt;More specifically, this methodology consists of 7 steps&lt;/p&gt;&#xA;&lt;ul&gt;&#xA;&lt;li&gt;Literature Research&lt;/li&gt;&#xA;&lt;li&gt;Jailbreak the Target&lt;/li&gt;&#xA;&lt;li&gt;Identify Components&lt;/li&gt;&#xA;&lt;li&gt;Understand the Architecture&lt;/li&gt;&#xA;&lt;li&gt;Map the Attack Surface&lt;/li&gt;&#xA;&lt;li&gt;Prioritize&lt;/li&gt;&#xA;&lt;li&gt;Analyze.&lt;/li&gt;&#xA;&lt;/ul&gt;&#xA;&lt;p&gt;Details on these steps as well as general suggestions to viable alternatives for security products can be found &lt;a href=&#34;https://www.ernw.de/download/31c0n_2017_sec_appliances.pdf&#34;&gt;here&lt;/a&gt; in the slides.&lt;/p&gt;</description>
    </item>
    <item>
      <title>Setting up a Research Environment for IP Cameras</title>
      <link>https://insinuator.net/2016/10/setting-up-a-research-environment-for-ip-cameras/</link>
      <pubDate>Mon, 17 Oct 2016 00:00:00 +0000</pubDate>
      <guid>https://insinuator.net/2016/10/setting-up-a-research-environment-for-ip-cameras/</guid>
      <description>&lt;p&gt;Embedded devices often serve as an entry point for an attack on a private or corporate network. The infamous attack on HackingTeam, for example, followed exactly this path as was revealed &lt;a href=&#34;http://pastebin.com/raw/0SNSvyjJ&#34;&gt;here&lt;/a&gt;. Although the attack may have been for the greater good (refer also to this great &lt;a href=&#34;https://www.troopers.de/events/troopers16/635_opening_keynote/&#34;&gt;keynote&lt;/a&gt;), such incidents demonstrate that it is important to properly secure your embedded devices. In a recent &lt;a href=&#34;https://www.insinuator.net/2016/04/discover-the-unknown-analyzing-an-iot-device/&#34;&gt;blog post&lt;/a&gt;, Niklaus presented how he analyzed the security posture of a MAX! Cube LAN Gateway. Moreover, Brian reported a few weeks ago on the &lt;a href=&#34;https://insinuator.net/2016/10/how-to-become-part-of-an-iot-botnet/&#34;&gt;security posture of IoT devices&lt;/a&gt; (and in particular on one of his cameras). With this post I would like to share my experiences with analyzing another embedded device: the &lt;a href=&#34;http://www.edimax.com/edimax/merchandise/merchandise_detail/data/edimax/au/home_network_cameras_indoor_fixed/ic-3116w/&#34;&gt;IC-3116W&lt;/a&gt; IP camera by Edimax. &lt;/p&gt;</description>
    </item>
    <item>
      <title>25th USENIX Security Symposium &amp;amp; WOOT Workshop</title>
      <link>https://insinuator.net/2016/09/25th-usenix-security-symposium-amp-woot-workshop/</link>
      <pubDate>Mon, 12 Sep 2016 00:00:00 +0000</pubDate>
      <guid>https://insinuator.net/2016/09/25th-usenix-security-symposium-amp-woot-workshop/</guid>
      <description>&lt;p&gt;Last month the annual USENIX Security Symposium with its co-located workshops (WOOT, CSET, FOCI, ASE, and HotSec) was held in Austin, Texas. The program of the conference together with the published papers can be found &lt;a href=&#34;https://www.usenix.org/conference/usenixsecurity16/technical-sessions&#34;&gt;here&lt;/a&gt; and information on the workshops can be found &lt;a href=&#34;https://www.usenix.org/conference/usenixsecurity16/workshops&#34;&gt;here&lt;/a&gt;.&lt;/p&gt;&#xA;&lt;p&gt;The research topics were quite diverse and included subjects such as low-level attacks, cryptographic attacks, and vehicle attacks. To give you an impression on the research that has been presented at the conference, let us discuss some of the talks in the following:&lt;/p&gt;</description>
    </item>
    <item>
      <title>SnoopCon Guest Day</title>
      <link>https://insinuator.net/2016/07/snoopcon-guest-day/</link>
      <pubDate>Fri, 01 Jul 2016 00:00:00 +0000</pubDate>
      <guid>https://insinuator.net/2016/07/snoopcon-guest-day/</guid>
      <description>&lt;p&gt;This year I had the pleasure to join the guest day of BT’s SnoopCon. There were quite a number of interesting talks throughout the day such as&lt;/p&gt;&#xA;&lt;ul&gt;&#xA;&lt;li&gt;&lt;a href=&#34;https://twitter.com/therealsaumil&#34;&gt;Saumil Shah&lt;/a&gt;‘s presentation on Stegosploit (as well as his rant about the state of information security)&lt;/li&gt;&#xA;&lt;li&gt;&lt;a href=&#34;https://twitter.com/drgfragkos&#34;&gt;Dr. Grigorios Fragkos&lt;/a&gt;‘ talk on airplane security (where he presented some maybe not-so-pleasant but also some good-to-hear facts on the security posture of airplanes)&lt;/li&gt;&#xA;&lt;li&gt;&lt;a href=&#34;https://twitter.com/dominicgs&#34;&gt;Dominic Spill&lt;/a&gt;‘s demonstration of tools and methods used to reverse engineer RF protocols&lt;/li&gt;&#xA;&lt;li&gt;&lt;a href=&#34;https://twitter.com/hackerfantastic&#34;&gt;Hacker Fantastic&lt;/a&gt;‘s talk on how to use the AX.25 protocol to bounce radio signals off the ISS to communicate with systems around the world&lt;/li&gt;&#xA;&lt;li&gt;Kostas Litovois’ and Vincent Yiu’s presentation on #WePWNise, a tool that can be used to efficiently create malicious VBA macros (by taking EMET configuration details into account)&lt;/li&gt;&#xA;&lt;li&gt;&lt;a href=&#34;https://twitter.com/bryanfite&#34;&gt;Bryan Fite&lt;/a&gt;‘s talk on how we have to think about Safety, Security, and Privacy in the IoT age.&lt;/li&gt;&#xA;&lt;/ul&gt;&#xA;&lt;p&gt;I really enjoyed the talks and had a great time! Thanks to all the organizers and speakers!&lt;/p&gt;</description>
    </item>
    <item>
      <title>24th USENIX Security Symposium &amp;amp; WOOT Workshop</title>
      <link>https://insinuator.net/2015/08/24th-usenix-security-symposium-amp-woot-workshop/</link>
      <pubDate>Fri, 28 Aug 2015 00:00:00 +0000</pubDate>
      <guid>https://insinuator.net/2015/08/24th-usenix-security-symposium-amp-woot-workshop/</guid>
      <description>&lt;p&gt;Recently I had the pleasure to attend the 24th USENIX Security Symposium and its co-located Workshop on Offensive Technologies (WOOT) in Washington, D.C. The workshop has received quite some attention this year, 57 submissions of which 19 have been accepted, so that the organizers decided to double its length from one to two days.&lt;/p&gt;&#xA;&lt;p&gt;The first day of the workshop began with an excellent keynote by Adam Langley, in which he reflected on the current state of SSL/TLS and its vulnerabilities. As a side remark he mentioned that to tackle the everlasting problem of such vulnerabilities to occur, research should be performed with a much higher level of abstraction rather than focusing on the exact details of a “certain hash function of some specific CBC cipher”.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
