<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>IoT on Insinuator.net - Bold Statements</title>
    <link>https://insinuator.net/tags/iot/</link>
    <description>Recent content in IoT on Insinuator.net - Bold Statements</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Thu, 16 Apr 2026 00:00:00 +0000</lastBuildDate>
    <atom:link href="https://insinuator.net/tags/iot/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Disclosure: Command Injection in Geutebrück Cameras</title>
      <link>https://insinuator.net/2026/04/disclosure-command-injection-in-geutebr%C3%BCck-cameras/</link>
      <pubDate>Thu, 16 Apr 2026 00:00:00 +0000</pubDate>
      <guid>https://insinuator.net/2026/04/disclosure-command-injection-in-geutebr%C3%BCck-cameras/</guid>
      <description>&lt;p&gt;During a penetration test for a customer, we identified a command injection&#xA;vulnerability in Geutebrück security cameras that allows authenticated attackers&#xA;to execute arbitrary commands as root through the web interface. The root cause&#xA;is unsanitized user input being passed into a &lt;code&gt;sed&lt;/code&gt; script (and at least 12&#xA;other CGI endpoints). In addition to the injection, we identified an XSS&#xA;vulnerability, an exposed system menu leaking configuration and log data, and an&#xA;insecure GET-parameter-to-environment-variable mapping that enables abuse of&#xA;variables like &lt;code&gt;LD_PRELOAD&lt;/code&gt; and &lt;code&gt;LD_DEBUG&lt;/code&gt;. We reported the findings to&#xA;Geutebrück and a patched firmware was provided. This post walks through how we&#xA;got from a  &lt;code&gt;sed&lt;/code&gt; error message to a root shell.&lt;/p&gt;</description>
    </item>
    <item>
      <title>Hacking a Bluetooth Printer Server: GATT to UART Adapter?</title>
      <link>https://insinuator.net/2026/03/hacking-a-bluetooth-printer-server-gatt-to-uart-adapter/</link>
      <pubDate>Thu, 12 Mar 2026 00:00:00 +0000</pubDate>
      <guid>https://insinuator.net/2026/03/hacking-a-bluetooth-printer-server-gatt-to-uart-adapter/</guid>
      <description>&lt;p&gt;This blog post describes the journey of how we discovered an interesting&#xA;Bluetooth SoC within the Datong NP330, a&#xA;&lt;a href=&#34;https://www.dtprinter.cn/upload/doc/NP330_NP332UserManual_en.pdf&#34;&gt;Printer Server IoT device&lt;/a&gt;.&#xA;Our initial goal was to reverse-engineer and analyze the Bluetooth controller&#xA;that is included in the device. So we wanted to be able to dump the firmware or,&#xA;if possible, get shell access on the printer server. During that journey we&#xA;found a few vulnerabilities that ultimately let an attacker fully compromise the&#xA;device. This is possible over Bluetooth or network via unauthenticated remote&#xA;code execution with root privileges.&lt;/p&gt;</description>
    </item>
    <item>
      <title>Part I: Bluetooth Auracast from a Security Researcher’s Perspective</title>
      <link>https://insinuator.net/2025/01/part-i-bluetooth-auracast-from-a-security-researchers-perspective/</link>
      <pubDate>Mon, 27 Jan 2025 00:00:00 +0000</pubDate>
      <guid>https://insinuator.net/2025/01/part-i-bluetooth-auracast-from-a-security-researchers-perspective/</guid>
      <description>&lt;p&gt;Auracast, the new Bluetooth LE Broadcast Audio feature has gained some publicity&#xA;in the past months. The Bluetooth SIG has introduced the LE Audio feature-set to&#xA;the Bluetooth 5.2 Specification in 2019 and vendors are only now starting to&#xA;implement it. Auracast facilitates broadcasting audio over Bluetooth LE to a&#xA;potentially unlimited number of devices. It does not require pairing or&#xA;interaction between the sender and the receivers.&lt;/p&gt;&#xA;&lt;p&gt;We also presented this topic&#xA;&lt;a href=&#34;https://media.ccc.de/v/38c3-auracast-breaking-broadcast-le-audio-before-it-hits-the-shelves&#34;&gt;at 38c3&lt;/a&gt;.&#xA;This blog post will contain similar contents albeit with some more details.&lt;/p&gt;</description>
    </item>
    <item>
      <title>Change Your BLE Passkey Like You Change Your Underwear</title>
      <link>https://insinuator.net/2021/10/change-your-ble-passkey-like-you-change-your-underwear/</link>
      <pubDate>Thu, 21 Oct 2021 00:00:00 +0000</pubDate>
      <guid>https://insinuator.net/2021/10/change-your-ble-passkey-like-you-change-your-underwear/</guid>
      <description>&lt;p&gt;Using a static passkey for Bluetooth Low Energy pairing is insecure. Recent&#xA;versions of the Bluetooth specification contain an explicit warning about this.&#xA;However, in practice, we often see static passkeys being used. Moreover, there&#xA;are no public implementations of proofs-of-concept that can practically show why&#xA;using a static passkey is an issue. This is why we implemented one.&lt;/p&gt;&#xA;&lt;p&gt;In a recent assessment, we were testing a device that offered a Bluetooth&#xA;interface for data export and configuration. This device uses Bluetooth Low&#xA;Energy (BLE), and a static passkey (or PIN) is required to pair with it. This&#xA;passkey is displayed for a few seconds when the device is booted and stays the&#xA;same on each reboot. In fact, it is derived from static, device-specific data.&lt;/p&gt;</description>
    </item>
    <item>
      <title>Hack.lu 2018: ARM IoT Firmware Emulation Workshop by Saumil Udayan Shah</title>
      <link>https://insinuator.net/2018/10/hack.lu-2018-arm-iot-firmware-emulation-workshop-by-saumil-udayan-shah/</link>
      <pubDate>Wed, 24 Oct 2018 00:00:00 +0000</pubDate>
      <guid>https://insinuator.net/2018/10/hack.lu-2018-arm-iot-firmware-emulation-workshop-by-saumil-udayan-shah/</guid>
      <description>&lt;p&gt;First day at &lt;a href=&#34;https://2018.hack.lu/&#34;&gt;hack.lu&lt;/a&gt;. Three of us kicked the conference off with the ARM IoT Firmware Emulation workshop by &lt;a href=&#34;https://twitter.com/therealsaumil&#34;&gt;Saumil&lt;/a&gt;. The goal of this workshop was not so much to write exploits or to pwn boxes but to learn how to build a beneficial research environment by emulating the hardware of a Linux based IoT device to run its firmware in order to run analysis and tests.&lt;/p&gt;&#xA;&lt;p&gt;First step is to obtain the firmware. This could be done by dumping it directly from the device or by downloading firmware images from the vendor. In order to dump the firmware from the device one has to obtain access to the underlying system which is usually done by finding the serial console on the hardware since this one often exposes an unauthenticated root shell. I think there is enough documentation online on how to identify and connect to a serial console so I won’t cover the details here. It’s also covered in Saumil’s &lt;a href=&#34;https://www.slideshare.net/saumilshah/hacklu-2018-make-arm-shellcode-great-again&#34;&gt;slides&lt;/a&gt; in detail. Having the bootup logs from this console will be helpful later though. While talking about baud rates for the serial console Saumil made a great pun I don’t want to withhold: “Most common is baud rate 115200. If you find a console with baud rate 9600 you are in fact talking to an acoustic coupler. That’s not an IoT device, it rather belongs to a museum.”&lt;/p&gt;</description>
    </item>
    <item>
      <title>Security of Busch-Jaeger IP Gateway</title>
      <link>https://insinuator.net/2018/05/security-of-busch-jaeger-ip-gateway/</link>
      <pubDate>Wed, 16 May 2018 00:00:00 +0000</pubDate>
      <guid>https://insinuator.net/2018/05/security-of-busch-jaeger-ip-gateway/</guid>
      <description>&lt;p&gt;IoT is everywhere right now and there are a lot of products out there. I have been looking at an IP Gateway lately and found some serious issues. The &lt;a href=&#34;https://www.busch-jaeger.de/en/products/systems/door-communication/abb-welcome-ip-gateway-app-and-myabb-livingspace/&#34;&gt;Busch-Welcome IP-Gateway from Busch-Jaeger&lt;/a&gt; is one of the devices that bridges the gap between sensors and actors in your smart home and the network/Internet. It enables the communication to a door control system that implements various smart home functions. The device itself is offering an HTTP service to configure it, which is protected by a username and password. Some folks even actually expose the device and its login to the Internet. I tried to configure one of these lately and stumbled upon some security issues that I would like to discuss in this blog post.&lt;/p&gt;</description>
    </item>
    <item>
      <title>Industrial IoT Overview &amp; Case Studies</title>
      <link>https://insinuator.net/2018/04/industrial-iot-overview-case-studies/</link>
      <pubDate>Wed, 25 Apr 2018 00:00:00 +0000</pubDate>
      <guid>https://insinuator.net/2018/04/industrial-iot-overview-case-studies/</guid>
      <description>&lt;p&gt;Stefan and I had the pleasure of joining a one-day closed workshop on Industrial IoT Security. As always, we ended up with plenty of new research ideas and great contacts. We hope of course to post on follow-up research, but in this short post we quickly want to publish our slides which contain our input for the workshop. We mainly presented on IT security challenges for modern IIoT environments and presented some case studies for successful hardening/protection of IIoT environments as well as security in IIoT product development.&lt;/p&gt;</description>
    </item>
    <item>
      <title>#TR18 Next Generation Internet (NGI) Summaries</title>
      <link>https://insinuator.net/2018/03/%23tr18-next-generation-internet-ngi-summaries/</link>
      <pubDate>Fri, 23 Mar 2018 00:00:00 +0000</pubDate>
      <guid>https://insinuator.net/2018/03/%23tr18-next-generation-internet-ngi-summaries/</guid>
      <description>&lt;p&gt;This blogpost contains summaries of talks from this year’s &lt;a href=&#34;https://www.troopers.de/troopers18/&#34;&gt;TROOPERS18&lt;/a&gt; Next Generation Internet Event.&lt;/p&gt;&#xA;&lt;p&gt; &lt;/p&gt;&#xA;&lt;h1 id=&#34;ngi-keynote-by-graeme-neilson&#34;&gt;NGI Keynote by &lt;a href=&#34;https://www.troopers.de/events/speaker/7_graeme_neilson/&#34;&gt;Graeme Neilson&lt;/a&gt;&lt;/h1&gt;&#xA;&lt;p&gt;Before his infosec career Graeme was a street performer, then security researcher, now he calls himself a defender. The talk was built around the following sentence: “The infosec industry and community have completely failed to create meaningful change in the behavior of people”.&lt;/p&gt;&#xA;&lt;p&gt;The following example is a resume of how hacking worked from 1988 to 2017:&lt;/p&gt;</description>
    </item>
    <item>
      <title>Hacking 101 to mobile data</title>
      <link>https://insinuator.net/2018/02/hacking-101-to-mobile-data/</link>
      <pubDate>Tue, 06 Feb 2018 00:00:00 +0000</pubDate>
      <guid>https://insinuator.net/2018/02/hacking-101-to-mobile-data/</guid>
      <description>&lt;p&gt;Here is a short blog post that explains how you can make your own Man-in-the-Middle (MitM) setup for sniffing the traffic between a SIM card and the backend server. This is** NOT a new research** but I hope this will help anyone who doesn’t have a telco background to get started to play with mobile data sniffing and fake base stations. This is applicable to many scenarios today as we have so many IoT devices with SIM cards in it that connects to the backend.&lt;br&gt;&#xA;In this particular case, I am explaining the simplest scenario where the SIM card is working with 2G and GPRS. You can probably expect me with more articles with 3G, 4G MitM in future. But lets stick to 2G and GPRS for now.&lt;/p&gt;</description>
    </item>
    <item>
      <title>RIPE IoT Roundtable Meeting / Balanced Security for IPv6 CPE Revisited</title>
      <link>https://insinuator.net/2017/09/ripe-iot-roundtable-meeting-/-balanced-security-for-ipv6-cpe-revisited/</link>
      <pubDate>Fri, 29 Sep 2017 00:00:00 +0000</pubDate>
      <guid>https://insinuator.net/2017/09/ripe-iot-roundtable-meeting-/-balanced-security-for-ipv6-cpe-revisited/</guid>
      <description>&lt;p&gt;Last week I had the pleasure to participate at the first &lt;a href=&#34;https://www.ripe.net/participate/meetings/roundtable/september-2017/ripe-iot-roundtable-meeting-21-september-2017&#34;&gt;&lt;em&gt;RIPE IoT Roundtable Meeting&lt;/em&gt;&lt;/a&gt; in Leeds (thanks! to &lt;a href=&#34;https://www.ripe.net/about-us/press-centre/publications/speakers/marco-hogewoning&#34;&gt;Marco Hogewoning&lt;/a&gt; for organising it). It was a day with many fruitful discussions. I particularly enjoyed &lt;a href=&#34;https://twitter.com/kistel&#34;&gt;Robert Kisteleki&lt;/a&gt;‘s talk on RIPE NCC’s own design &amp;amp; (security) process considerations in the context of &lt;a href=&#34;https://atlas.ripe.net/&#34;&gt;RIPE Atlas&lt;/a&gt; (at TR17 NGI there was an &lt;a href=&#34;https://www.troopers.de/downloads/troopers17/TR17_RIPEatlas.pdf&#34;&gt;intro to Atlas&lt;/a&gt;, too).&lt;br&gt;&#xA;In this post I’d like to quickly lay out the main points of my own contribution on “Balanced Security for IPv6 CPE Revisited” (the slides can be found &lt;a href=&#34;https://www.ernw.de/download/RIPE_IoT_Roundtable_Sep2017_EnnoRey_BalancedIPv6Sec.pdf&#34;&gt;here&lt;/a&gt;).&lt;/p&gt;</description>
    </item>
    <item>
      <title>Summary of “Lockpicking in the IoT” at 33C3</title>
      <link>https://insinuator.net/2017/02/summary-of-lockpicking-in-the-iot-at-33c3/</link>
      <pubDate>Tue, 14 Feb 2017 00:00:00 +0000</pubDate>
      <guid>https://insinuator.net/2017/02/summary-of-lockpicking-in-the-iot-at-33c3/</guid>
      <description>&lt;p&gt;“Lockpicking in the IoT, …or why adding BTLE to a device sometimes isn’t smart at all” by Ray was one of my favourite talks, as it beautifully showed many different attack vectors as well as giving a nice guide for getting started in this area.&lt;/p&gt;&#xA;&lt;p&gt;It impressed me how carefree vendors and startups handled hardware and software security in “smart” devices as it seems that their devices were more or less easy to own. In his talk Ray pointed out physical AND implementational weaknesses that remained even after he reported them to the vendors.&lt;br&gt;&#xA;The most prominent sample he gave was when he opened a “Masterlock” by spinning a magnet on the lock itself to open it.&lt;/p&gt;</description>
    </item>
    <item>
      <title>Analyzing yet another Smart Home device</title>
      <link>https://insinuator.net/2016/12/analyzing-yet-another-smart-home-device/</link>
      <pubDate>Mon, 05 Dec 2016 00:00:00 +0000</pubDate>
      <guid>https://insinuator.net/2016/12/analyzing-yet-another-smart-home-device/</guid>
      <description>&lt;p&gt;As you have probably already recognized, some of us here at ERNW are doing research in the area of smart home technologies e.g. KNX. Recently, we took a deeper look into a device which is used to control a smart home system produced by the vendor BAB TECHNOLOGIE GmbH called “eibPort”. This device can be used to control smart home systems based on different technologies e.g. EnoCean or KNX depending on the version of the device. The eibPort comes with a visualization running on a webserver to control the whole system e.g. open or close windows, changing the temperature in different rooms or turning the alarm system on or off by simply clicking on symbols. The following screenshots illustrate an example of such a visualization:&lt;/p&gt;</description>
    </item>
    <item>
      <title>Research Diary: IP-Cameras Part 2</title>
      <link>https://insinuator.net/2016/11/research-diary-ip-cameras-part-2/</link>
      <pubDate>Wed, 30 Nov 2016 00:00:00 +0000</pubDate>
      <guid>https://insinuator.net/2016/11/research-diary-ip-cameras-part-2/</guid>
      <description>&lt;p&gt;Hi everybody,&lt;br&gt;&#xA;This is the second entry in our research diary on IP cameras. If you haven’t done so yet, you should read the first entry in advance. This time we focused more on analysis and exploitation.&lt;/p&gt;&#xA;&lt;h2 id=&#34;another-entry-vector&#34;&gt;&lt;a href=&#34;#another-entry-vector&#34;&gt;&lt;/a&gt;Another entry vector&lt;/h2&gt;&#xA;&lt;p&gt;After running a vulnerability scan on both devices, it was revealed that the M1033 has multiple buffer overflow vulnerabilities (CVE-2012-5958 to CVE-2012-5965), which are readily exploitable via Metasploit. This gave us another shell (in addition to the root shell mentioned in the last post), though this time it was not a root shell. By using the &lt;em&gt;find&lt;/em&gt; command, we searched for executables having the &lt;em&gt;setuid&lt;/em&gt; or &lt;em&gt;setgid&lt;/em&gt; bit set. We hoped to use one of those to escalate privileges. To do so yourself add the parameter &lt;em&gt;-perm -4000&lt;/em&gt; to &lt;em&gt;find&lt;/em&gt; and it will search for files having the setuid bit set. If you try that on your own unix-like device, for example it should yield &lt;em&gt;/bin/passwd&lt;/em&gt; which is perfectly reasonable as you’re able to change your password without being root.&lt;/p&gt;</description>
    </item>
    <item>
      <title>Research Diary: IP-Cameras</title>
      <link>https://insinuator.net/2016/11/research-diary-ip-cameras/</link>
      <pubDate>Tue, 22 Nov 2016 00:00:00 +0000</pubDate>
      <guid>https://insinuator.net/2016/11/research-diary-ip-cameras/</guid>
      <description>&lt;p&gt;As you probably know we perform research on a regular basis at ERNW. This post is the first entry on our – Benjamin’s and Pascal’s – research diary. You might already have seen &lt;a href=&#34;https://insinuator.net/2016/10/setting-up-a-research-environment-for-ip-cameras/&#34;&gt;Oliver’s post on setting up an research environment&lt;/a&gt; or Brian’s posts on IoT botnets (&lt;a href=&#34;https://insinuator.net/2016/10/how-to-become-part-of-an-iot-botnet/&#34;&gt;here&lt;/a&gt; and &lt;a href=&#34;https://insinuator.net/2016/10/a-quick-insight-into-the-mirai-botnet/&#34;&gt;here&lt;/a&gt;). With that in mind we want to take a look at one of the market leaders for network camera equipment: AXIS.&lt;/p&gt;&#xA;&lt;p&gt;At first we’d like to give a quick overview of our research objects. We bought two cameras, an AXIS M1033-W and an AXIS M3005-V. The M1033’s description states that it is for “small business, hotels, residences and more”. The M3005 has a typical dome design and was actually seen in some customer environments during projects this year.&lt;/p&gt;</description>
    </item>
    <item>
      <title>IoT the S is for Secure – Unknown Administration Interface in Wireless Plug</title>
      <link>https://insinuator.net/2016/11/iot-the-s-is-for-secure-unknown-administration-interface-in-wireless-plug/</link>
      <pubDate>Mon, 21 Nov 2016 00:00:00 +0000</pubDate>
      <guid>https://insinuator.net/2016/11/iot-the-s-is-for-secure-unknown-administration-interface-in-wireless-plug/</guid>
      <description>&lt;p&gt;Dear Readers,&lt;/p&gt;&#xA;&lt;p&gt;just recently i bought a wireless plug on &lt;a href=&#34;https://www.amazon.de/gp/product/B01LXASIZG/ref=oh_aui_detailpage_o01_s00?ie=UTF8&amp;amp;psc=1&#34;&gt;Amazon&lt;/a&gt; with the main use of controlling my coffee machine with an app. The installation of the wireless plug was quite easy and only requires me to set my Wifi SSID and my passphrase – that’s it. But what happened behind the scenes? I visited the control interface of my router and saw that along with the other devices there was a new one with the network name HF-LPB100 and a local IP address in my case 192.168.0.235. First of all i wondered about the name itself, but ignored that and kept on looking for open ports.&lt;/p&gt;</description>
    </item>
    <item>
      <title>(Securely) Updating Smart Devices / Some Considerations</title>
      <link>https://insinuator.net/2016/11/securely-updating-smart-devices-/-some-considerations/</link>
      <pubDate>Tue, 15 Nov 2016 00:00:00 +0000</pubDate>
      <guid>https://insinuator.net/2016/11/securely-updating-smart-devices-/-some-considerations/</guid>
      <description>&lt;p&gt;How to provide updates to IoT devices – yes, I’m aware this might be a overly broad generalization for many different devices – has been the topic of many discussions in the last years (for those interested the papers from the “&lt;a href=&#34;https://www.iab.org/activities/workshops/iotsu/&#34;&gt;Internet of Things Software Update Workshop (IoTSU)&lt;/a&gt;” might be a good starting point).&lt;br&gt;&#xA;Given Matthias and I will moderate the respective session at tomorrow’s &lt;a href=&#34;https://www.troopers.de/iot-insight-summit-2016/iot-insight-summit-2016-overview/&#34;&gt;IoT Insight Summit&lt;/a&gt; I started writing down some points that we consider relevant in this context.&lt;/p&gt;</description>
    </item>
    <item>
      <title>15. Cyber-Sicherheits-Tag</title>
      <link>https://insinuator.net/2016/11/15.-cyber-sicherheits-tag/</link>
      <pubDate>Tue, 08 Nov 2016 00:00:00 +0000</pubDate>
      <guid>https://insinuator.net/2016/11/15.-cyber-sicherheits-tag/</guid>
      <description>&lt;p&gt;Today Kevin and I had the pleasure to to present at the German &lt;a href=&#34;https://www.allianz-fuer-cybersicherheit.de/ACS/DE/Erfahrungsaustausch/CST/cur/cst.html&#34;&gt;15. Cyber-Sicherheits-Tag&lt;/a&gt; in &lt;a href=&#34;https://en.wikipedia.org/wiki/Project_Blinkenlights&#34;&gt;Berlin&lt;/a&gt; which is organized by the &lt;a href=&#34;https://www.allianz-fuer-cybersicherheit.de/ACS/DE/Home/startseite.html&#34;&gt;Alliance for Cyber Security&lt;/a&gt;. This iteration covered security aspects of the Internet of Things and we enjoyed some great conversations. The presentations were limited to ten slides and can be found here:&lt;/p&gt;&#xA;&lt;p&gt;&lt;a href=&#34;https://www.ernw.de/download/ERNW_Defense_in_Depth_IoT_kschaller.pdf&#34;&gt;Kevin Schaller – Defense in Depth in IoT&lt;/a&gt;&lt;/p&gt;&#xA;&lt;p&gt;&lt;a href=&#34;https://www.ernw.de/download/ERNWResearch_UpdateManagementAndIoT_mluft.pdf&#34;&gt;Matthias Luft – Update Management in IoT&lt;/a&gt;&lt;/p&gt;&#xA;&lt;p&gt;Since the slides were supposed to be short and only support the presentation, you still have the chance to get the full content (and even challenge it or ask to dive deeper during the break-out discussions) next week at &lt;a href=&#34;https://www.troopers.de/iot-insight-summit-2016/iot-insight-summit-2016-overview/&#34;&gt;our own IoT event&lt;/a&gt; 😉&lt;/p&gt;</description>
    </item>
    <item>
      <title>IoT Insight Summit November 15, 2016</title>
      <link>https://insinuator.net/2016/10/iot-insight-summit-november-15-2016/</link>
      <pubDate>Wed, 26 Oct 2016 00:00:00 +0000</pubDate>
      <guid>https://insinuator.net/2016/10/iot-insight-summit-november-15-2016/</guid>
      <description>&lt;p&gt;The newest addition to ERNW, ERNW Insight which now hosts &lt;a href=&#34;https://www.troopers.de/troopers17/&#34;&gt;TROOPERS&lt;/a&gt;, is launching a new concept this year. Based on the successful TROOPERS Roundtable sessions, ERNW Insight will host a series events every year covering current and relevant topics in the field of IT Security. While the style of the events may vary the in-depth knowledge sharing that you have come to know from TROOPERS will not!&lt;/p&gt;&#xA;&lt;p&gt;The inaugural event will be our&lt;a href=&#34;https://www.troopers.de/iot-insight-summit-2016/iot-insight-summit-2016-overview/&#34;&gt; IoT Insight Summit&lt;/a&gt;, taking place on November 15, 2016 at the &lt;a href=&#34;https://www.ihg.com/crowneplaza/hotels/us/en/heidelberg/hdbge/hoteldetail&#34;&gt;Crowne Plaza Heidelberg&lt;/a&gt;.  This 1-day event will begin with a keynote and case study from industry experts.  Afterwards, all participants will be divided into five groups of 10 persons each to participate in our “Break Out Sessions”. Every participant  will get the opportunity to attend all 5 Break Out Sessions, where our IT Security moderators will lead discussions on typical problems and solutions in IoT.&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>How to Become Part of an IoT Botnet</title>
      <link>https://insinuator.net/2016/10/how-to-become-part-of-an-iot-botnet/</link>
      <pubDate>Sat, 01 Oct 2016 00:00:00 +0000</pubDate>
      <guid>https://insinuator.net/2016/10/how-to-become-part-of-an-iot-botnet/</guid>
      <description>&lt;p&gt;I suppose there are many people out there who want to achieve a greater good, fight evil corp and “show those guys”. So why not set a statement and become part of a botnet? #Irony!!! Of course I suppose (hope) that none of you actually want to be part of something like an IoT botnet, but joining could in theory be dead easy. So quite a while back I bought a dead cheap WiFi camera for use at home. It was kind of just as insecure as I had expected, so it got it’s own VLAN and stuff and here is why….&lt;/p&gt;</description>
    </item>
    <item>
      <title>Hardware Hacking Week @ ERNW</title>
      <link>https://insinuator.net/2016/09/hardware-hacking-week-@-ernw/</link>
      <pubDate>Fri, 09 Sep 2016 00:00:00 +0000</pubDate>
      <guid>https://insinuator.net/2016/09/hardware-hacking-week-@-ernw/</guid>
      <description>&lt;p&gt;Internal workshops are one of the reoccurring events at ERNW, that help us to gain knowledge in areas outside our usual expertise. One of the recent workshops which happened during the week from August 22nd-25th was Hardware Hacking. Held by Brian Butterly (&lt;a href=&#34;https://twitter.com/BadgeWizard&#34;&gt;@BadgeWizard&lt;/a&gt;) and Dominic Spill &lt;a href=&#34;http://@dominicgs&#34;&gt;(@dominicgs),&lt;/a&gt; this workshop took place in two parts. Brian kickstarted the introductory session by guiding us through the fundamental steps of Hardware Hacking. Brian did an excellent job of making things simpler by giving a detailed explanation on the basic concepts. For a beginner in hardware hacking, the topic could be rather intimidating if not handled properly.&lt;/p&gt;</description>
    </item>
    <item>
      <title>KNXmap: A KNXnet/IP Scanning and Auditing Tool</title>
      <link>https://insinuator.net/2016/09/knxmap-a-knxnet/ip-scanning-and-auditing-tool/</link>
      <pubDate>Mon, 05 Sep 2016 00:00:00 +0000</pubDate>
      <guid>https://insinuator.net/2016/09/knxmap-a-knxnet/ip-scanning-and-auditing-tool/</guid>
      <description>&lt;p&gt;Users of the &lt;a href=&#34;https://en.wikipedia.org/wiki/KNX_(standard)&#34;&gt;KNX&lt;/a&gt;, a standard for home automation bus systems, may already have come across KNXnet/IP (also known as EIBnet/IP): It is an extension for KNX that defines Ethernet as a communication medium for KNX which allows communication with KNX buses over IP driven networks. Additionally, it enables one to couple multiple bus installations over IP gateways, or so called KNXnet/IP gateways.&lt;/p&gt;&#xA;&lt;p&gt;In the course of some KNX related research we’ve had access to various KNXnet/IP gateways from different vendors, most of them coupled in a lab setup for testing purposes. The typical tools used for such tasks are &lt;a href=&#34;https://knx.org/knx-de/software/ets/herunterladen/index.php&#34;&gt;ETS&lt;/a&gt;, the professional software developed by the creators of KNX (proprietary, test licenses available) and &lt;a href=&#34;https://www.auto.tuwien.ac.at/~mkoegler/index.php/eibd&#34;&gt;eibd&lt;/a&gt;, an open source implementation of the KNX standard developed by the TU Vienna.&lt;/p&gt;</description>
    </item>
    <item>
      <title>Notes on Hijacking GSM/GPRS Connections</title>
      <link>https://insinuator.net/2016/07/notes-on-hijacking-gsm/gprs-connections/</link>
      <pubDate>Sun, 17 Jul 2016 00:00:00 +0000</pubDate>
      <guid>https://insinuator.net/2016/07/notes-on-hijacking-gsm/gprs-connections/</guid>
      <description>&lt;p&gt;As shown in previous blogposts we regularly work with GSM/GPRS basestations for &lt;a href=&#34;https://www.insinuator.net/2016/05/some-notes-on-utilizing-telco-networks-for-penetration-tests/&#34;&gt;testing devices with cellular uplinks&lt;/a&gt; or to simply run a &lt;a href=&#34;https://www.insinuator.net/2016/03/troopers16-gsm-network/&#34;&gt;private network during TROOPERS&lt;/a&gt;. Here the core difference between a random TROOPERS attendee and a device we want to hack is the will to join our network, or not! While at the conference we hand out own SIM cards which accept the TROOERPS GSM network as their “home network” some device need to be pushed a little bit.&lt;br&gt;&#xA;Every SIM card has it’s own home network, which is encoded in the fist five (European standard) or six (North American standard) digits of its IMSI – International Subscriber Number. The first three digits are the MCC, the Mobile Country Code, the next two/three the MNC, Mobile Network Code. International network overview are publicly available and for example &lt;a href=&#34;https://www.itu.int/dms_pub/itu-t/opb/sp/T-SP-E.212B-2014-PDF-E.pdf&#34;&gt;can be found &amp;gt;here&amp;lt;&lt;/a&gt;. For instance, Germany has the MCC 262 and Vodafone Germany uses MNC 02. So a SIM card with an IMSI starting with 26202 belongs to them.&lt;br&gt;&#xA;Sticking to the settings in its own SIM card a device will always prefer to connect to it’s own home network above all others. If the home network is not available it will usually go for the strongest signal. To protect users from unnecessary costs, an operator will usually add certain rules to prevent the device from connecting to other networks in the same country. So if you’re an O2 customer in Germany, visit a shopping center and only have reception for a T-Mobile cell, your phone will not directly jump into this network, even though it’s the strongest signal source.&lt;/p&gt;</description>
    </item>
    <item>
      <title>Some Notes on Utilizing Telco Networks for Penetration Tests</title>
      <link>https://insinuator.net/2016/05/some-notes-on-utilizing-telco-networks-for-penetration-tests/</link>
      <pubDate>Wed, 25 May 2016 00:00:00 +0000</pubDate>
      <guid>https://insinuator.net/2016/05/some-notes-on-utilizing-telco-networks-for-penetration-tests/</guid>
      <description>&lt;p&gt;After a couple of years in pentesting Telco Networks, I’d like to give you some insight into our pentesting methodology and setup we are using for testing “Mobile and Telecommunication Devices”. I am not talking about pentesting professional providers’ equipment (as in previous blogposts), it is about pentesting of devices that have a modem in place like a lot of IoT devices (you know about the fridge having a GSM Modem, right?) do.&lt;/p&gt;</description>
    </item>
    <item>
      <title>Discover the Unknown: Analyzing an IoT Device</title>
      <link>https://insinuator.net/2016/04/discover-the-unknown-analyzing-an-iot-device/</link>
      <pubDate>Mon, 11 Apr 2016 00:00:00 +0000</pubDate>
      <guid>https://insinuator.net/2016/04/discover-the-unknown-analyzing-an-iot-device/</guid>
      <description>&lt;p&gt;This blog post will give a brief overview about how a simple IoT device can be assessed. It will show a basic methodology, what tools can be used for different tasks and how to solve problems that may arise during analyses. It is aimed at readers that are interested in how such a device can be assessed, those with general interest in reverse engineering or the ones who just want to see how to technically approach an unknown device.&lt;/p&gt;</description>
    </item>
    <item>
      <title>The road to secure Smart Cars: ENISA approach</title>
      <link>https://insinuator.net/2016/04/the-road-to-secure-smart-cars-enisa-approach/</link>
      <pubDate>Fri, 01 Apr 2016 00:00:00 +0000</pubDate>
      <guid>https://insinuator.net/2016/04/the-road-to-secure-smart-cars-enisa-approach/</guid>
      <description>&lt;p&gt;At TROOPERS16, Dr. Cédric LÉVY-BENCHETON an expert in cyber security at ENISA, the European Union Agency for Network and Information Security. Dr. Cédric LÉVY-BENCHETON  holds a presentation about cyber security of IoT (Internet of Things) and smart cars he presents the current threats in IoT and Smart cars. ENISA is an agency of the European Union. ENISA assists the Commission, the Member States and, the business community in meeting the requirements of network and information security.&lt;/p&gt;</description>
    </item>
    <item>
      <title>How easy to grow robust botnet with low hanging fruits (IoT) – for free</title>
      <link>https://insinuator.net/2016/03/how-easy-to-grow-robust-botnet-with-low-hanging-fruits-iot-for-free/</link>
      <pubDate>Thu, 31 Mar 2016 00:00:00 +0000</pubDate>
      <guid>https://insinuator.net/2016/03/how-easy-to-grow-robust-botnet-with-low-hanging-fruits-iot-for-free/</guid>
      <description>&lt;p&gt;Attila Marosi works as a Senior Threat Research at Sophos Labs in Hungary. His talk focused on vulnerable IoT devices that are exposed to the internet. His approach was to look for vulnerable devices with low cost tools and publicly available data.&lt;/p&gt;&#xA;&lt;p&gt;He started his talk with the spoiler that he is not going to reveal any new attacks nor new techniques. But newer data are more adequate and we can see the current state of vulnerable devices connected to the internet. This means his approach was to test the state of IoT devices like Routers, NAS and so on with publicly available data.&lt;/p&gt;</description>
    </item>
    <item>
      <title>13th escar Europe conference | Embedded Security in Cars</title>
      <link>https://insinuator.net/2015/11/13th-escar-europe-conference-embedded-security-in-cars/</link>
      <pubDate>Tue, 17 Nov 2015 00:00:00 +0000</pubDate>
      <guid>https://insinuator.net/2015/11/13th-escar-europe-conference-embedded-security-in-cars/</guid>
      <description>&lt;p&gt;Last week I had the pleasure to attend the “&lt;strong&gt;escar&lt;/strong&gt;” (&lt;em&gt;Embedded Security in Cars&lt;/em&gt;) &lt;strong&gt;conference&lt;/strong&gt; in &lt;em&gt;Cologne, Germany&lt;/em&gt;.&lt;br&gt;&#xA;Arriving late Tuesday, I had the chance to get a rich breakfast before joining the con in the hotel Dorint at Cologne’s famous place the Heumarkt. Unfortunately I had to deal with two stumbling blocks on my way to the Dobrint: The magnetic sensor of my mobile which went crazy (no compass) and – the date. 11th of November in Cologne means just one thing – &lt;em&gt;&lt;strong&gt;carneval&lt;/strong&gt;&lt;/em&gt;! The whole city was just in a state of exception. Everybody on my way to the venue seemed to be drinking or beeing already drunk – at 9am! 😉&lt;br&gt;&#xA;Being a little late, I went straight to the room after registration. As there was only one track to follow you could not miss any talk – nice thing!&lt;br&gt;&#xA;After we were welcomed by the hosts, and the first talk started.&lt;/p&gt;</description>
    </item>
    <item>
      <title>Car Hacking Lab – Work in Progress</title>
      <link>https://insinuator.net/2015/04/car-hacking-lab-work-in-progress/</link>
      <pubDate>Tue, 28 Apr 2015 00:00:00 +0000</pubDate>
      <guid>https://insinuator.net/2015/04/car-hacking-lab-work-in-progress/</guid>
      <description>&lt;p&gt;We just wanted to share some impressions from our car hacking lab:&lt;/p&gt;&#xA;&lt;p&gt;&lt;a href=&#34;https://www.insinuator.net/wp-content/uploads/2015/04/car_lab2.mp4&#34;&gt;https://www.insinuator.net/wp-content/uploads/2015/04/car_lab2.mp4&lt;/a&gt;&lt;/p&gt;&#xA;&lt;p&gt; &lt;/p&gt;&#xA;&lt;p&gt;stay tuned,&lt;/p&gt;&#xA;&lt;p&gt;The ERNW Car Hacking Team&lt;/p&gt;&#xA;&lt;p&gt; &lt;/p&gt;</description>
    </item>
    <item>
      <title>Scal(e)ing down Privacy</title>
      <link>https://insinuator.net/2014/11/scaleing-down-privacy/</link>
      <pubDate>Sat, 22 Nov 2014 00:00:00 +0000</pubDate>
      <guid>https://insinuator.net/2014/11/scaleing-down-privacy/</guid>
      <description>&lt;p&gt;As you might know we are continuously doing &lt;a href=&#34;http://www.insinuator.net/2013/11/medical-device-security/&#34; title=&#34;Medical Devices&#34;&gt;research on medical devices&lt;/a&gt;. I presented some of the new results at &lt;a href=&#34;http://www.powerofcommunity.net/index.html&#34; title=&#34;Power of Community 2014&#34;&gt;Power of Community 2014&lt;/a&gt; last week and we thought we would share some of the details with you here. The focus of the previous work was testing medical devices that are used in hospitals like patient monitors, syringe pumps or even MRIs. This time we looked at a device that every user can use at home and which is available to anyone on the market: A smart scale.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
