<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Misc on Insinuator.net - Bold Statements</title>
    <link>https://insinuator.net/categories/misc/</link>
    <description>Recent content in Misc on Insinuator.net - Bold Statements</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Wed, 12 Aug 2026 00:00:00 +0000</lastBuildDate>
    <atom:link href="https://insinuator.net/categories/misc/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>ERNW White Paper 79: Integrating Incident Analysis and Digital Forensics Tooling for Automated Compromise Detection</title>
      <link>https://insinuator.net/2026/08/ernw-white-paper-79-integrating-incident-analysis-and-digital-forensics-tooling-for-automated-compromise-detection/</link>
      <pubDate>Wed, 12 Aug 2026 00:00:00 +0000</pubDate>
      <guid>https://insinuator.net/2026/08/ernw-white-paper-79-integrating-incident-analysis-and-digital-forensics-tooling-for-automated-compromise-detection/</guid>
      <description>&lt;p&gt;With this blog post I am pleased to announce the publication of a new ERNW White Paper about our incident analysis and digital forensics framework. It is available on our &lt;a href=&#34;https://ernw.de/en/whitepapers/issue-79.html&#34;&gt;website&lt;/a&gt;.&lt;/p&gt;&#xA;&lt;p&gt;Due to the increasing number and impact of computer security incidents, it has become essential to develop and implement efficient measures for their investigation. However, comprehensive forensic analyses are time-consuming, and this time is often not available to security analysts during computer security incidents. As a result, automated tools are increasingly being used. These tools, however, often cover only a limited scope of the necessary analyses and typically require deep technical expertise to be used effectively.&lt;/p&gt;</description>
    </item>
    <item>
      <title>TIA Project Parser</title>
      <link>https://insinuator.net/2026/08/tia-project-parser/</link>
      <pubDate>Wed, 12 Aug 2026 00:00:00 +0000</pubDate>
      <guid>https://insinuator.net/2026/08/tia-project-parser/</guid>
      <description>&lt;p&gt;While working on an OT project, we looked into TIA Portal&lt;sup id=&#34;fnref:1&#34;&gt;&lt;a href=&#34;#fn:1&#34; class=&#34;footnote-ref&#34; role=&#34;doc-noteref&#34;&gt;1&lt;/a&gt;&lt;/sup&gt; project files to extract more information about changes, especially timestamps to be able to reconstruct a timeline. The TIA Portal (Totally Integrated Automation Portal) allows to create and upload programs for PLC (Programmable Logic Controller) devices often used in the OT (Operational Technology) landscape. Some attacks are able to find the workstation with the TIA Portal and manipulate the project to reprogram the PLCs. To be able to reconstruct the timeline of these changes we wanted to be able to read the timestamps of events from the TIA project files.&lt;/p&gt;</description>
    </item>
    <item>
      <title>Your Android Bluetooth Traffic Captures Should Be Live</title>
      <link>https://insinuator.net/2026/07/your-android-bluetooth-traffic-captures-should-be-live/</link>
      <pubDate>Mon, 27 Jul 2026 00:00:00 +0000</pubDate>
      <guid>https://insinuator.net/2026/07/your-android-bluetooth-traffic-captures-should-be-live/</guid>
      <description>&lt;p&gt;In this post I want to talk about a very essential part of my workflow when dealing with Bluetooth devices, particularly IoT devices with a corresponding mobile app: Live capture of Android Bluetooth traffic with Wireshark.&lt;/p&gt;&#xA;&lt;p&gt;Before you stop reading because you think you know how to do this already, the method does not involve pulling bug reports off your phone, and it does not require root. And most importantly it gives you a &lt;strong&gt;live&lt;/strong&gt; packet log in Wireshark.&lt;/p&gt;</description>
    </item>
    <item>
      <title>Windows Hello for Business – Full Report Has Been Released</title>
      <link>https://insinuator.net/2026/07/windows-hello-for-business-full-report-has-been-released/</link>
      <pubDate>Thu, 16 Jul 2026 00:00:00 +0000</pubDate>
      <guid>https://insinuator.net/2026/07/windows-hello-for-business-full-report-has-been-released/</guid>
      <description>&lt;p&gt;Yesterday, the BSI (the German Federal Office for Information Security, or Bundesamt für Sicherheit in der Informationstechnik in German) published the first result document from the “Windows dissected” (ger.: “Windows seziert”) project: our analysis of Windows Hello for Business (WHfB). If you have followed this blog over the past year, you have seen the pieces. The full 170-page report has now been published. And it can be downloaded from the &lt;a href=&#34;https://www.bsi.bund.de/DE/Service-Navi/Publikationen/Studien/Windows-seziert/windows-seziert_node.html&#34;&gt;project page&lt;/a&gt;.&lt;/p&gt;</description>
    </item>
    <item>
      <title>Insights into Entra ID’s (Un)Conditional Access</title>
      <link>https://insinuator.net/2026/05/insights-into-entra-ids-unconditional-access/</link>
      <pubDate>Thu, 21 May 2026 00:00:00 +0000</pubDate>
      <guid>https://insinuator.net/2026/05/insights-into-entra-ids-unconditional-access/</guid>
      <description>&lt;p&gt;When looking at security measures in Microsoft Entra ID environments, a common&#xA;recommendation is to implement Conditional Access policies.&lt;/p&gt;&#xA;&lt;p&gt;Whether Conditional Access is implemented can be quickly checked, and you can&#xA;put a check mark next to it in your best-practice compliance form. However,&#xA;simply implementing conditional access will not provide much security. A&#xA;phishing attack that we recently analyzed highlights this very well.&lt;/p&gt;</description>
    </item>
    <item>
      <title>CVE-2026-47237 – Overly Permissive Istio Permissions Allow Kubeflow Authorization Token Stealing</title>
      <link>https://insinuator.net/2026/05/cve-2026-47237-overly-permissive-istio-permissions-allow-kubeflow-authorization-token-stealing/</link>
      <pubDate>Wed, 20 May 2026 00:00:00 +0000</pubDate>
      <guid>https://insinuator.net/2026/05/cve-2026-47237-overly-permissive-istio-permissions-allow-kubeflow-authorization-token-stealing/</guid>
      <description>&lt;p&gt;Kubeflow is vulnerable to the theft of authorization tokens by any user of the&#xA;Kubeflow UI or APIs, such as the Dashboard, Pipelines API, or Notebooks. With&#xA;this token, the attacker can take over the user&amp;rsquo;s account and the data that is&#xA;processed by that user. The attacker needs a valid user with the &lt;code&gt;kubeflow-edit&lt;/code&gt;&#xA;or Contributor role in a random Kubeflow namespace to perform this attack. This&#xA;is given if &lt;em&gt;Automatic Profile Creation&lt;/em&gt; is enabled. A setup based on the&#xA;official manifests prior to version 1.10, and on most other packaged Kubeflow&#xA;distributions, is vulnerable.&lt;/p&gt;&#xA;&lt;p&gt;The Istio edit permissions were removed by Kubeflow in a timely manner. Affected&#xA;users should update to the latest version to mitigate this issue.&lt;/p&gt;</description>
    </item>
    <item>
      <title>ERNW White Paper 77: Unified Security Hardening with Cross-Platform Native Binaries</title>
      <link>https://insinuator.net/2026/05/ernw-white-paper-77-unified-security-hardening-with-cross-platform-native-binaries/</link>
      <pubDate>Wed, 20 May 2026 00:00:00 +0000</pubDate>
      <guid>https://insinuator.net/2026/05/ernw-white-paper-77-unified-security-hardening-with-cross-platform-native-binaries/</guid>
      <description>&lt;p&gt;When configuring a new device, achieving an acceptable Lynis hardening score is&#xA;a challenge most practitioners are familiar with.&lt;/p&gt;</description>
    </item>
    <item>
      <title>ERNW Whitepaper 76: Linux Client Hardening Guide</title>
      <link>https://insinuator.net/2026/05/ernw-whitepaper-76-linux-client-hardening-guide/</link>
      <pubDate>Tue, 19 May 2026 00:00:00 +0000</pubDate>
      <guid>https://insinuator.net/2026/05/ernw-whitepaper-76-linux-client-hardening-guide/</guid>
      <description>&lt;p&gt;Hardening a Linux client system to an acceptable degree is a time-consuming&#xA;process, one that demands familiarity with a broad set of configuration&#xA;parameters, framework recommendations, and the reasoning behind each control.&lt;/p&gt;&#xA;&lt;p&gt;This post introduces our new Linux client hardening guide&#xA;(&lt;a href=&#34;https://github.com/ernw/hardening/blob/master/operating_system/linux/ERNW_Hardening_Linux.md&#34;&gt;MD&lt;/a&gt;,&#xA;&lt;a href=&#34;https://ernw.de/en/whitepapers/issue-76.html&#34;&gt;PDF&lt;/a&gt;), a comprehensive, publicly&#xA;available hardening reference for Linux systems.&lt;/p&gt;&#xA;&lt;h2 id=&#34;motivation-and-scope&#34;&gt;Motivation and Scope&lt;/h2&gt;&#xA;&lt;p&gt;The guide covers the full breadth of controls needed to significantly raise the&#xA;security posture of a modern Linux installation while preserving operational&#xA;usability (this will be very subjective, the guide reflects my opinion of&#xA;“usable”). It has been developed and validated against Ubuntu 24.04 LTS as the&#xA;primary reference platform, and cross-tested on Fedora, Debian 12, and Arch&#xA;Linux as well as on traditionally server-oriented distributions like openSUSE&#xA;Leap 15.6, Debian 12, Rocky Linux 9, and Red Hat Enterprise Linux 9 while not&#xA;focussing on those as the guide is created for Linux clients.&lt;/p&gt;</description>
    </item>
    <item>
      <title>When paradigms are shifting: InfoSec in the age of AI</title>
      <link>https://insinuator.net/2026/04/when-paradigms-are-shifting-infosec-in-the-age-of-ai/</link>
      <pubDate>Thu, 30 Apr 2026 00:00:00 +0000</pubDate>
      <guid>https://insinuator.net/2026/04/when-paradigms-are-shifting-infosec-in-the-age-of-ai/</guid>
      <description>&lt;p&gt;Over the last few weeks, I have had a very productive exchange with&#xA;&lt;a href=&#34;https://www.linkedin.com/in/christoph-klaassen-9a4651144/&#34;&gt;Christoph Klaassen&lt;/a&gt;&#xA;on the impact of AI on security governance and compliance. In this post, we&#xA;summarize our thoughts.&lt;/p&gt;</description>
    </item>
    <item>
      <title>Windows Early Boot Configuration: The CmControlVector and PspSystemMitigationOptions</title>
      <link>https://insinuator.net/2026/04/windows-early-boot-configuration-the-cmcontrolvector-and-pspsystemmitigationoptions/</link>
      <pubDate>Mon, 13 Apr 2026 00:00:00 +0000</pubDate>
      <guid>https://insinuator.net/2026/04/windows-early-boot-configuration-the-cmcontrolvector-and-pspsystemmitigationoptions/</guid>
      <description>&lt;p&gt;While investigating how process mitigation settings are initialized, I&#xA;encountered the global variable &lt;code&gt;PspSystemMitigationOptions&lt;/code&gt;. Tracing how this&#xA;value is populated led me to the &lt;code&gt;CmControlVector&lt;/code&gt;. In this blog post, we take a&#xA;look at the Windows kernel land configuration manager, especially its global&#xA;&lt;code&gt;CmControlVector&lt;/code&gt; variable. Quick note: the kernel’s configuration manager is&#xA;not related to Microsoft Intune’s&#xA;&lt;a href=&#34;https://learn.microsoft.com/en-us/intune/configmgr/core/understand/introduction&#34;&gt;Configuration Manager&lt;/a&gt;.&#xA;In short, the configuration manager is responsible for managing and implementing&#xA;the registry. However, it is also responsible for setting up parts of the system&#xA;during early boot.&lt;/p&gt;</description>
    </item>
    <item>
      <title>KubeCon &#43; CloudNativeCon Europe 2026</title>
      <link>https://insinuator.net/2026/04/kubecon--cloudnativecon-europe-2026/</link>
      <pubDate>Wed, 01 Apr 2026 00:00:00 +0000</pubDate>
      <guid>https://insinuator.net/2026/04/kubecon--cloudnativecon-europe-2026/</guid>
      <description>&lt;p&gt;Exactly one week ago, Sven and I had the incredible opportunity to give our very&#xA;first talk at KubeCon + CloudNativeCon&#xA;2026: &lt;a href=&#34;https://kccnceu2026.sched.com/event/2CW2U/how-to-break-multi-tenancy-again-and-again-and-what-we-can-learn-from-it-lorin-lehawany-sven-nobis-ernw?iframe=no&amp;amp;w=100%25&amp;amp;sidebar=yes&amp;amp;bg=no&#34;&gt;How To Break Multi-Tenancy Again and Again …and What We Can Learn From It&lt;/a&gt;.&#xA;We discussed the challenges of namespace-based multi-tenancy and presented&#xA;real-world exploits in&#xA;Kubeflow, &lt;a href=&#34;https://insinuator.net/2026/03/security-considerations-on-istios-crds-with-namespace-based-multi-tenancy/&#34;&gt;Istio&lt;/a&gt;,&#xA;and Traefik that bypass threat boundaries between namespaces and workloads.&#xA;Based on these problems, we developed a methodology to assess and address them.&#xA;You can find the methodology discussed in the talk in&#xA;detail &lt;a href=&#34;https://insinuator.net/2026/03/methodology-for-assessing-namespace-based-multi-tenancy-setups/&#34;&gt;in another blog post&lt;/a&gt; or&#xA;on &lt;a href=&#34;https://github.com/ernw/k8s-multi-tenancy&#34;&gt;GitHub&lt;/a&gt;. You can also find the&#xA;slides &lt;a href=&#34;https://github.com/ernw/k8s-multi-tenancy/blob/main/Slides%20-%20How%20To%20Break%20Multi-Tenancy%20Again%20and%20Again%20...and%20What%20We%20Can%20Learn%20From%20It-%20KubeCon%20+%20CloudNativeCon%20Europe%202026%20-%20final.pdf&#34;&gt;here&lt;/a&gt;.&lt;/p&gt;</description>
    </item>
    <item>
      <title>Methodology for Assessing Kubernetes Namespace-Based Multi-Tenancy Setups</title>
      <link>https://insinuator.net/2026/03/methodology-for-assessing-kubernetes-namespace-based-multi-tenancy-setups/</link>
      <pubDate>Thu, 26 Mar 2026 00:00:00 +0000</pubDate>
      <guid>https://insinuator.net/2026/03/methodology-for-assessing-kubernetes-namespace-based-multi-tenancy-setups/</guid>
      <description>&lt;p&gt;This page introduces our structured methodology for assessing security risks in&#xA;Kubernetes environments that use Namespace-based Multi-Tenancy. It addresses&#xA;weaknesses that break Namespace-based isolation that not well studied, yet. We&#xA;found this issues during our research and presented them together with this&#xA;methodology in our&#xA;&lt;a href=&#34;https://kccnceu2026.sched.com/event/2CW2U/how-to-break-multi-tenancy-again-and-again-and-what-we-can-learn-from-it-lorin-lehawany-sven-nobis-ernw?iframe=yes&amp;amp;w=100%25&amp;amp;sidebar=yes&amp;amp;bg=no&#34;&gt;Talk at KubeCon + CloudNativeCon Europe 2026&lt;/a&gt;.&lt;/p&gt;&#xA;&lt;p&gt;The methodology assumes that industry best practices, such as NetworkPolicies,&#xA;Role-Based Access Control (RBAC), and Pod Security Standards, are already in&#xA;place. These measures provide a necessary baseline level of protection against&#xA;well-known isolation threats. However, they are insufficient to address a class&#xA;of more subtle attack vectors arising from interactions between tenants and&#xA;shared components. Such attack vectors may still compromise the confidentiality,&#xA;integrity, and availability (CIA) of the cluster and its workloads, even in&#xA;well-hardened environments.&lt;/p&gt;</description>
    </item>
    <item>
      <title>Security Considerations on Istio’s CRDs with Namespace-based Multi-Tenancy</title>
      <link>https://insinuator.net/2026/03/security-considerations-on-istios-crds-with-namespace-based-multi-tenancy/</link>
      <pubDate>Wed, 25 Mar 2026 00:00:00 +0000</pubDate>
      <guid>https://insinuator.net/2026/03/security-considerations-on-istios-crds-with-namespace-based-multi-tenancy/</guid>
      <description>&lt;p&gt;We reported a possible Man-in-the-Middle (MitM) attack scenario in which&#xA;a &lt;code&gt;VirtualService&lt;/code&gt; can redirect or intercept traffic within the service mesh.&#xA;This affects Namespace-based Multi-Tenancy clusters where tenants have the&#xA;permissions to deploy Istio resources (&lt;code&gt;networking.istio.io/v1&lt;/code&gt;).&lt;/p&gt;&#xA;&lt;p&gt;In collaboration with Istio, we&#xA;published &lt;a href=&#34;https://istio.io/latest/blog/2026/security-considerations-on-namespace-based-multi-tenancy/&#34;&gt;a guest submission in Istio’s blog&lt;/a&gt; (as&#xA;well as below),&#xA;a &lt;a href=&#34;https://istio.io/latest/news/security/istio-security-2026-002/&#34;&gt;Security Bulletin&lt;/a&gt;,&#xA;and an update to&#xA;their &lt;a href=&#34;https://istio.io/latest/docs/ops/deployment/security-model/#k8s-account-compromise&#34;&gt;Security Model&lt;/a&gt; to&#xA;address this issue.&lt;/p&gt;&#xA;&lt;p&gt;This blog post highlights the risks of using Istio in multi-tenant clusters and&#xA;explains how users can mitigate these risks and safely operate Istio in their&#xA;deployments.&lt;/p&gt;</description>
    </item>
    <item>
      <title>Assessing Endpoint Protection: Our Approach to EDR/XDR and Supplements Evaluation</title>
      <link>https://insinuator.net/2026/03/assessing-endpoint-protection-our-approach-to-edr/xdr-and-supplements-evaluation/</link>
      <pubDate>Thu, 19 Mar 2026 00:00:00 +0000</pubDate>
      <guid>https://insinuator.net/2026/03/assessing-endpoint-protection-our-approach-to-edr/xdr-and-supplements-evaluation/</guid>
      <description>&lt;p&gt;There is a growing landscape of security products promising to protect an&#xA;organization’s IT infrastructure from attacks. Solutions referred to as EDR, and&#xA;sometimes also as XDR, are designed to protect endpoints from all malicious&#xA;activity. The ever-increasing cases of breaches and the associated costs,&#xA;especially in the realm of&#xA;&lt;a href=&#34;https://www.totalassure.com/blog/ransomware-statistics-by-year-2025-comprehensive-report&#34;&gt;ransomware attacks&lt;/a&gt;,&#xA;raise the question of whether there is more that can be done to add an&#xA;additional layer to traditional endpoint protection concepts. That is why a&#xA;customer of ours commissioned us to evaluate whether EDR supplementing solutions&#xA;provide extended protection against ever-evolving threats, as well as to shine a&#xA;light on the performance overheads those solutions might introduce.&lt;/p&gt;</description>
    </item>
    <item>
      <title>Capture Bumble Bluetooth Traffic with Wireshark</title>
      <link>https://insinuator.net/2026/02/capture-bumble-bluetooth-traffic-with-wireshark/</link>
      <pubDate>Wed, 04 Feb 2026 00:00:00 +0000</pubDate>
      <guid>https://insinuator.net/2026/02/capture-bumble-bluetooth-traffic-with-wireshark/</guid>
      <description>&lt;p&gt;When conducting pentests of Bluetooth devices or whilst working on Bluetooth&#xA;related research, we often use &lt;a href=&#34;https://github.com/google/bumble&#34;&gt;Bumble&lt;/a&gt;. In&#xA;this Blogpost I will present a solution to capture a live stream of Bumble&#xA;Bluetooth traffic in Wireshark.&lt;/p&gt;&#xA;&lt;p&gt;Bumble is a fully featured Bluetooth stack, written entirely in Python. What&#xA;makes it extremely powerful for security assessments and research is the level&#xA;of control it provides. It can simulate certain conditions, including errors,&#xA;with a level of precision that most Bluetooth stacks don’t offer. However,&#xA;sometimes you not only need control, you also need visibility.&lt;/p&gt;</description>
    </item>
    <item>
      <title>Incident Response in GCP: Out of Scope – Out of Mind</title>
      <link>https://insinuator.net/2026/01/incident-response-in-gcp-out-of-scope-out-of-mind/</link>
      <pubDate>Tue, 27 Jan 2026 00:00:00 +0000</pubDate>
      <guid>https://insinuator.net/2026/01/incident-response-in-gcp-out-of-scope-out-of-mind/</guid>
      <description>&lt;p&gt;We are regularly offering a&#xA;&lt;a href=&#34;https://hm-ts.de/seminare/courses/google-cloud-gcp-incident-response-analysis-2&#34;&gt;GCP Incident Response and Analysis&lt;/a&gt;&#xA;training. In this training, we analyze resources in GCP cloud together with our&#xA;trainees that were successfully compromised by attackers, e.g., GCE instances&#xA;and Cloud Build projects. Therefore, we need tooling that quickly detects&#xA;misconfiguration of resources that helped the attacker during the compromise.&#xA;During the analysis of different tools and different kinds of misconfiguration&#xA;we realized that GCE instance &lt;em&gt;access scopes&lt;/em&gt; are a blind spot of many (in fact&#xA;all that we tested) security audit tools. In this blog post, we want to&#xA;elaborate on the problems that arise from this behavior.&lt;/p&gt;</description>
    </item>
    <item>
      <title>Bluetooth Headphone Jacking: Full Disclosure of Airoha RACE Vulnerabilities</title>
      <link>https://insinuator.net/2025/12/bluetooth-headphone-jacking-full-disclosure-of-airoha-race-vulnerabilities/</link>
      <pubDate>Sun, 28 Dec 2025 00:00:00 +0000</pubDate>
      <guid>https://insinuator.net/2025/12/bluetooth-headphone-jacking-full-disclosure-of-airoha-race-vulnerabilities/</guid>
      <description>&lt;p&gt;About six months ago we released a&#xA;&lt;a href=&#34;https://insinuator.net/2025/06/airoha-bluetooth-security-vulnerabilities/&#34;&gt;security advisory&lt;/a&gt;&#xA;on this blog about vulnerabilities in Airoha-based Bluetooth headphones and&#xA;earbuds. Back then, we didn’t release all technical details to give vendors more&#xA;time to release updates and users time to patch their devices. Around the time&#xA;of the initial partial disclosure in the beginning of June, Airoha put out an&#xA;SDK release for their customers that mitigates the vulnerabilities. Now, half a&#xA;year later, we finally want to publish the technical details and release a tool&#xA;for researchers and users to continue researching and check whether their&#xA;devices are vulnerable.&lt;/p&gt;</description>
    </item>
    <item>
      <title>Windows Hello for Business – Past and Present Attacks</title>
      <link>https://insinuator.net/2025/06/windows-hello-for-business-past-and-present-attacks/</link>
      <pubDate>Fri, 20 Jun 2025 00:00:00 +0000</pubDate>
      <guid>https://insinuator.net/2025/06/windows-hello-for-business-past-and-present-attacks/</guid>
      <description>&lt;p&gt;Windows Hello for Business is a key component of Microsoft’s passwordless&#xA;authentication strategy. It enables user authentication not only during system&#xA;sign-in but also in conjunction with new and advanced features such as Personal&#xA;Data Encryption, Administrator Protection, and Recall. Rather than depending on&#xA;traditional passwords, Windows Hello leverages a PIN or biometric methods – such&#xA;as fingerprint or facial recognition – to unlock cryptographic keys protected by&#xA;the Trusted Platform Module (TPM).&lt;/p&gt;</description>
    </item>
    <item>
      <title>Using the Raspberry Pi Pico W as a Bluetooth Dongle</title>
      <link>https://insinuator.net/2025/06/using-the-raspberry-pi-pico-w-as-a-bluetooth-dongle/</link>
      <pubDate>Fri, 13 Jun 2025 00:00:00 +0000</pubDate>
      <guid>https://insinuator.net/2025/06/using-the-raspberry-pi-pico-w-as-a-bluetooth-dongle/</guid>
      <description>&lt;p&gt;During our recent research, we experimented with different Bluetooth USB&#xA;dongles. There are tons of options, and sometimes, it’s challenging to determine&#xA;what chipset a dongle actually contains, what Bluetooth features it supports,&#xA;and whether it works on Linux. Inspired by the recent&#xA;&lt;a href=&#34;https://www.tarlogic.com/blog/esp32-hidden-hci-vendor-commands/&#34;&gt;ESP32 Bluetooth research&lt;/a&gt;,&#xA;we wondered whether we could turn our Raspberry Pi Pico Ws into a functioning&#xA;Bluetooth dongle. We had a few lying around, and the advantage here is that we&#xA;know exactly which&#xA;&lt;a href=&#34;https://www.raspberrypi.com/documentation/microcontrollers/pico-series.html&#34;&gt;Bluetooth controller it uses&lt;/a&gt;&#xA;– the Infineon CYW43439. It’s also very easy to get one. You can just buy the&#xA;Pico W for a few bucks, even cheaper than some Bluetooth dongles. You also have&#xA;a controller family that has been researched quite a bit in the&#xA;&lt;a href=&#34;https://github.com/seemoo-lab/internalblue/&#34;&gt;internalblue project&lt;/a&gt;. However,&#xA;there was one disadvantage. We did not find any code that exposes the CYW43439’s&#xA;HCI interface via USB. So we had to write that on our own.&lt;/p&gt;</description>
    </item>
    <item>
      <title>When Your Edge Browser Syncs Private Data to Your Employer</title>
      <link>https://insinuator.net/2025/02/when-your-edge-browser-syncs-private-data-to-your-employer/</link>
      <pubDate>Fri, 07 Feb 2025 00:00:00 +0000</pubDate>
      <guid>https://insinuator.net/2025/02/when-your-edge-browser-syncs-private-data-to-your-employer/</guid>
      <description>&lt;p&gt;Recently, one of our customers contacted us to investigate the extent of some&#xA;unwanted and unexpected behavior regarding browsing data of employees.&lt;/p&gt;&#xA;&lt;p&gt;Employees started contacting IT support because private browser bookmarks,&#xA;private login credentials etc. showed up on their work machines. All affected&#xA;employees stated that they never created these bookmarks on work systems. And&#xA;interestingly, the data seemed to have been collected over quite some time.&lt;/p&gt;&#xA;&lt;p&gt;Our customer wanted to understand how private data ended up in their&#xA;environment. Obviously, private employee data in the enterprise landscape could&#xA;cause some data privacy trouble (GDPR).&lt;/p&gt;</description>
    </item>
    <item>
      <title>Jigsaw RDPuzzle: Piecing Attacker Actions Together</title>
      <link>https://insinuator.net/2025/01/jigsaw-rdpuzzle-piecing-attacker-actions-together/</link>
      <pubDate>Wed, 29 Jan 2025 00:00:00 +0000</pubDate>
      <guid>https://insinuator.net/2025/01/jigsaw-rdpuzzle-piecing-attacker-actions-together/</guid>
      <description>&lt;p&gt;In a recent incident response project, we had the chance to virtually look over&#xA;the attackers’ shoulder and observe their activities. The attackers used the&#xA;Remote Desktop Protocol (RDP) for lateral movement within the compromized&#xA;environment and beyond (MITRE techniques&#xA;&lt;a href=&#34;https://attack.mitre.org/techniques/T1570/&#34;&gt;T1570&lt;/a&gt;,&#xA;&lt;a href=&#34;https://attack.mitre.org/techniques/T1021/001/&#34;&gt;T1021&lt;/a&gt;). As a matter of fact,&#xA;RDP creates cache files that contain tiles of the transferred screen recording&#xA;data. While this fact is well-known and there are existing tools, we found it&#xA;worth reporting because of two different aspects:&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>Announcement: Progress / Kemp LoadMaster CVE-2024-7591</title>
      <link>https://insinuator.net/2024/09/announcement-progress-/-kemp-loadmaster-cve-2024-7591/</link>
      <pubDate>Mon, 09 Sep 2024 00:00:00 +0000</pubDate>
      <guid>https://insinuator.net/2024/09/announcement-progress-/-kemp-loadmaster-cve-2024-7591/</guid>
      <description>&lt;p&gt;Hey everybody,&lt;/p&gt;&#xA;&lt;p&gt;during a recent Red Teaming engagement Marius Walter from &lt;a href=&#34;https://ernw.de/&#34;&gt;ERNW&lt;/a&gt; found a command injection issue in Progress (Kemp) LoadMaster. It was registered as &lt;a href=&#34;https://www.cve.org/CVERecord?id=CVE-2024-7591&#34;&gt;CVE-2024-7591&lt;/a&gt; and scores a CVSS of 10.0.&lt;/p&gt;&#xA;&lt;p&gt;The vendor already has patches out, make sure to apply them as this is a high severe issue. You can find the official announcement and the patch references on the &lt;a href=&#34;https://support.kemptechnologies.com/hc/en-us/articles/29196371689613-LoadMaster-Security-Vulnerability-CVE-2024-7591&#34;&gt;official support page&lt;/a&gt;.&lt;/p&gt;&#xA;&lt;p&gt;Marius will follow up with a technical blog post on this issue once we think everybody had a realistic chance of applying the patches.&lt;/p&gt;</description>
    </item>
    <item>
      <title>CrowdStrike: What is the worldwide BSOD all about?</title>
      <link>https://insinuator.net/2024/08/crowdstrike-what-is-the-worldwide-bsod-all-about/</link>
      <pubDate>Tue, 20 Aug 2024 00:00:00 +0000</pubDate>
      <guid>https://insinuator.net/2024/08/crowdstrike-what-is-the-worldwide-bsod-all-about/</guid>
      <description>&lt;p&gt;&lt;em&gt;This article is about the massive BSOD triggered by CrowdStrike worldwide on July 19. Analysis and information from CrowdStrike or other sources are regularly published, completing what is expressed here. Updates may also be provided in the future.&lt;/em&gt;&lt;/p&gt;&#xA;&lt;p&gt;Friday, July 19, is a day to be remembered in computing history as the day of one of the biggest BSODs (Blue Screens of Death). We have seen air traffic come to a standstill over the USA and people climbing ladders with USB sticks to update giant screens. The impact was still measurable over many days. The question on everyone’s lips is how that all happened. CrowdStrike provided, on a regular basis, an explanation for people to understand what happened. But explanations can be hard to understand, especially for one who would like to read directly within CrowdStrike’s internal wording in their publications and regarding technical driver implementation details. Also, the analysis misses some points we consider relevant for secure software development. This article discusses conclusions from this massive crash, especially the necessity to change our mindset about software. This means we should understand, document, and evaluate independently software provided by vendors to know exactly what we install on our systems and to figure out the risk that may be taken by using the software. The time of naive belief in software magic must end with a third party’s independent review of the software, analysing its reliability, security, and stability. This is an activity we have been doing at ERNW for years, especially for e.g. the German Federal Office for Information Security (BSI)&lt;sup id=&#34;fnref:1&#34;&gt;&lt;a href=&#34;#fn:1&#34; class=&#34;footnote-ref&#34; role=&#34;doc-noteref&#34;&gt;1&lt;/a&gt;&lt;/sup&gt;.&lt;/p&gt;</description>
    </item>
    <item>
      <title>BMBF UNCOVER – Monitoring von Sicherheitsvorfällen in Fahrzeugen</title>
      <link>https://insinuator.net/2024/06/bmbf-uncover-monitoring-von-sicherheitsvorf%C3%A4llen-in-fahrzeugen/</link>
      <pubDate>Fri, 21 Jun 2024 00:00:00 +0000</pubDate>
      <guid>https://insinuator.net/2024/06/bmbf-uncover-monitoring-von-sicherheitsvorf%C3%A4llen-in-fahrzeugen/</guid>
      <description>&lt;h4 id=&#34;english-abstract&#34;&gt;English Abstract&lt;/h4&gt;&#xA;&lt;p&gt;For the realization and introduction of autonomous vehicles, the safe interaction of functions, systems and services as well as their monitoring over the entire product life cycle is essential. An exclusive security-by-design approach is no longer sufficient and must be continuously supported by feedback obtained from in-the-wild operation. This is where the recently successfully completed joint project BMBF UNCOVER comes into play, which targets the requirements of the standards &lt;em&gt;ISO/SAE 21434 (Road vehicles – Cybersecurity engineering)&lt;/em&gt; and &lt;em&gt;ISO 21448 (Road vehicles – Safety of the intended functionality (SOTIF))&lt;/em&gt;.&lt;/p&gt;</description>
    </item>
    <item>
      <title>Linux Character Devices: Exploring systemd-run and pkexec</title>
      <link>https://insinuator.net/2024/05/linux-character-devices-exploring-systemd-run-and-pkexec/</link>
      <pubDate>Tue, 14 May 2024 00:00:00 +0000</pubDate>
      <guid>https://insinuator.net/2024/05/linux-character-devices-exploring-systemd-run-and-pkexec/</guid>
      <description>&lt;p&gt;In this blog post, we quickly look into issues involving character devices. As is typical for Linux, everything is a file, so character devices are referenced as files, such as pseudo terminals (pts) under &lt;code&gt;/dev/pts/&lt;/code&gt;. &lt;code&gt;man pty&lt;/code&gt; briefly introduces the topic. Essentially, it is used to connect a program, such as a terminal emulator, to a shell. In the end, a pty can read and write like a regular file. A colleague already brought up the topic of ptys and character devices. But more recently a &lt;a href=&#34;https://twitter.com/hackerschoice/status/1787601814021361729&#34;&gt;Twitter post&lt;/a&gt; and the &lt;a href=&#34;https://github.com/hackerhouse-opensource/exploits/blob/master/systemd-run-tty.txt&#34;&gt;accompanying advisory&lt;/a&gt; piqued my interest.&lt;/p&gt;</description>
    </item>
    <item>
      <title>Is Google Play Protect a Reliable Malware Detector?</title>
      <link>https://insinuator.net/2024/05/is-google-play-protect-a-reliable-malware-detector/</link>
      <pubDate>Fri, 03 May 2024 00:00:00 +0000</pubDate>
      <guid>https://insinuator.net/2024/05/is-google-play-protect-a-reliable-malware-detector/</guid>
      <description>&lt;p&gt;Google Play Protect is a built-in Android solution that enhances devices’ security. Its main job is to detect and block malware on Android devices. Several malware families were known for bypassing Play Protect checks in recent years. This brings us to an important question: “Is Google Play Protect a Reliable Malware Detector?”. This blog post shows how Play Protect deals with various Android malware in different scenarios. I deal with Play Protect as a black box.&lt;/p&gt;</description>
    </item>
    <item>
      <title>BSI Publishes Windows 10 SiSyPHuS Reports: Application Compatibility Infrastructure, Microsoft Defender Antivirus ETW Usage and Device Setup Manager Service</title>
      <link>https://insinuator.net/2024/04/bsi-publishes-windows-10-sisyphus-reports-application-compatibility-infrastructure-microsoft-defender-antivirus-etw-usage-and-device-setup-manager-service/</link>
      <pubDate>Tue, 16 Apr 2024 00:00:00 +0000</pubDate>
      <guid>https://insinuator.net/2024/04/bsi-publishes-windows-10-sisyphus-reports-application-compatibility-infrastructure-microsoft-defender-antivirus-etw-usage-and-device-setup-manager-service/</guid>
      <description>&lt;p&gt;The German Federal Office for Information Security (BSI – Bundesamt für Sicherheit in der Informationstechnik) has published several papers ERNW created as part of the long-term &lt;a href=&#34;https://www.bsi.bund.de/DE/Service-Navi/Publikationen/Studien/SiSyPHuS_Win10/SiSyPHuS_node.html&#34;&gt;SiSyPHuS Win10-Project&lt;/a&gt;. This project focuses on system analysis of selected parts of the Windows 10 operating system performed by ERNW.&lt;/p&gt;&#xA;&lt;p&gt;&lt;a href=&#34;https://www.bsi.bund.de/DE/Service-Navi/Publikationen/Studien/SiSyPHuS_Win10/AP3/SiSyPHuS_AP3_node.html&#34;&gt;Analysis of the Application Compatibility Infrastructure (ACI)&lt;/a&gt;: In this work we present an overview of the ACI technology along with a technical analysis of the compatibility protocol which is used first to determine if a compatibility solution needs to be applied, and second, to apply said compatibility solution. Furthermore, threats and mitigation in the context of the technology are presented a long with a monitoring approach. Finally, configuration and logging capabilities are discussed.&lt;/p&gt;</description>
    </item>
    <item>
      <title>Considerations on AI-Security – Part I: Introduction and Nondeterminism</title>
      <link>https://insinuator.net/2024/02/considerations-on-ai-security-part-i-introduction-and-nondeterminism/</link>
      <pubDate>Tue, 06 Feb 2024 00:00:00 +0000</pubDate>
      <guid>https://insinuator.net/2024/02/considerations-on-ai-security-part-i-introduction-and-nondeterminism/</guid>
      <description>&lt;p&gt;Hey there!&lt;/p&gt;&#xA;&lt;p&gt;This is the first blog post in a series about issues we think are currently relevant in the field of AI-Security. The intention is not to get full coverage of the topic, but to point out things that seem practical and relevant. We will base some of our statements on lab setups and real-life examples. The technology that we will focus on is chat bots based on generative AI, mainly OpenAI’s ChatGPT. Right now, this specific application of AI in the wild seems to be the best way to demonstrate issues and pitfalls when it comes to IT security.&lt;/p&gt;</description>
    </item>
    <item>
      <title>c0c0n 2023 – A Short Retrospective</title>
      <link>https://insinuator.net/2023/10/c0c0n-2023-a-short-retrospective/</link>
      <pubDate>Tue, 17 Oct 2023 00:00:00 +0000</pubDate>
      <guid>https://insinuator.net/2023/10/c0c0n-2023-a-short-retrospective/</guid>
      <description>&lt;p&gt;Two weeks ago, I was at the &lt;a href=&#34;https://india.c0c0n.org/2023/&#34;&gt;c0c0n&lt;/a&gt; conference in&#xA;Cochin (India). This conference is quite special for at least two&#xA;considerations. At first, this is – to the best of my knowledge – one of the few&#xA;conferences which officially brings together hackers, industrials, politics, and&#xA;security forces. This is not always obvious for all these different persons to&#xA;talk together, may be due to a lack of mutual understanding ?. But for a couple&#xA;of days, all of them meet, talk, exchange, and they share mutual needs and&#xA;appropriate solutions. And this may explain the second consideration, why c0c0n&#xA;is one of the oldest cyber security conferences in India (more than 15 years).&#xA;And yes, this is the conference where police forces directly pick you up from&#xA;the gates of your plane at airport, sitting you at the back of a police car to&#xA;drive you to your hotel with emergency lights ?&lt;/p&gt;</description>
    </item>
    <item>
      <title>Identification of (malicious) modifications in memory-mapped image files</title>
      <link>https://insinuator.net/2023/09/identification-of-malicious-modifications-in-memory-mapped-image-files/</link>
      <pubDate>Wed, 06 Sep 2023 00:00:00 +0000</pubDate>
      <guid>https://insinuator.net/2023/09/identification-of-malicious-modifications-in-memory-mapped-image-files/</guid>
      <description>&lt;p&gt;I’m happy to announce the publication of the paper&#xA;&lt;a href=&#34;https://dfrws.org/wp-content/uploads/2023/07/block-windowsmemoryforensics.pdf&#34;&gt;Windows memory forensics: Identification of (malicious) modifications in memory-mapped image files&lt;/a&gt;&#xA;at this years DFRWS USA, and the release of the corresponding&#xA;&lt;a href=&#34;https://github.com/f-block/volatility-plugins#imgmalfind&#34;&gt;volatility plugin&lt;/a&gt;.&#xA;With this research came also an update to the Ptenum family (affecting&#xA;especially the &lt;code&gt;ptemalfind&lt;/code&gt; plugin), which makes the plugins reliable in&#xA;identifying modified pages despite memory combining, so make sure to grab the&#xA;newest version from the Github repository.&lt;/p&gt;</description>
    </item>
    <item>
      <title>Select * from OpenStack - A Steampipe Plugin for OpenStack</title>
      <link>https://insinuator.net/2023/08/select-from-openstack-a-steampipe-plugin-for-openstack/</link>
      <pubDate>Wed, 02 Aug 2023 00:00:00 +0000</pubDate>
      <guid>https://insinuator.net/2023/08/select-from-openstack-a-steampipe-plugin-for-openstack/</guid>
      <description>&lt;p&gt;Although, more and more companies start to move their IT-Infrastructure from&#xA;on-premise to public cloud solutions like Amazon Web Services (AWS) and&#xA;Microsoft Azure, public cloud providers are not an option for every&#xA;organization. This is where private cloud platforms come into play as they give&#xA;organizations direct control over their information, can be more energy&#xA;efficient than other on-premise hosting solutions, and offer companies the&#xA;possibility to manage their data centers efficiently.&#xA;&lt;a href=&#34;https://www.openstack.org/&#34;&gt;OpenStack&lt;/a&gt; is a widely deployed, open-source&#xA;private cloud platform many companies and universities use.&lt;/p&gt;</description>
    </item>
    <item>
      <title>The DRACO Stream Cipher</title>
      <link>https://insinuator.net/2023/06/the-draco-stream-cipher/</link>
      <pubDate>Wed, 21 Jun 2023 00:00:00 +0000</pubDate>
      <guid>https://insinuator.net/2023/06/the-draco-stream-cipher/</guid>
      <description>&lt;p&gt;In symmetric-key cryptography, we typically distinguish two types of encryption&#xA;schemes: block ciphers and stream ciphers. Block ciphers divide a plaintext into&#xA;blocks of a fixed size (e.g., 64 or 128 bits) and encrypt one such block of data&#xA;as a whole. Stream ciphers, on the other hand, consider the plaintext as a&#xA;continuous stream of data. The stream cipher maintains an internal state and in&#xA;each step it outputs one bit or several bits and updates its internal state. The&#xA;output bit stream is then combined with the plaintext, usually using the XOR&#xA;operation. One advantage of stream ciphers is that their resource requirements&#xA;are lower than those of block ciphers in many application scenarios. This makes&#xA;them particularly useful in lightweight cryptography targeting resource&#xA;constrained devices such as low-cost RFID tags.&lt;/p&gt;</description>
    </item>
    <item>
      <title>IMF Conference 2023 in Munich</title>
      <link>https://insinuator.net/2023/05/imf-conference-2023-in-munich/</link>
      <pubDate>Thu, 25 May 2023 00:00:00 +0000</pubDate>
      <guid>https://insinuator.net/2023/05/imf-conference-2023-in-munich/</guid>
      <description>&lt;p&gt;The IMF Conference is the &lt;em&gt;International Conference on IT Security Incident&#xA;Management &amp;amp; IT Forensics&lt;/em&gt;. This year it took place from May 23 to 24 in Munich.&#xA;The schedule lists&#xA;&lt;a href=&#34;https://imf-conference.org/imf2023/program.html&#34;&gt;a lot of interesting talks&lt;/a&gt;.&#xA;One of the talks was my presentation on a paper about Ceph forensics, based on&#xA;my Master Thesis:&lt;/p&gt;&#xA;&lt;p&gt;The concept of Software Defined Storage (SDS) has become very popular over the&#xA;last few years.  It is used in public, private, and hybrid clouds to store&#xA;enterprise, private, and other kinds of data. &lt;a href=&#34;https://ceph.io/&#34;&gt;Ceph&lt;/a&gt; is an&#xA;open-source software that implements an SDS stack.&lt;/p&gt;</description>
    </item>
    <item>
      <title>AD /Azure Security Track on Troopers 23</title>
      <link>https://insinuator.net/2023/05/ad-/azure-security-track-on-troopers-23/</link>
      <pubDate>Fri, 05 May 2023 00:00:00 +0000</pubDate>
      <guid>https://insinuator.net/2023/05/ad-/azure-security-track-on-troopers-23/</guid>
      <description>&lt;p&gt;&lt;strong&gt;Hi!&lt;/strong&gt;&lt;/p&gt;&#xA;&lt;p&gt;&lt;strong&gt;We’re excited to announce the nearly complete composition of the Active&#xA;Directory &amp;amp; Azure Security Track on Troopers 23 with fantastic speakers!&lt;/strong&gt;&lt;/p&gt;&#xA;&lt;p&gt;Here we go:&lt;/p&gt;&#xA;&lt;p&gt;“&lt;a href=&#34;https://troopers.de/troopers23/talks/ywstkv/&#34;&gt;Dumping NTHashes from Azure AD&lt;/a&gt;”&lt;br&gt;&#xA;(Nestori&#xA;Syynimaa)&lt;/p&gt;&#xA;&lt;p&gt;“&lt;a href=&#34;https://troopers.de/troopers23/talks/33fcyz/&#34;&gt;Hidden Pathways: Exploring the Anatomy of ACL-Based Active Directory Attacks and Building Strong Defenses&lt;/a&gt;”&lt;br&gt;&#xA;(Jonas&#xA;Bülow Knudsen, Alexander Schmitt)&lt;/p&gt;&#xA;&lt;p&gt;“&lt;a href=&#34;https://troopers.de/troopers23/talks/9tqyud/&#34;&gt;Priority for Effective Action – A Practical Model for quantifying the Risk of Active Directory Attacks&lt;/a&gt;”&lt;br&gt;&#xA;(Mars&#xA;Cheng, Dexter Chen)&lt;/p&gt;</description>
    </item>
    <item>
      <title>Hack In The Box Security Conference 2023 @ Amsterdam - Summary</title>
      <link>https://insinuator.net/2023/05/hack-in-the-box-security-conference-2023-@-amsterdam-summary/</link>
      <pubDate>Thu, 04 May 2023 00:00:00 +0000</pubDate>
      <guid>https://insinuator.net/2023/05/hack-in-the-box-security-conference-2023-@-amsterdam-summary/</guid>
      <description>&lt;p&gt;In this blog post, we are sharing summaries of talks from the Hack in the Box&#xA;Conference in Amsterdam (HITBSecConf2023), the final HITB conference in&#xA;Amsterdam. Before we do that, however, we would like to extend a heartfelt thank&#xA;you to the organizers of the conference for putting together such an insightful&#xA;and engaging event.&lt;/p&gt;&#xA;&lt;h2 id=&#34;drbramwell-brizendine--windows-syscalls-in-shellcode-advanced-techniques-for-malicious-functionality&#34;&gt;Dr. Bramwell Brizendine – Windows Syscalls in Shellcode: Advanced Techniques for Malicious Functionality&lt;/h2&gt;&#xA;&lt;p&gt;The talk by Bramwell Brizendine covered the topic of syscall usage in shell&#xA;code. The general idea here is to hide from AV/EDR systems by not using APIs&#xA;such as &lt;code&gt;CreateProcessA&lt;/code&gt;, which may be monitored, but to directly call into the&#xA;corresponding kernel functions. This can be accomplished for example with the&#xA;&lt;em&gt;syscall&lt;/em&gt; CPU instruction (see &lt;sup id=&#34;fnref:1&#34;&gt;&lt;a href=&#34;#fn:1&#34; class=&#34;footnote-ref&#34; role=&#34;doc-noteref&#34;&gt;1&lt;/a&gt;&lt;/sup&gt;, &lt;sup id=&#34;fnref:2&#34;&gt;&lt;a href=&#34;#fn:2&#34; class=&#34;footnote-ref&#34; role=&#34;doc-noteref&#34;&gt;2&lt;/a&gt;&lt;/sup&gt; and &lt;sup id=&#34;fnref:3&#34;&gt;&lt;a href=&#34;#fn:3&#34; class=&#34;footnote-ref&#34; role=&#34;doc-noteref&#34;&gt;3&lt;/a&gt;&lt;/sup&gt; for more information). While&#xA;this technique is not perfectly stealthy and can still be detected (e.g., with a&#xA;kernel driver), it circumvents at least inline-hooks in user space. Another&#xA;downside is the effort of building shell code that directly uses syscalls.&#xA;Besides more overhead in preparing everything for the syscall (for example&#xA;manually creating appropriate structs), the correct syscall ID must be gathered,&#xA;which can change between kernel versions.&lt;/p&gt;</description>
    </item>
    <item>
      <title>Hilarious Buffer Overflow  Mitigation and TCL Injection in CheckPoint Gaia Portal</title>
      <link>https://insinuator.net/2022/12/hilarious-buffer-overflow-mitigation-and-tcl-injection-in-checkpoint-gaia-portal/</link>
      <pubDate>Fri, 16 Dec 2022 00:00:00 +0000</pubDate>
      <guid>https://insinuator.net/2022/12/hilarious-buffer-overflow-mitigation-and-tcl-injection-in-checkpoint-gaia-portal/</guid>
      <description>&lt;p&gt;Hey there,&lt;/p&gt;&#xA;&lt;p&gt;I am going to disclose two bug classes I found a while ago in CheckPoint R77.30:&#xA;Two buffer overflows in the username (no shit) and HTTP method of a request to&#xA;the administrative UI pre-auth and some interesting injections into the TCL web&#xA;interface.&lt;/p&gt;&#xA;&lt;p&gt;Let’s start with the TCL part. The web interface reacted pretty weird when a&#xA;payload contained a colon. Diving deeper into this it became clear that a colon&#xA;would actually cause an error from the TCL interpreter. By going down this&#xA;rabbit hole and learning some TCL (:D) you could see that injecting a colon&#xA;breaks some part of the application code, probably because colons are control&#xA;characters in TCL e.g. preceding a global variable in TCL (::MyVar) or&#xA;separating namespaces.&lt;/p&gt;</description>
    </item>
    <item>
      <title>Spymax: The android RAT and it works like that</title>
      <link>https://insinuator.net/2022/09/spymax-the-android-rat-and-it-works-like-that/</link>
      <pubDate>Wed, 07 Sep 2022 00:00:00 +0000</pubDate>
      <guid>https://insinuator.net/2022/09/spymax-the-android-rat-and-it-works-like-that/</guid>
      <description>&lt;p&gt;Spymax is a mobile Remote Administration Tool (RAT) that enables an attacker to&#xA;control victims’ devices through an Android malware. Once the malware is&#xA;installed on a phone, the attacker can execute many attacks that highly impact&#xA;the confidentiality and integrity of the victim’s data, as well as the victim’s&#xA;privacy. It is powerful, widely available, and does not require root privileges&#xA;on the victim’s device. In this blogpost, I show the capabilities of this RAT&#xA;and analyze how its Android malware works.&lt;/p&gt;</description>
    </item>
    <item>
      <title>Whitepaper Endpoint Management &amp;amp; Monitoring Solutions Released</title>
      <link>https://insinuator.net/2022/08/whitepaper-endpoint-management-amp-monitoring-solutions-released/</link>
      <pubDate>Wed, 10 Aug 2022 00:00:00 +0000</pubDate>
      <guid>https://insinuator.net/2022/08/whitepaper-endpoint-management-amp-monitoring-solutions-released/</guid>
      <description>&lt;p&gt;Over the course of the last 2 years we performed vulnerability research on&#xA;several Endpoint Management &amp;amp; Monitoring Solutions. The results were already&#xA;partially presented in security advisories which were published on this blog&#xA;during the last two years. The advisories can be found here:&lt;/p&gt;&#xA;&lt;ul&gt;&#xA;&lt;li&gt;&lt;a href=&#34;https://insinuator.net/2020/06/security-advisories-for-ivanti-dsm-suite/&#34;&gt;Ivanti DSM Suite&lt;/a&gt;&lt;/li&gt;&#xA;&lt;li&gt;&lt;a href=&#34;https://insinuator.net/2020/12/security-advisories-for-solarwinds-n-central/&#34;&gt;Solarwinds N-Central&lt;/a&gt;&lt;/li&gt;&#xA;&lt;li&gt;&lt;a href=&#34;https://insinuator.net/2020/07/security-advisories-for-nagios-xi/&#34;&gt;Nagios XI&lt;/a&gt;&lt;/li&gt;&#xA;&lt;li&gt;&lt;a href=&#34;https://insinuator.net/2022/06/security-advisories-for-broadcom-automic-automation-uc4/&#34;&gt;Broadcom Automic Automation (UC4)&lt;/a&gt;&lt;/li&gt;&#xA;&lt;/ul&gt;&#xA;&lt;p&gt;We also recently presented the results on&#xA;&lt;a href=&#34;https://troopers.de/troopers22/agenda/tr22-1088-a-vulnerability-analysis-of-endpoint-management-monitoring-solutions/&#34;&gt;Troopers 2022&lt;/a&gt;.&#xA;Now the results have been published in a more in-depth manner in the form of a&#xA;technical whitepaper. The whitepaper can be found&#xA;&lt;a href=&#34;https://ernw.de/en/whitepapers/issue-72.html&#34;&gt;here&lt;/a&gt;.&lt;/p&gt;</description>
    </item>
    <item>
      <title>Security Advisories for Broadcom Automic Automation (UC4)</title>
      <link>https://insinuator.net/2022/06/security-advisories-for-broadcom-automic-automation-uc4/</link>
      <pubDate>Thu, 09 Jun 2022 00:00:00 +0000</pubDate>
      <guid>https://insinuator.net/2022/06/security-advisories-for-broadcom-automic-automation-uc4/</guid>
      <description>&lt;h2 id=&#34;updated-on-200622-with-cves-and-link-to-broadcom-security-notice&#34;&gt;Updated on 20.06.22 with CVEs and link to Broadcom Security Notice.&lt;/h2&gt;&#xA;&lt;p&gt;In April 2021 we reported seven vulnerabilities in Broadcom Automic Automation&#xA;(UC4) 12.3.5+hf.3. CVE IDs were assigned on 16.06.22, the corresponding Broadcom&#xA;Security Notice can be found&#xA;&lt;a href=&#34;https://support.broadcom.com/web/ecx/support-content-notification/-/external/content/SecurityAdvisories/0/20629&#34;&gt;here&lt;/a&gt;.&lt;/p&gt;&#xA;&lt;p&gt;The vulnerabilities have been found in the course of a research project, in&#xA;which we analyzed the security of multiple Endpoint Management solutions.&#xA;Similar vulnerabilities have been found in other solutions as we pointed out in&#xA;previous posts about the&#xA;&lt;a href=&#34;https://insinuator.net/2020/06/security-advisories-for-ivanti-dsm-suite/&#34;&gt;Ivanti DSM Suite&lt;/a&gt;,&#xA;&lt;a href=&#34;https://insinuator.net/2020/07/security-advisories-for-nagios-xi/&#34;&gt;Nagios XI&lt;/a&gt;,&#xA;and&#xA;&lt;a href=&#34;https://insinuator.net/2020/12/security-advisories-for-solarwinds-n-central/&#34;&gt;Solarwinds N-Central&lt;/a&gt;. &#xA;The outcome of the research project will be published as a whitepaper and a&#xA;conference talk at&#xA;&lt;a href=&#34;https://troopers.de/troopers22/talks/brzgam/&#34;&gt;Troopers 2022&lt;/a&gt;.&lt;/p&gt;</description>
    </item>
    <item>
      <title>Solving client-side controls once and for all</title>
      <link>https://insinuator.net/2022/04/solving-client-side-controls-once-and-for-all/</link>
      <pubDate>Fri, 01 Apr 2022 00:00:00 +0000</pubDate>
      <guid>https://insinuator.net/2022/04/solving-client-side-controls-once-and-for-all/</guid>
      <description>&lt;p&gt;Missing server-side validation consistently scores a place in the&#xA;&lt;a href=&#34;https://owasp.org/www-project-top-ten/&#34;&gt;OWASP Top 10&lt;/a&gt;. Browsers nowadays offer&#xA;a lot of ways to easily implement client-side controls, increasing the usability&#xA;by a lot. They automatically detect missing fields or invalid characters in your&#xA;input fields and may even validate user input against a regular expressions.&lt;/p&gt;&#xA;&lt;p&gt;However, these controls should only be considered as usability features. When&#xA;sending data to a back-end system the application must always ensure data&#xA;integrity by implementing encodings, validations and filters. Even for small&#xA;applications this is a painful and tedious process. For each possible input,&#xA;developers together with security experts have to carefully identify the context&#xA;of each field, how the input is going to be used and what data requirements are&#xA;present.&lt;/p&gt;</description>
    </item>
    <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>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>Analysis of HSTS Caches of Different Browsers</title>
      <link>https://insinuator.net/2021/05/analysis-of-hsts-caches-of-different-browsers/</link>
      <pubDate>Thu, 06 May 2021 00:00:00 +0000</pubDate>
      <guid>https://insinuator.net/2021/05/analysis-of-hsts-caches-of-different-browsers/</guid>
      <description>&lt;p&gt;I recently stumbled upon a strange behavior in my Firefox: I visited an&#xA;HTTPS-enabled website that I had visited before and saw that my Firefox&#xA;connected insecurely via HTTP. I found that strange because nowadays, most&#xA;websites set the&#xA;&lt;a href=&#34;https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/Strict-Transport-Security&#34;&gt;HSTS&lt;/a&gt;&#xA;header, which is supposed to force the browser to connect via HTTPS. I checked&#xA;whether this website set the HSTS header – and it did. This means my Firefox was&#xA;ignoring/forgetting about the HSTS header right after my visit.&lt;/p&gt;</description>
    </item>
    <item>
      <title>Attack llvmpipe Graphics Driver from Chromium</title>
      <link>https://insinuator.net/2021/05/attack-llvmpipe-graphics-driver-from-chromium/</link>
      <pubDate>Tue, 04 May 2021 00:00:00 +0000</pubDate>
      <guid>https://insinuator.net/2021/05/attack-llvmpipe-graphics-driver-from-chromium/</guid>
      <description>&lt;p&gt;In this post, we are discussing a bug we came across in Mesas llvmpipe Gallium3D&#xA;graphics driver. This bug was accessible through Chromium’s WebGL implementation&#xA;and can provide control of the program counter (pc) within Chromium’s GPU&#xA;process if llvmpipe is used. Llvmpipe is a software rasterizer that is used on&#xA;Linux if no hardware acceleration (graphics card) is available. This is a pretty&#xA;rare edge case as llvmpipe has no widespread use. An estimate by Google is that&#xA;approx 0.06% of the Chromium users are affected by this. However, as this is a&#xA;simple but valid Chromium bug, we want to give you a quick walkthrough. The&#xA;issue is tracked as&#xA;&lt;a href=&#34;https://bugs.chromium.org/p/chromium/issues/detail?id=1155974&#34;&gt;CVE-2021-21153&lt;/a&gt;&#xA;and was fixed in February 2020.&lt;/p&gt;</description>
    </item>
    <item>
      <title>DogWhisperer&#39;s SharpHound Cheat Sheet</title>
      <link>https://insinuator.net/2021/05/dogwhisperers-sharphound-cheat-sheet/</link>
      <pubDate>Tue, 04 May 2021 00:00:00 +0000</pubDate>
      <guid>https://insinuator.net/2021/05/dogwhisperers-sharphound-cheat-sheet/</guid>
      <description>&lt;p&gt;BloodHound data collection, aka &lt;strong&gt;Sharphound&lt;/strong&gt;, is quite a complex beast.&lt;br&gt;&#xA;When giving BloodHound workshops, the part where I get the most questions is&#xA;always data collection.&lt;br&gt;&#xA;How is the BloodHound data collected? &lt;strong&gt;What methods do what?&lt;/strong&gt; Who am I talking&#xA;to? How do I fly under the radar?&lt;/p&gt;&#xA;&lt;p&gt;These are all very relevant questions when you think about it.&lt;br&gt;&#xA;After all, the rest is just a gorgeous UI sitting on top of a cool data model,&#xA;but the only bit of BloodHound code that ever touches the targeted network is&#xA;SharpHound. And so questions about it should be mandatory.&lt;br&gt;&#xA;Now even thought I’ve been working with BloodHound for quite a while, there is&#xA;always this moment where I have to check before answering… (I feel the older I&#xA;get, the quicker I understand, but the less I remember… but that’s another story&#xA;I guess…)&lt;/p&gt;</description>
    </item>
    <item>
      <title>BSI veröffentlicht Hardening Guide, Protokollierungs-Empfehlung und zugehörige GPOs für Windows 10 im Rahmen der SiSyPHuS-Studie</title>
      <link>https://insinuator.net/2021/05/bsi-ver%C3%B6ffentlicht-hardening-guide-protokollierungs-empfehlung-und-zugeh%C3%B6rige-gpos-f%C3%BCr-windows-10-im-rahmen-der-sisyphus-studie/</link>
      <pubDate>Mon, 03 May 2021 00:00:00 +0000</pubDate>
      <guid>https://insinuator.net/2021/05/bsi-ver%C3%B6ffentlicht-hardening-guide-protokollierungs-empfehlung-und-zugeh%C3%B6rige-gpos-f%C3%BCr-windows-10-im-rahmen-der-sisyphus-studie/</guid>
      <description>&lt;p&gt;Wir freuen uns, dass das Bundesamt für Sicherheit in der Informationstechnik&#xA;(BSI) im Rahmen des gemeinsam mit ERNW durchgeführten SiSyPHuS Win10-Projekts&#xA;(&lt;strong&gt;S&lt;/strong&gt;tud&lt;strong&gt;i&lt;/strong&gt;e zu &lt;strong&gt;Sy&lt;/strong&gt;stemintegrität, &lt;strong&gt;P&lt;/strong&gt;rotokollierung, &lt;strong&gt;H&lt;/strong&gt;ärtung&#xA;&lt;strong&gt;u&lt;/strong&gt;nd &lt;strong&gt;S&lt;/strong&gt;icherheitsfunktionen in Windows 10) heute (ca. 10 Uhr) die nächsten&#xA;drei Arbeitspakete veröffentlicht:&lt;/p&gt;&#xA;&lt;ul&gt;&#xA;&lt;li&gt;Empfehlung zur Härtung von Windows 10 mit Bordmitteln&lt;/li&gt;&#xA;&lt;li&gt;Empfehlung zur Konfiguration der Protokollierung in Windows 10&lt;/li&gt;&#xA;&lt;li&gt;Gruppenrichtlinien zu den Konfigurationsempfehlungen für Härtung und&#xA;Protokollierung für Windows 10&lt;/li&gt;&#xA;&lt;/ul&gt;&#xA;&lt;p&gt;In den Dokumenten finden sich unterschiedliche Empfehlungen für&#xA;Domänenmitglieder (mit normalem und mit hohem Schutzbedarf) und&#xA;Einzelplatzrechner. Die Dokumente bauen auf den Empfehlungen von Microsofts&#xA;Security Baseline und dem CIS Benchmark für Windows 10 auf und ergänzen diese in&#xA;von Microsoft und CIS nicht betrachteten Bereichen oder modifizieren sie dort,&#xA;wo es aus Erfahrung von ERNW im Hardening von Windows-Systemen sinnvoll ist.&lt;/p&gt;</description>
    </item>
    <item>
      <title>Of Corona, Buggy Audio Drivers and Industrial Espionage</title>
      <link>https://insinuator.net/2021/04/of-corona-buggy-audio-drivers-and-industrial-espionage/</link>
      <pubDate>Fri, 23 Apr 2021 00:00:00 +0000</pubDate>
      <guid>https://insinuator.net/2021/04/of-corona-buggy-audio-drivers-and-industrial-espionage/</guid>
      <description>&lt;h2 id=&#34;the-situation&#34;&gt;The Situation&lt;/h2&gt;&#xA;&lt;p&gt;Last year, the CISO of a customer sent me a laptop for analysis. The reason was&#xA;that he feared the company could have been victim of industrial espionage.&#xA;Starting in spring 2020, the IT help desk got several employee laptops with full&#xA;hard drives, caused by a huge amount of audio recordings. The audio files&#xA;contained recordings even of highly sensitive telephone conferences. An&#xA;automated scan on all employee computers for such audio recordings showed that&#xA;about 300 devices were affected.&lt;/p&gt;</description>
    </item>
    <item>
      <title>fpicker: Fuzzing with Frida</title>
      <link>https://insinuator.net/2021/03/fpicker-fuzzing-with-frida/</link>
      <pubDate>Mon, 15 Mar 2021 00:00:00 +0000</pubDate>
      <guid>https://insinuator.net/2021/03/fpicker-fuzzing-with-frida/</guid>
      <description>&lt;h2 id=&#34;introduction&#34;&gt;Introduction&lt;/h2&gt;&#xA;&lt;p&gt;In this post, I will introduce fpicker. Fpicker is a Frida-based&#xA;coverage-guided, mostly in-process, blackbox fuzzing suite. Its most significant&#xA;feature is the AFL++ proxy mode which enables blackbox in-process fuzzing with&#xA;AFL++ on platforms supported by Frida. In practice, this means that fpicker&#xA;enables fuzzing binary-only targets with AFL++ on potentially any system that is&#xA;supported by Frida. For example, it allows fuzzing a user-space application on&#xA;the iOS operating system, such as the Bluetooth daemon bluetoothd – which was&#xA;part of the original motivation to implement fpicker.&lt;/p&gt;</description>
    </item>
    <item>
      <title>ERNW Whitepaper 71: Analysis of Anti-Virus Software Quarantine Files</title>
      <link>https://insinuator.net/2021/01/ernw-whitepaper-71-analysis-of-anti-virus-software-quarantine-files/</link>
      <pubDate>Wed, 27 Jan 2021 00:00:00 +0000</pubDate>
      <guid>https://insinuator.net/2021/01/ernw-whitepaper-71-analysis-of-anti-virus-software-quarantine-files/</guid>
      <description>&lt;p&gt;I am glad to announce the release of the ERNW whitepaper 71 containing&#xA;information about quarantine file formats of different AV software vendors. It&#xA;is available&#xA;&lt;a href=&#34;https://static.ernw.de/whitepaper/ERNW-Whitepaper-71_AV_Quarantine_signed.pdf&#34;&gt;here&lt;/a&gt;.&lt;/p&gt;&#xA;&lt;h2 id=&#34;anti-virus-software&#34;&gt;Anti-Virus Software&lt;/h2&gt;&#xA;&lt;p&gt;I took quarantine files from real-life incidents and created some in a lab&#xA;environment. Afterwards I tried to identify metadata, like timestamps, path&#xA;names, malware names, and the actual malicious file in the quarantine files. One&#xA;goal was to use this information to support our incident analyses: Using the&#xA;results, we can now easily create timelines showing information about&#xA;quarantined files, extract the detected malware, and sometimes even find&#xA;information about processes that created the malicious files.&lt;/p&gt;</description>
    </item>
    <item>
      <title>Having Fun with Google MDM Solution</title>
      <link>https://insinuator.net/2021/01/having-fun-with-google-mdm-solution/</link>
      <pubDate>Thu, 21 Jan 2021 00:00:00 +0000</pubDate>
      <guid>https://insinuator.net/2021/01/having-fun-with-google-mdm-solution/</guid>
      <description>&lt;p&gt;It’s Friday, you managed to escape for a couple of hours from a busy working day&#xA;to see a doctor. Now you have to wait in a boring waiting room at the clinic&#xA;until it’s your turn to see her majesty. What would you like to do in this time?&#xA;Answer pending business emails, get lost in social media, or choose a new theme&#xA;to make your iPhone look awesome?  What about: all of the above? It’s nice to&#xA;have everything on your iPhone: MDM enrollment to access business data, in&#xA;addition to jailbreak for device freedom. However, MDM solutions ban jailbroken&#xA;devices, because they are not secure enough to handle sensitive business data.&#xA;And so, cat and mouse games of jailbreak detection/bypass between MDM solutions&#xA;and some users develop.&lt;/p&gt;</description>
    </item>
    <item>
      <title>Pentesting the ELK Stack</title>
      <link>https://insinuator.net/2021/01/pentesting-the-elk-stack/</link>
      <pubDate>Wed, 13 Jan 2021 00:00:00 +0000</pubDate>
      <guid>https://insinuator.net/2021/01/pentesting-the-elk-stack/</guid>
      <description>&lt;p&gt;With this blog post, I will provide information on how to proceed when testing&#xA;ELK Stack landscapes. Information regarding the exploitation of the ELK Stack is&#xA;very rare on the internet. Therefore, following article aims to provide you with&#xA;some approaches that can be useful during a penetration test.&lt;/p&gt;&#xA;&lt;p&gt;&lt;strong&gt;Disclaimer:&lt;/strong&gt;&lt;/p&gt;&#xA;&lt;p&gt;All information below were collected during a research project and there is no&#xA;claim for completeness. The guide focuses on ELK Stack deployments for Linux&#xA;machines. Further, this article does not include information for identifying&#xA;misconfigurations in a white-box configuration audit.&lt;/p&gt;</description>
    </item>
    <item>
      <title>Root Cause Analysis of a Heap-Based Buffer Overflow in GNU Readline</title>
      <link>https://insinuator.net/2020/12/root-cause-analysis-of-a-heap-based-buffer-overflow-in-gnu-readline/</link>
      <pubDate>Thu, 17 Dec 2020 00:00:00 +0000</pubDate>
      <guid>https://insinuator.net/2020/12/root-cause-analysis-of-a-heap-based-buffer-overflow-in-gnu-readline/</guid>
      <description>&lt;p&gt;In the &lt;a href=&#34;https://insinuator.net/2020/12/how-fuzzers-decide-if-a-crash-is-unique/&#34;&gt;last blog post&lt;/a&gt;, we discussed how fuzzers determine the uniqueness of a crash. In this blog post, we discuss how we can manually triage a crash and determine the root cause. As an example, we use a heap-based buffer overflow I found in GNU readline 8.1 rc2, which has been fixed in the newest release. We use GDB and rr for time-travel debugging to determine the root cause of the bug.&lt;/p&gt;</description>
    </item>
    <item>
      <title>Security Advisories for SolarWinds N-Central</title>
      <link>https://insinuator.net/2020/12/security-advisories-for-solarwinds-n-central/</link>
      <pubDate>Thu, 10 Dec 2020 00:00:00 +0000</pubDate>
      <guid>https://insinuator.net/2020/12/security-advisories-for-solarwinds-n-central/</guid>
      <description>&lt;p&gt;In August 2020 we reported six vulnerabilities in SolarWinds N-Central 12.3.0.670 to the vendor.&lt;/p&gt;&#xA;&lt;p&gt;The following CVE IDs were assigned to the issues :&lt;/p&gt;&#xA;&lt;ul&gt;&#xA;&lt;li&gt;CVE-2020-25617: RCE in N-Central Administration Console (AdvancedScripts Endpoint)&lt;/li&gt;&#xA;&lt;li&gt;CVE-2020-25618: Local Privilege Escalation from nable User to root (N-Central Backend Server)&lt;/li&gt;&#xA;&lt;li&gt;CVE-2020-25619: Access to Internal Services through SSH Port Forwarding (N-Central Backend Server)&lt;/li&gt;&#xA;&lt;li&gt;CVE-2020-25620: SolarWinds Support Account with Default Credentials&lt;/li&gt;&#xA;&lt;li&gt;CVE-2020-25621: Local Database does not require Authentication (N-Central Backend Server)&lt;/li&gt;&#xA;&lt;li&gt;CVE-2020-25622: CSRF in N-Central Administration Console (AdvancedScripts Endpoint)&lt;/li&gt;&#xA;&lt;/ul&gt;&#xA;&lt;p&gt;The vulnerabilities have been found in the course of an extensive research project, in which we analyze the security of multiple Unified Endpoint Management (UEM) solutions. Similar vulnerabilities have been found in other solutions as we pointed out in previous posts about the &lt;a href=&#34;https://insinuator.net/2020/06/security-advisories-for-ivanti-dsm-suite/&#34;&gt;Ivanti DSM Suite&lt;/a&gt; and &lt;a href=&#34;https://insinuator.net/2020/07/security-advisories-for-nagios-xi/&#34;&gt;Nagios XI&lt;/a&gt;. The final outcome of the research project will be published as a whitepaper and possibly conference talk as soon as the project including all disclosure processes concludes.&lt;/p&gt;</description>
    </item>
    <item>
      <title>How Fuzzers Decide if a Crash is Unique</title>
      <link>https://insinuator.net/2020/12/how-fuzzers-decide-if-a-crash-is-unique/</link>
      <pubDate>Thu, 03 Dec 2020 00:00:00 +0000</pubDate>
      <guid>https://insinuator.net/2020/12/how-fuzzers-decide-if-a-crash-is-unique/</guid>
      <description>&lt;p&gt;This blogpost sheds some light on how fuzzers handle crash deduplication and what a unique crash is for a fuzzer. For this, we take a look at two contrived examples and compare the unique crashes identified by &lt;a href=&#34;https://github.com/AFLplusplus/AFLplusplus&#34;&gt;AFL++&lt;/a&gt; and &lt;a href=&#34;https://github.com/google/honggfuzz&#34;&gt;honggfuzz&lt;/a&gt;.&lt;/p&gt;&#xA;&lt;p&gt;Both examples are similar. They read from STDIN, check if the first character of the read data is a digit, then call a vulnerable function. The main difference in &lt;a href=&#34;https://gist.github.com/murx-/5c490c14f4ea994dd7e8bf6d49fdb3b2&#34;&gt;test1.c&lt;/a&gt; is that the program crashes directly in the vuln function due to a null pointer dereference. In &lt;a href=&#34;https://gist.github.com/murx-/98adcbf98806dbe237dc0bff6e03ce6c&#34;&gt;test2.c&lt;/a&gt;, a previously allocated buffer is freed; this buffer is again freed at the end of main, resulting in libc identifying the double free and raising a sigabort.&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>Microsoft Office Telemetry: Report Release</title>
      <link>https://insinuator.net/2020/11/microsoft-office-telemetry-report-release/</link>
      <pubDate>Tue, 17 Nov 2020 00:00:00 +0000</pubDate>
      <guid>https://insinuator.net/2020/11/microsoft-office-telemetry-report-release/</guid>
      <description>&lt;p&gt;The &lt;a href=&#34;https://www.bsi.bund.de/&#34;&gt;German Federal Office for Information Security&lt;/a&gt; (orig., ger., Bundesamt für Sicherheit in der Informationstechnik – BSI) has published our report on Microsoft Office Telemetry.&lt;/p&gt;&#xA;&lt;p&gt;Microsoft has released a set of &lt;a href=&#34;https://docs.microsoft.com/en-us/deployoffice/privacy/manage-privacy-controls&#34;&gt;privacy settings&lt;/a&gt; for Office, one of which enables users to configure the type and amount of diagnostic (i.e., telemetry) data that Office may send to Microsoft. When deployed, it is available in the form of a group policy setting. It allows users to configure one of the following diagnostic data levels: &lt;em&gt;required&lt;/em&gt;, &lt;em&gt;optional&lt;/em&gt;, or &lt;em&gt;neither&lt;/em&gt;.  The report we produced:&lt;/p&gt;</description>
    </item>
    <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>Apps on Prescription?! – Perspectives on Digital Health Applications (DiGA)</title>
      <link>https://insinuator.net/2020/11/apps-on-prescription-perspectives-on-digital-health-applications-diga/</link>
      <pubDate>Thu, 05 Nov 2020 00:00:00 +0000</pubDate>
      <guid>https://insinuator.net/2020/11/apps-on-prescription-perspectives-on-digital-health-applications-diga/</guid>
      <description>&lt;p&gt;Some time ago, we carried out an evaluation of the &lt;em&gt;Digital Health Applications Ordinance&lt;/em&gt; (Digitale-Gesundheitsanwendungen-Verordnung, DiGAV) for the &lt;em&gt;Federal Chamber of Psychotherapists in Germany&lt;/em&gt; (Bundespsychotherapeutenkammer, BPtK) focusing on the security of digital health applications, often referred to as &lt;em&gt;apps on prescription&lt;/em&gt;.&lt;/p&gt;&#xA;&lt;p&gt;The audit was intended to determine to which extent security guidelines, security objectives, and best practices are adhered to by the requirements formulated by the ordinance, thus enabling the foundations to securely operate digital health applications. The main subject of the examination is whether requirements, including procedural requirements defined in the ordinance are sufficient to ensure security of digital health applications. The examination has shown that the requirements can be seen as positive. However, in order to be able to make reliable statements about the IT security of digital healthcare applications, further details and mechanisms should be clarified within the ordinance, which I would like to present in the following.&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>How can data from fitness trackers be obtained and analyzed with a forensic approach?</title>
      <link>https://insinuator.net/2020/09/how-can-data-from-fitness-trackers-be-obtained-and-analyzed-with-a-forensic-approach/</link>
      <pubDate>Thu, 10 Sep 2020 00:00:00 +0000</pubDate>
      <guid>https://insinuator.net/2020/09/how-can-data-from-fitness-trackers-be-obtained-and-analyzed-with-a-forensic-approach/</guid>
      <description>&lt;p&gt;The use of Internet of Things devices is continuously increasing: People buy devices, such as smart assistants, to make their lives more comfortable or fitness trackers to assess sports activities. According to the Pew Research Center [1], every fifth American wears a device to track their fitness. In Germany, the number increases likewise. The increasing number of fitness trackers in use can also be seen in criminal proceedings, as there exist more and more cases where these devices provide evidence.&lt;/p&gt;</description>
    </item>
    <item>
      <title>Puppet Assessment Techniques</title>
      <link>https://insinuator.net/2020/09/puppet-assessment-techniques/</link>
      <pubDate>Wed, 09 Sep 2020 00:00:00 +0000</pubDate>
      <guid>https://insinuator.net/2020/09/puppet-assessment-techniques/</guid>
      <description>&lt;p&gt;Hardening guides for different systems that can be managed by Puppet are easy to find, but not the guides for hardening Puppet itself.&lt;/p&gt;&#xA;&lt;p&gt;The enterprise software configuration management (SCM) tool &lt;a href=&#34;https://puppet.com&#34;&gt;Puppet&lt;/a&gt; is valued by many SysAdmins and DevOps, e.g. at &lt;a href=&#34;https://cloud.google.com/blog/products/gcp/introducing-puppet-support-for-google-cloud-platform24&#34;&gt;Google&lt;/a&gt;, for scalable, continuous and secure deployment of application server configuration files across large heterogeneous system landscapes and increasingly also as “&lt;a href=&#34;https://puppet.com/blog/enforcing-cis-compliance-with-puppet/&#34;&gt;end-to-end&lt;/a&gt;” compliance solution.&lt;/p&gt;&#xA;&lt;p&gt;&lt;strong&gt;Disclaimer:&lt;/strong&gt;&lt;br&gt;&#xA;This blog post does not present anything new about Puppet security, but aims to raise security awareness and summarize useful attack and audit techniques for an internal black and whitebox infrastructure assessment of a Puppet Enterprise landscape.&lt;br&gt;&#xA;Most information in this post were collected during and based-on a time-limited graybox Puppet landscape assessment (Puppet Enterprise version 6.4.0, on RHEL7).&lt;br&gt;&#xA;Hence, there is no claim for completeness and the post shall not be considered as a fully fledged Puppet hardening guide.&lt;/p&gt;</description>
    </item>
    <item>
      <title>Java Buffer Overflow with ByteBuffer (CVE-2020-2803) and Mutable MethodType (CVE-2020-2805) Sandbox Escapes</title>
      <link>https://insinuator.net/2020/09/java-buffer-overflow-with-bytebuffer-cve-2020-2803-and-mutable-methodtype-cve-2020-2805-sandbox-escapes/</link>
      <pubDate>Wed, 02 Sep 2020 00:00:00 +0000</pubDate>
      <guid>https://insinuator.net/2020/09/java-buffer-overflow-with-bytebuffer-cve-2020-2803-and-mutable-methodtype-cve-2020-2805-sandbox-escapes/</guid>
      <description>&lt;p&gt;Years ago, Java could be used on websites trough applets. To make these applets secure and not let them access files or do other dangerous stuff, Java introduced the SecurityManager. Before some action was performed, the SecurityManager was asked if the code is privileged to perform this action. However, since the SecurityManager lives in the same running program and can be accessed via System.getSecurityManager(), there &lt;a href=&#34;http://www.phrack.org/papers/escaping_the_java_sandbox.html&#34;&gt;existed some ways to remove it&lt;/a&gt;.&lt;/p&gt;</description>
    </item>
    <item>
      <title>Security Advisories for Nagios XI</title>
      <link>https://insinuator.net/2020/07/security-advisories-for-nagios-xi/</link>
      <pubDate>Thu, 30 Jul 2020 00:00:00 +0000</pubDate>
      <guid>https://insinuator.net/2020/07/security-advisories-for-nagios-xi/</guid>
      <description>&lt;p&gt;In June 2020 we reported three vulnerabilities in Nagios XI 5.7.1 to the vendor.&lt;br&gt;&#xA;The following CVE IDs were assigned to the issues :&lt;/p&gt;&#xA;&lt;ul&gt;&#xA;&lt;li&gt; CVE-2020-15901: Command Injection in Nagios XI web interface (RCE)&lt;/li&gt;&#xA;&lt;li&gt; CVE-2020-15902: Cross Site Scripting (XSS)&lt;/li&gt;&#xA;&lt;li&gt; CVE-2020-15903: Reserved, details will be given on vendor fix&lt;/li&gt;&#xA;&lt;/ul&gt;&#xA;&lt;p&gt;CVE-2020-15901 and CVE-2020-15902 have meanwhile been fixed in version 5.7.2 according to the changelog on the Nagios website (&lt;a href=&#34;https://www.nagios.com/downloads/nagios-xi/change-log/)&#34;&gt;https://www.nagios.com/downloads/nagios-xi/change-log/)&lt;/a&gt;. CVE-2020-15903 is currently being worked on by the vendor and will probably be fixed in the near future.&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>Security Advisories for Ivanti DSM Suite</title>
      <link>https://insinuator.net/2020/06/security-advisories-for-ivanti-dsm-suite/</link>
      <pubDate>Tue, 23 Jun 2020 00:00:00 +0000</pubDate>
      <guid>https://insinuator.net/2020/06/security-advisories-for-ivanti-dsm-suite/</guid>
      <description>&lt;p&gt;From the end of 2019 on, we reported two critical vulnerabilities in the Ivanti DSM Suite to the vendor. The following CVE IDs were assigned to the issues (but note that they have a status of RESERVED, i.e. titles and descriptions may change in the future):&lt;/p&gt;&#xA;&lt;ul&gt;&#xA;&lt;li&gt;CVE-2020-12441: Denial-of-Service (DoS) in Ivanti Service Manager HEAT Remote Control 7.4&lt;/li&gt;&#xA;&lt;li&gt;CVE-2020-13793: Unsafe storage of AD credentials in Ivanti DSM netinst 5.1&lt;/li&gt;&#xA;&lt;/ul&gt;&#xA;&lt;p&gt;The vulnerabilities have meanwhile been fixed and an updated software version can be downloaded &lt;a href=&#34;http://forums.ivanti.com/s/article/Ivanti-DSM-Download-Center&#34;&gt;here&lt;/a&gt;.&lt;/p&gt;</description>
    </item>
    <item>
      <title>Dog Whisperer Update</title>
      <link>https://insinuator.net/2020/03/dog-whisperer-update/</link>
      <pubDate>Thu, 26 Mar 2020 00:00:00 +0000</pubDate>
      <guid>https://insinuator.net/2020/03/dog-whisperer-update/</guid>
      <description>&lt;p&gt;With the current situation, it’s not easy to find the right angle to start this blog post, so I won’t even try… but with Troopers cancelled, my Bloodhound workshop went down the drain, and I didn’t get a chance to meet or catch up with all of you and share my latest BloodHound adventures. So I decided to write a quick post to share all this…&lt;/p&gt;&#xA;&lt;p&gt;&lt;img src=&#34;Whipsererlogo3.png&#34; alt=&#34;&#34;&gt;&lt;/p&gt;&#xA;&lt;p&gt;As you might have heard, BloodHound 3 was released last month, so I thought it was time to update the &lt;strong&gt;Dog Whisperers Handbook&lt;/strong&gt;.&lt;br&gt;&#xA;It’s basically a quick intro to BloodHound and Cypher, with a lot of links to resources for further learning.&lt;br&gt;&#xA;You can download the latest version &lt;a href=&#34;https://www.ernw.de/download/ERNW_DogWhisperer3.pdf&#34;&gt;here&lt;/a&gt;. Hope you enjoy it.&lt;/p&gt;</description>
    </item>
    <item>
      <title>VMware NSX-T Distributed Firewall can be bypassed by default</title>
      <link>https://insinuator.net/2020/03/vmware-nsx-t-distributed-firewall-can-be-bypassed-by-default/</link>
      <pubDate>Mon, 23 Mar 2020 00:00:00 +0000</pubDate>
      <guid>https://insinuator.net/2020/03/vmware-nsx-t-distributed-firewall-can-be-bypassed-by-default/</guid>
      <description>&lt;p&gt;We recently came across an issue when playing around with VMware NSX-T which not anyone might be aware of when getting started with it. Because many of our customers start with transitioning to NSX-T, we want to share this with you. In short, the Distributed Firewall (DFW) of NSX-T can be easily bypassed in the default configuration because it only works effectively if at the same time, the &lt;em&gt;SpoofGuard&lt;/em&gt; feature is enabled on all logical switch ports which is not the case by default.&lt;/p&gt;</description>
    </item>
    <item>
      <title>Windows Insight: The Windows Telemetry ETW Monitor</title>
      <link>https://insinuator.net/2020/01/windows-insight-the-windows-telemetry-etw-monitor/</link>
      <pubDate>Tue, 14 Jan 2020 00:00:00 +0000</pubDate>
      <guid>https://insinuator.net/2020/01/windows-insight-the-windows-telemetry-etw-monitor/</guid>
      <description>&lt;p&gt;The &lt;a href=&#34;https://github.com/ernw/Windows-Insight&#34;&gt;Windows Insight&lt;/a&gt; repository now hosts the &lt;a href=&#34;https://github.com/ernw/Windows-Insight/tree/master/files/wintel_etwmonitor&#34;&gt;Windows Telemetry ETW Monitor&lt;/a&gt; framework. The framework monitors and reports on Windows Telemetry ETW (Event Tracing for Windows) activities – ETW activities for providing data to Windows Telemetry. It consists of two components:&lt;/p&gt;&#xA;&lt;ul&gt;&#xA;&lt;li&gt;the Windbg Framework: a set of scripts for monitoring Windows Telemetry ETW activities. The scripts are fed to a running windbg instance, connected to the Windows instance whose Windows Telemetry ETW activities are monitored.&lt;/li&gt;&#xA;&lt;li&gt;the Telemetry Information Visualization (TIV) framework for visualization of information and statistics. The TIV framework is a set of Python scripts that visualize information and statistics based on the data produced by the Windbg Framework. The output of the TIV framework is a report in the form of a web page.&lt;/li&gt;&#xA;&lt;/ul&gt;&#xA;&lt;p&gt;&lt;a href=&#34;https://insinuator.net/2020/01/windows-insight-the-windows-telemetry-etw-monitor/wintel/&#34;&gt;&lt;img src=&#34;wintel-1024x575.png&#34; alt=&#34;wintel&#34;&gt;&lt;/a&gt;&lt;/p&gt;</description>
    </item>
    <item>
      <title>Dissection of an Incident – Part 2</title>
      <link>https://insinuator.net/2019/10/dissection-of-an-incident-part-2/</link>
      <pubDate>Wed, 30 Oct 2019 00:00:00 +0000</pubDate>
      <guid>https://insinuator.net/2019/10/dissection-of-an-incident-part-2/</guid>
      <description>&lt;p&gt;After our &lt;a href=&#34;https://insinuator.net/2019/07/emotet-at-heise-emotet-there-emotet-everywhere-dissection-of-an-incident/&#34;&gt;last blogpost&lt;/a&gt; regarding Emotet and several other Emotet and Ransomware samples that we encountered, we recently stumbled across a variant belonging to the &lt;em&gt;Gozi&lt;/em&gt;, &lt;em&gt;ISFB&lt;/em&gt;, &lt;em&gt;Dreambot&lt;/em&gt; respectively &lt;em&gt;Ursnif&lt;/em&gt; family. In this blogpost, we want to share our insights from the analysis of this malware, whose malware family is mainly known for being a banking trojan that typically tries to infect browser sessions and sniff/redirect data. In particular, we are going to provide details about the first stage Word Document, the embedded JavaScript/XSL document, an in-depth runtime analysis of the downloaded executable, and some details regarding detection.&lt;/p&gt;</description>
    </item>
    <item>
      <title>Windows Insight: Code integrity and WDAC</title>
      <link>https://insinuator.net/2019/10/windows-insight-code-integrity-and-wdac/</link>
      <pubDate>Wed, 30 Oct 2019 00:00:00 +0000</pubDate>
      <guid>https://insinuator.net/2019/10/windows-insight-code-integrity-and-wdac/</guid>
      <description>&lt;p&gt;The &lt;a href=&#34;https://github.com/ernw/Windows-Insight&#34;&gt;Windows Insight&lt;/a&gt; repository now hosts three articles on Windows code integrity and WDAC (Windows Defender Application Control):&lt;/p&gt;&#xA;&lt;ul&gt;&#xA;&lt;li&gt;&lt;strong&gt;Device Guard Image Integrity: Architecture Overview&lt;/strong&gt; (&lt;em&gt;Aleksandar Milenkoski&lt;/em&gt;, &lt;em&gt;Dominik Phillips&lt;/em&gt;): In this work, we present the high-level architecture of the code integrity mechanism implemented as part of Windows 10.&lt;/li&gt;&#xA;&lt;li&gt;&lt;strong&gt;Windows Defender Application Control: Initialization&lt;/strong&gt; (&lt;em&gt;Dominik Phillips&lt;/em&gt;, &lt;em&gt;Aleksandar Milenkoski&lt;/em&gt;): This work describes the process for initializing WDAC performed by the Windows loader and the kernel when Windows 10 is booted.&lt;/li&gt;&#xA;&lt;li&gt;&lt;strong&gt;Windows Defender Application Control: Image verification&lt;/strong&gt; (&lt;em&gt;Aleksandar Milenkoski&lt;/em&gt;): This work discusses the workflow of WDAC for verifying images.&lt;/li&gt;&#xA;&lt;/ul&gt;&#xA;&lt;p&gt;– Aleksandar Milenkoski&lt;/p&gt;</description>
    </item>
    <item>
      <title>PSD2 – Mandatory Account Access for Third Party Providers</title>
      <link>https://insinuator.net/2019/09/psd2-mandatory-account-access-for-third-party-providers/</link>
      <pubDate>Thu, 12 Sep 2019 00:00:00 +0000</pubDate>
      <guid>https://insinuator.net/2019/09/psd2-mandatory-account-access-for-third-party-providers/</guid>
      <description>&lt;p&gt;On September 14th the final deadline of complying with the new Payment Service Directive PSD2 will be reached. Among other things, this directive will bring quite a few technical challenges for credit institutions. These include new requirements on two-factor authentication and API access for third parties. In this blog post we will give a short overview of what this means for banks from a security perspective and outline a few of the security-related issues based on what we have been observing during recent assessments of such APIs.&lt;/p&gt;</description>
    </item>
    <item>
      <title>A Follow-Up on the Heisec Webinar on Emotet &amp;amp; Some Active Directory Security Sources</title>
      <link>https://insinuator.net/2019/08/a-follow-up-on-the-heisec-webinar-on-emotet-amp-some-active-directory-security-sources/</link>
      <pubDate>Fri, 09 Aug 2019 00:00:00 +0000</pubDate>
      <guid>https://insinuator.net/2019/08/a-follow-up-on-the-heisec-webinar-on-emotet-amp-some-active-directory-security-sources/</guid>
      <description>&lt;p&gt;Some weeks ago, Heinrich and I had the pleasure to participate in the heisec-Webinar &lt;a href=&#34;https://www.heise.de/security/meldung/heisec-Webinar-Emotet-bei-Heise-Lernen-aus-unseren-Fehlern-4439874.html&#34;&gt;“Emotet bei Heise – Lernen aus unseren Fehlern”&lt;/a&gt;. We really enjoyed the webinar and the (alas, due to the format: too short) discussions and we hope we could contribute to understand how to make Active Directory implementations out there a bit safer in the future.&lt;/p&gt;&#xA;&lt;p&gt;Now, I have the pleasure to announce a continuation of our talk about Active Directory security next week, Wednesday, 14^(th) of August @heisec in the format of a technical talk &lt;a href=&#34;https://www.heise-events.de/webinare/emotet_cybercrime&#34;&gt;“Emotet bei Heise – Online-Fachgespräch zum Schutz vor Cybercrime”&lt;/a&gt;. Seats are still available 😉&lt;/p&gt;</description>
    </item>
    <item>
      <title>LibreOffice – A Python Interpreter (code execution vulnerability CVE-2019-9848)</title>
      <link>https://insinuator.net/2019/07/libreoffice-a-python-interpreter-code-execution-vulnerability-cve-2019-9848/</link>
      <pubDate>Fri, 26 Jul 2019 00:00:00 +0000</pubDate>
      <guid>https://insinuator.net/2019/07/libreoffice-a-python-interpreter-code-execution-vulnerability-cve-2019-9848/</guid>
      <description>&lt;p&gt;While waiting for a download to complete, I stumbled across an interesting &lt;a href=&#34;https://insert-script.blogspot.com/2019/02/libreoffice-cve-2018-16858-remote-code.html&#34;&gt;blogpost&lt;/a&gt;. The author describes a flaw in LibreOffice that allowed an attacker to execute code. Since this was quite recent, I was interested if my version is vulnerable to this attack and how they fixed it. Thus, I looked at the sources and luckily it was fixed. What I didn’t know before however was, that macros shipped with LibreOffice are executed without prompting the user, even on the highest macro security setting. So, if there would be a system macro from LibreOffice with a bug that allows to execute code, the user would not even get a prompt and the code would be executed right away. Therefor, I started to have a closer look at the source code and found out that exactly this is the case!&lt;/p&gt;</description>
    </item>
    <item>
      <title>Emotet at Heise, Emotet there, Emotet everywhere – Dissection of an Incident</title>
      <link>https://insinuator.net/2019/07/emotet-at-heise-emotet-there-emotet-everywhere-dissection-of-an-incident/</link>
      <pubDate>Thu, 18 Jul 2019 00:00:00 +0000</pubDate>
      <guid>https://insinuator.net/2019/07/emotet-at-heise-emotet-there-emotet-everywhere-dissection-of-an-incident/</guid>
      <description>&lt;p&gt;After the &lt;a href=&#34;https://www.heise.de/ct/artikel/Emotet-bei-Heise-4437807.html&#34;&gt;Emotet Incident at Heise&lt;/a&gt;, where &lt;a href=&#34;https://www.heise.de/security/meldung/heisec-Webinar-Emotet-bei-Heise-Lernen-aus-unseren-Fehlern-4439874.html&#34;&gt;ERNW has been consulted for Incident Response&lt;/a&gt;, we decided to start a blogpost series, in which we want to regularly report on current attacks that we observe. In particular we want to provide details about the utilized pieces of malware, different stages, and techniques used for the initial infection and lateral movement. We hope that this information might help you to detect ongoing incidents, apply countermeasures, and in the best case to figure out proactive countermeasures and security controls beforehand.&lt;/p&gt;</description>
    </item>
    <item>
      <title>IPv6 Surveys / Application Space</title>
      <link>https://insinuator.net/2019/06/ipv6-surveys-/-application-space/</link>
      <pubDate>Sun, 30 Jun 2019 00:00:00 +0000</pubDate>
      <guid>https://insinuator.net/2019/06/ipv6-surveys-/-application-space/</guid>
      <description>&lt;p&gt;In some organizations we work with a certain state of IPv6 deployment has been reached in the interim which includes, among others, the following aspects:&lt;/p&gt;&#xA;&lt;ul&gt;&#xA;&lt;li&gt;the network infrastructure is IPv6-enabled (incl. interface addressing, routing [protocols] and the like).&lt;/li&gt;&#xA;&lt;li&gt;parts of supporting services (security functions, monitoring, system management) include IPv6 in a proper way.&lt;/li&gt;&#xA;&lt;li&gt;3rd party providers have been contractually obliged to deliver their services in an “IPv6-enabled” mode (as opposed to only being “IPv6-capable” which was the standard requirement in many RFIs during earlier years).&lt;/li&gt;&#xA;&lt;/ul&gt;&#xA;&lt;p&gt;It might then happen that networking people (who often are the initial motivators for deploying IPv6) in such organizations are stating, when asked about IPv6: “it’s [mostly] done”.&lt;br&gt;&#xA;Point is that, alas, this does not necessarily mean that a single service or application is *actually using* IPv6, so while the above certainly constitutes an achievement it might not even be halfway through.&lt;/p&gt;</description>
    </item>
    <item>
      <title>IPv6 Properties of Windows Server 2019 / Windows 10 (1809)</title>
      <link>https://insinuator.net/2019/06/ipv6-properties-of-windows-server-2019-/-windows-10-1809/</link>
      <pubDate>Wed, 12 Jun 2019 00:00:00 +0000</pubDate>
      <guid>https://insinuator.net/2019/06/ipv6-properties-of-windows-server-2019-/-windows-10-1809/</guid>
      <description>&lt;p&gt;In this post I’ll cover some properties of the Windows Server 2019 IPv6 stack. It is an update of a similar post I wrote on the &lt;a href=&#34;https://insinuator.net/2017/01/ipv6-properties-of-windows-server-2016-windows-10/&#34;&gt;IPv6 properties of Server 2016&lt;/a&gt; a while ago.&lt;/p&gt;&#xA;&lt;p&gt;For this reason I will mostly look at the same properties I did at the time (read: at times without providing too much technical background information; that can be found in the other post) and I’ve hence performed the same types of practical tests.&lt;/p&gt;</description>
    </item>
    <item>
      <title>Windows Insight: Virtual Secure Mode</title>
      <link>https://insinuator.net/2019/06/windows-insight-virtual-secure-mode/</link>
      <pubDate>Wed, 12 Jun 2019 00:00:00 +0000</pubDate>
      <guid>https://insinuator.net/2019/06/windows-insight-virtual-secure-mode/</guid>
      <description>&lt;p&gt;The &lt;a href=&#34;https://github.com/ernw/Windows-Insight&#34;&gt;Windows Insight&lt;/a&gt; repository currently hosts four articles on VSM (Virtual Secure Mode):&lt;/p&gt;&#xA;&lt;ul&gt;&#xA;&lt;li&gt;&lt;strong&gt;Virtual Secure Mode: Architecture Overview&lt;/strong&gt; (&lt;em&gt;Aleksandar Milenkoski&lt;/em&gt;): In this work, we discuss the architecture of a virtualized Windows environment.&lt;/li&gt;&#xA;&lt;li&gt;**Virtual Secure Mode: Communication Interfaces **(&lt;em&gt;Aleksandar Milenkoski&lt;/em&gt;): In this work, we discuss the communication interfaces that VSM implements: Isolated User Mode (IUM) system calls, normal-mode services, secure services, and hypercalls.&lt;/li&gt;&#xA;&lt;li&gt;&lt;strong&gt;Virtual Secure Mode: Protections of Communication Interfaces&lt;/strong&gt; (&lt;em&gt;Aleksandar Milenkoski&lt;/em&gt;): This work discusses implemented mechanisms for securing the above VSM communication interfaces. This includes restrictions on issuing hypercalls, data marshalling and sanitization, and secure data sharing.&lt;/li&gt;&#xA;&lt;li&gt;&lt;strong&gt;Virtual Secure Mode: Initialization&lt;/strong&gt; (&lt;em&gt;Dominik Phillips, Aleksandar Milenkoski&lt;/em&gt;): This work describes the process for VSM initialization activities performed by the Windows loader and the Windows kernel when Windows 10 is booted.&lt;/li&gt;&#xA;&lt;/ul&gt;&#xA;&lt;p&gt;– Aleksandar Milenkoski&lt;/p&gt;</description>
    </item>
    <item>
      <title>Emotet im Active Directory: Es kann jeden treffen – aber Jeder kann es dem Angreifer schwer machen!</title>
      <link>https://insinuator.net/2019/06/emotet-im-active-directory-es-kann-jeden-treffen-aber-jeder-kann-es-dem-angreifer-schwer-machen/</link>
      <pubDate>Fri, 07 Jun 2019 00:00:00 +0000</pubDate>
      <guid>https://insinuator.net/2019/06/emotet-im-active-directory-es-kann-jeden-treffen-aber-jeder-kann-es-dem-angreifer-schwer-machen/</guid>
      <description>&lt;p&gt;Heise berichtet aktuell öffentlich über die &lt;a href=&#34;https://www.heise.de/ct/artikel/Emotet-bei-Heise-4437807.html&#34;&gt;Emotet-Infektion im eigenen Haus&lt;/a&gt;, bei dessen Aufklärung ERNW unterstützte. &lt;a href=&#34;https://www.heise.de/newsticker/meldung/heiseshow-Emotet-trifft-Heise-Einblicke-in-einen-Trojaner-Angriff-4439850.html&#34;&gt;Damit liefert Heise Informationen&lt;/a&gt; zum Verlauf aktueller Angriffe, aber insbesondere auch wertvolle Einsichten zu Vorbeugung, Erkennung, Analyse und Gegenmaßnahmen aus eigener Erfahrung, wie sie nur selten der Öffentlichkeit preisgegeben werden.&lt;/p&gt;&#xA;&lt;p&gt;Ein Team aus Incident-Response Spezialisten der ERNW Research unterstützte Heise bei der Analyse und Rekonstruktion des Vorfalls und analysierte die Schadsoftware, um deren Ausbreitungswege nachzuvollziehen und IoCs (Indicators of Compromise) zu extrahieren. Hierdurch konnten effektive Gegenmaßnahmen entwickelt und gemeinsam mit Heise erfolgreich umgesetzt werden.&lt;/p&gt;</description>
    </item>
    <item>
      <title>Windows Insight: The TPM</title>
      <link>https://insinuator.net/2019/05/windows-insight-the-tpm/</link>
      <pubDate>Mon, 27 May 2019 00:00:00 +0000</pubDate>
      <guid>https://insinuator.net/2019/05/windows-insight-the-tpm/</guid>
      <description>&lt;p&gt;The &lt;a href=&#34;https://github.com/ernw/Windows-Insight&#34;&gt;Windows Insight&lt;/a&gt; repository currently hosts three articles on the TPM (Trusted Platform Module):&lt;/p&gt;&#xA;&lt;ul&gt;&#xA;&lt;li&gt;&lt;strong&gt;The TPM: Communication Interfaces&lt;/strong&gt; (&lt;em&gt;Aleksandar Milenkoski&lt;/em&gt;): In this work, we discuss how the different components of the Windows 10 operating system deployed in user-land and in kernel-land, use the TPM. We focus on the communication interfaces between Windows 10 and the TPM. In addition, we discuss the construction of TPM usage profiles, that is, information on system entities communicating with the TPM as well as on communication patterns and frequencies;&lt;/li&gt;&#xA;&lt;li&gt;&lt;strong&gt;The TPM: Integrity Measurement&lt;/strong&gt; (&lt;em&gt;Aleksandar Milenkoski&lt;/em&gt;): In this work, we discuss the integrity measurement mechanism of Windows 10 and the role that the TPM plays&lt;br&gt;&#xA;as part of it. This mechanism, among other things, implements the production of measurement data. This involves calculation of hashes of relevant executable files or of code sequences at every system startup. It also involves the storage of these hashes and relevant related data in log files for later analysis;&lt;/li&gt;&#xA;&lt;/ul&gt;&#xA;&lt;p&gt; &lt;/p&gt;</description>
    </item>
    <item>
      <title>The Week in Review #RIPE78</title>
      <link>https://insinuator.net/2019/05/the-week-in-review-%23ripe78/</link>
      <pubDate>Sun, 26 May 2019 00:00:00 +0000</pubDate>
      <guid>https://insinuator.net/2019/05/the-week-in-review-%23ripe78/</guid>
      <description>&lt;p&gt;This week &lt;a href=&#34;https://twitter.com/bcp38_&#34;&gt;Chris&lt;/a&gt; and I participated in the RIPE 78 meeting in Reykjavík. Being part of the group was fun as always and we had quite some interesting conversations with peers from (not only) the IPv6 community.&lt;br&gt;&#xA;Big thanks to the &lt;a href=&#34;https://twitter.com/RIPE_NCC&#34;&gt;RIPE NCC&lt;/a&gt; team for the smooth organization and for taking care of us!&lt;/p&gt;&#xA;&lt;p&gt;In this post I’ll provide some notes on talks I found particularly interesting, plus links to our own contributions.&lt;/p&gt;</description>
    </item>
    <item>
      <title>Windows Insight: A New ERNW Repository</title>
      <link>https://insinuator.net/2019/05/windows-insight-a-new-ernw-repository/</link>
      <pubDate>Thu, 23 May 2019 00:00:00 +0000</pubDate>
      <guid>https://insinuator.net/2019/05/windows-insight-a-new-ernw-repository/</guid>
      <description>&lt;p&gt;We are glad to announce the &lt;a href=&#34;https://github.com/ernw/Windows-Insight&#34;&gt;Windows Insight&lt;/a&gt; repository. The content of this repository aims to assist efforts on analysing inner working principles, functionalities, and properties of the Microsoft Windows operating system. This repository stores relevant documentation as well as executable files needed for conducting analysis studies.&lt;/p&gt;&#xA;&lt;p&gt;Some of the content of this repository has been created in the course of a project named ‘Studie zu Systemaufbau, Protokollierung, Härtung und Sicherheitsfunktionen in Windows 10 (SiSyPHuS Win10)’ (ger.) – ‘Study of system design, logging, hardening, and security functions in Windows 10’ (eng.). This project has been contracted by the &lt;a href=&#34;https://www.bsi.bund.de/EN/TheBSI/thebsi_node.html&#34;&gt;German Federal Office for Information Security&lt;/a&gt; (ger., Bundesamt für Sicherheit in der Informationstechnik – BSI). The work planned as part of the project is conducted by ERNW GmbH, starting in May 2017.&lt;/p&gt;</description>
    </item>
    <item>
      <title>IPv6 Security for Enterprise Organisations @ #RIPE78</title>
      <link>https://insinuator.net/2019/05/ipv6-security-for-enterprise-organisations-@-%23ripe78/</link>
      <pubDate>Fri, 17 May 2019 00:00:00 +0000</pubDate>
      <guid>https://insinuator.net/2019/05/ipv6-security-for-enterprise-organisations-@-%23ripe78/</guid>
      <description>&lt;p&gt;&lt;a href=&#34;https://twitter.com/bcp38_&#34;&gt;Chris&lt;/a&gt; and I will give a tutorial on the above topic at &lt;a href=&#34;https://ripe78.ripe.net/&#34;&gt;next week’s RIPE Meeting&lt;/a&gt; in Reykjavík. In this post (actually this will probably become a small series of posts) I’ll try to summarize some thoughts on IPv6 security in enterprise environments in 2019.&lt;/p&gt;&#xA;&lt;p&gt;We’re going to cover three main areas:&lt;/p&gt;&#xA;&lt;ul&gt;&#xA;&lt;li&gt;Why IPv6 Is Different, Security-wise&lt;/li&gt;&#xA;&lt;li&gt;Traffic Filtering in IPv6 Networks&lt;/li&gt;&#xA;&lt;li&gt;IPv6 Security in L2 Networks / First Hop Security et al.&lt;/li&gt;&#xA;&lt;/ul&gt;&#xA;&lt;p&gt;Let’s start with the first item. In real-life scenarios the security of “a protocol” – IPv6 can rather be considered a “protocol family” which includes helper protocols like ICMPv6 and MLD (which in turn is implemented by means of ICMPv6 messages) and potentially others like DHCPv6 – might depend on a number of factors:&lt;/p&gt;</description>
    </item>
    <item>
      <title>Heise Security Tour: Offensive PowerShell</title>
      <link>https://insinuator.net/2019/05/heise-security-tour-offensive-powershell/</link>
      <pubDate>Mon, 13 May 2019 00:00:00 +0000</pubDate>
      <guid>https://insinuator.net/2019/05/heise-security-tour-offensive-powershell/</guid>
      <description>&lt;p&gt;Dominik Phillips and I are taking part in a tour organized by &lt;a href=&#34;https://www.heise.de/security/&#34;&gt;Heise Security&lt;/a&gt; – the &lt;a href=&#34;https://www.heise-events.de/konferenzen/securitytour&#34;&gt;Heise Security Tour&lt;/a&gt;. We give a talk titled “PowerShell: Attack under the radar”. In this talk, we provide an overview of the architecture of PowerShell and show how attackers may use PowerShell for malicious purposes. We demonstrate PowerShell post-exploitation activities implemented as part of publicly available frameworks, such as &lt;a href=&#34;https://www.powershellempire.com/&#34;&gt;Empire&lt;/a&gt;. We also discuss a security concept for defending against such activities.&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>MDMs – The Mobile Device “Magic” Solutions – Expectations and Reality</title>
      <link>https://insinuator.net/2019/04/mdms-the-mobile-device-magic-solutions-expectations-and-reality/</link>
      <pubDate>Mon, 15 Apr 2019 00:00:00 +0000</pubDate>
      <guid>https://insinuator.net/2019/04/mdms-the-mobile-device-magic-solutions-expectations-and-reality/</guid>
      <description>&lt;p&gt;When you are working in the area of mobile security, you sooner or later receive requests from clients asking you to test specific ‘Mobile Device Management’ (MDM) solutions which they (plan to) use, the corresponding mobile apps, as well as different environment setups and device policy sets.&lt;br&gt;&#xA;The expectations are often high, not only for the MDM solutions ability to massively reduce the administrative workload of keeping track, updating and managing the often hundreds or thousands of devices within a company but also regarding the improvements towards the level of security that an MDM solution is regularly advertised to provide.&lt;/p&gt;</description>
    </item>
    <item>
      <title>IPv6 Address Management / The “External” Flag</title>
      <link>https://insinuator.net/2019/02/ipv6-address-management-/-the-external-flag/</link>
      <pubDate>Fri, 22 Feb 2019 00:00:00 +0000</pubDate>
      <guid>https://insinuator.net/2019/02/ipv6-address-management-/-the-external-flag/</guid>
      <description>&lt;p&gt;We’re regularly asked to review IPv6 address plans from different organizations and I’d like to share some reflections from such a process currently happening. I’ve discussed a few aspects of IPv6 address planning before; those readers interested please see &lt;a href=&#34;https://insinuator.net/2019/01/ipv6-talks-publications/&#34;&gt;this post&lt;/a&gt; which contains some references.&lt;/p&gt;&#xA;&lt;p&gt;The organization in question is headquartered in Germany, has ~60K employees and a number of subsidiaries in European countries. They belong to a “traditional industry sector” (so they’re not an “Internet company”, even though they – as the majority of large organizations right now – strive to be one in a few years ;-).&lt;/p&gt;</description>
    </item>
    <item>
      <title>IPv6 Security in an IPv4-only Environment</title>
      <link>https://insinuator.net/2019/02/ipv6-security-in-an-ipv4-only-environment/</link>
      <pubDate>Wed, 20 Feb 2019 00:00:00 +0000</pubDate>
      <guid>https://insinuator.net/2019/02/ipv6-security-in-an-ipv4-only-environment/</guid>
      <description>&lt;p&gt;Starting a post, in 2019, with a mention of sth being “IPv4-only” somewhat hurts ;-), but here we go. Recently &lt;a href=&#34;https://twitter.com/manelrodero&#34;&gt;Manel Rodero&lt;/a&gt; from Barcelona asked me the &lt;a href=&#34;https://twitter.com/manelrodero/status/1093272272599695360&#34;&gt;following question&lt;/a&gt; on Twitter:&lt;/p&gt;&#xA;&lt;p&gt;&lt;img src=&#34;tweet_mr.png&#34; alt=&#34;&#34;&gt;&lt;/p&gt;&#xA;&lt;p&gt;In this post I’ll try to discuss some inherent aspects of that question and ofc I’ll try to provide a response to it, too ;-).&lt;/p&gt;&#xA;&lt;p&gt;Let’s first think about the main IPv6-related &lt;em&gt;risks&lt;/em&gt; (= threats put into a context of relevance) in an “environment [that] is only IPv4”. While some of you might scratch your heads “what IPv6 threats could there be in an IPv4 setting?” I’m tempted to scratch my head: “what could be the reasons to run an university network without IPv6 these days, or to use BIND?” (which I have a strong opinion on, see &lt;a href=&#34;https://insinuator.net/2011/11/call-me-snake/&#34;&gt;here&lt;/a&gt; or &lt;a href=&#34;https://twitter.com/Enno_Insinuator/status/852358157292761089&#34;&gt;here&lt;/a&gt;). But I disgress. More seriously the main reason for the question can be broken down to:&lt;/p&gt;</description>
    </item>
    <item>
      <title>Some Notes on the IPv6 Properties of the Wireless Network @ Cisco Live Europe</title>
      <link>https://insinuator.net/2019/02/some-notes-on-the-ipv6-properties-of-the-wireless-network-@-cisco-live-europe/</link>
      <pubDate>Sun, 03 Feb 2019 00:00:00 +0000</pubDate>
      <guid>https://insinuator.net/2019/02/some-notes-on-the-ipv6-properties-of-the-wireless-network-@-cisco-live-europe/</guid>
      <description>&lt;p&gt;Some years ago &lt;a href=&#34;https://twitter.com/bcp38&#34;&gt;Christopher&lt;/a&gt; wrote two posts (&lt;a href=&#34;https://insinuator.net/2016/02/observations-from-the-cisco-live-europe-2016-wifi-infrastructure/&#34;&gt;2016&lt;/a&gt;, &lt;a href=&#34;https://insinuator.net/2015/01/observations-from-the-cisco-live-europe-wifi-infrastructure/&#34;&gt;2015&lt;/a&gt;) about the  IPv6-related characteristics of the WiFi network at Cisco Live Europe. To somewhat continue this tradition and for mere technical interest I had a look at some properties of this year’s setting.&lt;/p&gt;&#xA;&lt;p&gt;There were two SSIDs of interest: a dual-stacked one (“CiscoLive2019”) and one with v6-only plus NAT64 (“CL-NAT64”). For some background on the underlying infrastructure components you might look at this &lt;a href=&#34;https://twitter.com/DarchisNicolas/status/1089095382171299840&#34;&gt;thread&lt;/a&gt; by &lt;a href=&#34;https://twitter.com/DarchisNicolas&#34;&gt;Nicolas Darchis&lt;/a&gt; from the NOC or at &lt;a href=&#34;https://twitter.com/networkautobahn/status/1089827410541977600&#34;&gt;this tweet&lt;/a&gt; from &lt;a href=&#34;https://twitter.com/networkautobahn&#34;&gt;Dominik Pickhardt&lt;/a&gt;. Some stats on IPv6 usage at CLEUR can be found &lt;a href=&#34;https://twitter.com/SNMPguy/status/1091018632593895425&#34;&gt;here&lt;/a&gt;.&lt;/p&gt;</description>
    </item>
    <item>
      <title>IPv6 Talks &amp; Publications</title>
      <link>https://insinuator.net/2019/01/ipv6-talks-publications/</link>
      <pubDate>Thu, 10 Jan 2019 00:00:00 +0000</pubDate>
      <guid>https://insinuator.net/2019/01/ipv6-talks-publications/</guid>
      <description>&lt;p&gt;At first a very happy new year to everybody!&lt;/p&gt;&#xA;&lt;p&gt;While thinking about the agenda of the upcoming &lt;a href=&#34;https://www.troopers.de/&#34;&gt;Troopers&lt;/a&gt; NGI IPv6 Track I realized that quite a lot of IPv6-related topics have been covered in the last years by various IPv6 practitioners (like my colleague &lt;a href=&#34;https://twitter.com/bcp38_&#34;&gt;Christopher Werny&lt;/a&gt;) or researchers (like my friend &lt;a href=&#34;https://twitter.com/AntoniosAtlasis&#34;&gt;Antonios Atlasis&lt;/a&gt;). In a kind of shameless self plug I then decided to put together of list of IPv6 talks I myself gave at several occasions and of publications I (co-) authored. Please find this list below (sorted by years); you can click on the titles to access the respective documents/sources.&lt;br&gt;&#xA;I hope some of this can be of help for one or the other among you in the course of your own IPv6 efforts.&lt;br&gt;&#xA;Cheers,&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>Motivational Aspects and Privacy Concerns on Wearables in the German Running Community</title>
      <link>https://insinuator.net/2018/12/motivational-aspects-and-privacy-concerns-on-wearables-in-the-german-running-community/</link>
      <pubDate>Fri, 14 Dec 2018 00:00:00 +0000</pubDate>
      <guid>https://insinuator.net/2018/12/motivational-aspects-and-privacy-concerns-on-wearables-in-the-german-running-community/</guid>
      <description>&lt;p&gt;Today I am proud to announce that another paper of my former colleagues from Heilbronn University and me was published in one of the journals with the highest impact factor for Medical Informatics research called &lt;em&gt;JMIR mHealth and uHealth&lt;/em&gt;. There is a reason why we published in this journal besides its informatics focus. The journal is an open access journal. That means that readers are not charged on a pay-per-view basis or other business models to access the full text of the paper. In return, the authors need to pay publication fees. In my opinion restricting access to academic research is not a way to go. I think this isn’t a thing we see in the security community often anyway. But this is and was the standard in academia for years.&lt;/p&gt;</description>
    </item>
    <item>
      <title>ERNW Whitepaper 67: Active Directory Trust Considerations</title>
      <link>https://insinuator.net/2018/12/ernw-whitepaper-67-active-directory-trust-considerations/</link>
      <pubDate>Tue, 11 Dec 2018 00:00:00 +0000</pubDate>
      <guid>https://insinuator.net/2018/12/ernw-whitepaper-67-active-directory-trust-considerations/</guid>
      <description>&lt;p&gt;Last week &lt;a href=&#34;https://twitter.com/HarmJ0y&#34;&gt;Will “harmj0y” Schroeder&lt;/a&gt; published an excellent technical article titled &lt;a href=&#34;https://www.harmj0y.net/blog/redteaming/not-a-security-boundary-breaking-forest-trusts/&#34;&gt;“Not A Security Boundary: Breaking Forest Trusts”&lt;/a&gt; in which he lays out how a highly critical security compromise can be achieved across a forest boundary, resulting from a combination of default AD (security) settings and a novel attack method. His post is a follow-up to the DerbyCon talk “The Unintended Risks of Trusting Active Directory” which he had given together with &lt;a href=&#34;https://twitter.com/tifkin_&#34;&gt;Lee Christensen&lt;/a&gt; and &lt;a href=&#34;https://twitter.com/enigma0x3&#34;&gt;Matt Nelson&lt;/a&gt; at DerbyCon (video &lt;a href=&#34;http://www.irongeek.com/i.php?page=videos/derbycon8/track-2-03-the-unintended-risks-of-trusting-active-directory-lee-christensen-will-schroeder-matt-nelson&#34;&gt;here&lt;/a&gt;). They will also discuss this at the upcoming &lt;a href=&#34;https://www.troopers.de/&#34;&gt;Troopers&lt;/a&gt; Active Directory Security Track (details on some more talks, including &lt;a href=&#34;https://twitter.com/PyroTek3&#34;&gt;Sean Metcalf’s&lt;/a&gt; one, can be found in &lt;a href=&#34;https://insinuator.net/2018/11/first-talks-of-troopers19-accepted/&#34;&gt;this post&lt;/a&gt; or &lt;a href=&#34;https://insinuator.net/2018/12/and-five-talks-more-were-accepted-at-troopers19/&#34;&gt;this one&lt;/a&gt;).&lt;/p&gt;</description>
    </item>
    <item>
      <title>Comparison of our tool afro (APFS file recovery) with Blackbag Blacklight and Sleuthkit</title>
      <link>https://insinuator.net/2018/10/comparison-of-our-tool-afro-apfs-file-recovery-with-blackbag-blacklight-and-sleuthkit/</link>
      <pubDate>Thu, 18 Oct 2018 00:00:00 +0000</pubDate>
      <guid>https://insinuator.net/2018/10/comparison-of-our-tool-afro-apfs-file-recovery-with-blackbag-blacklight-and-sleuthkit/</guid>
      <description>&lt;p&gt;At this years ARES conference, Jonas Plum (Siemens) and me (Andreas Dewald, ERNW Research GmbH) published a &lt;a href=&#34;https://dl.acm.org/citation.cfm?id=3232808&#34;&gt;paper&lt;/a&gt; about the forensic analysis of APFS, file system internals and presented different methodologies for file recovery. We also publicly released a tool implementing our presented approaches, called &lt;a href=&#34;https://github.com/cugu/afro&#34;&gt;afro&lt;/a&gt; (APFS file recovery).&lt;/p&gt;&#xA;&lt;p&gt;APFS is the file system for Apple devices that is used by default on all current iOS mobile devices, as well as macOS since High Sierra, and is thus currently rolled out on a large number of devices. By using afro, we evaluated and compared the different approaches amongst each other and identified the method that so far delivers the best results and compared it to photorec. This showed that AFRO outperforms photorec on the evaluated APFS dataset. In the presentations of this research we were often asked if other tools like Blackbags Blacklight do not already support this recovery process. So, we decided to compare the file recovery capabilities of BlackLight and afro. We wanted to compare afro to the sleuth kit as well, as at the DFRWS conference it was discussed about &lt;a href=&#34;https://www.dfrws.org/sites/default/files/session-files/pres_adding_apfs_support_to_the_sleuthkit_framework.pdf&#34;&gt;adding APFS Support to The Sleuthkit Framework&lt;/a&gt;, but no implementations are public yet.&lt;/p&gt;</description>
    </item>
    <item>
      <title>A little KeePass Mea Culpa…</title>
      <link>https://insinuator.net/2018/07/a-little-keepass-mea-culpa/</link>
      <pubDate>Mon, 23 Jul 2018 00:00:00 +0000</pubDate>
      <guid>https://insinuator.net/2018/07/a-little-keepass-mea-culpa/</guid>
      <description>&lt;p&gt;Some weeks ago, I tweeted about grabbing clipboard content from KeePass with some PowerShell. From some reactions to this tweet, and after reading it a couple of times again, I realize it was sending the wrong message, and I would like to take a bit more than 280 chars to clarify what I meant when I posted that tweet…&lt;/p&gt;&#xA;&lt;p&gt;TLDR: Password managers are a must, not using one exposes you to far more risks than using one. Do it. &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>Creating Static Binaries for Nmap, Socat and other Tools</title>
      <link>https://insinuator.net/2018/02/creating-static-binaries-for-nmap-socat-and-other-tools/</link>
      <pubDate>Fri, 23 Feb 2018 00:00:00 +0000</pubDate>
      <guid>https://insinuator.net/2018/02/creating-static-binaries-for-nmap-socat-and-other-tools/</guid>
      <description>&lt;p&gt;In various scenarios it might be helpful or even required to have a statically compiled version of Nmap available. This applies to e.g. scenarios where only limited user privileges are available and installing anything to the system might not be desirable.&lt;/p&gt;&#xA;&lt;p&gt;For such cases I’ve started to create recipes to build such binaries. Similar projects are already available on GitHub, but there are several reasons why I chose to create my own tools:&lt;/p&gt;</description>
    </item>
    <item>
      <title>White Paper on Incident Analysis and Forensics in Docker Environments</title>
      <link>https://insinuator.net/2018/02/white-paper-on-incident-analysis-and-forensics-in-docker-environments/</link>
      <pubDate>Wed, 14 Feb 2018 00:00:00 +0000</pubDate>
      <guid>https://insinuator.net/2018/02/white-paper-on-incident-analysis-and-forensics-in-docker-environments/</guid>
      <description>&lt;p&gt;In this article, we describe the impact of the increased use of &lt;em&gt;Docker&lt;/em&gt; in corporate environments on forensic investigations and incident analysis. Even though Docker is being used more and more (Portworx, Inc., 2017), the implications of the changed runtime environment for forensic processes and tools have barely been considered. We describe the technological basics of Docker and, based on them, outline the differences that occur with respect to digital evidence and previously used methods for evidence acquisition. Specifically, we look at digital evidence within a Docker container which are lost or need to be acquired in different ways compared to a classical virtual machine, and what new traces and opportunities arise from Docker itself.&lt;/p&gt;</description>
    </item>
    <item>
      <title>White Paper on Multi-Factor Authentication in Microsoft Windows Environments</title>
      <link>https://insinuator.net/2018/01/white-paper-on-multi-factor-authentication-in-microsoft-windows-environments/</link>
      <pubDate>Mon, 29 Jan 2018 00:00:00 +0000</pubDate>
      <guid>https://insinuator.net/2018/01/white-paper-on-multi-factor-authentication-in-microsoft-windows-environments/</guid>
      <description>&lt;p&gt;A new ERNW whitepaper was just published. I wrote this whitepaper in the course of my bachelor thesis and it examines multi-factor authentication in Microsoft Windows environments:&lt;/p&gt;&#xA;&lt;blockquote&gt;&#xA;&lt;p&gt;Credential theft and the subsequent reuse of stolen credentials are a significant problem in today’s information security. To counter the associated risks, a planned approach is required as part of a comprehensive security architecture program. This includes the implementation of multi-factor authentication as an important building block. This whitepaper covers the relevant steps of implementing a multi-factor authentication system in an enterprise environment and closes with a security evaluation.&lt;/p&gt;</description>
    </item>
    <item>
      <title>Interacting with the BlueCoat Filesystem</title>
      <link>https://insinuator.net/2017/10/interacting-with-the-bluecoat-filesystem/</link>
      <pubDate>Thu, 26 Oct 2017 00:00:00 +0000</pubDate>
      <guid>https://insinuator.net/2017/10/interacting-with-the-bluecoat-filesystem/</guid>
      <description>&lt;p&gt;the last &lt;a href=&#34;https://insinuator.net/2017/10/reading-the-bluecoat-filesystem/&#34;&gt;post&lt;/a&gt; was about a fuse filesystem which provides a read-only access to the proprietary bluecoat filesystem. After some further investigations based on the possibilities this offered us, I started to implement a tool which allows to modify parts of the filesystem.&lt;/p&gt;&#xA;&lt;h2 id=&#34;protection-mechanisms&#34;&gt;Protection Mechanisms&lt;/h2&gt;&#xA;&lt;p&gt;Since last time, the discovered filesystem structures still had unknown fields. Some of those fields could be reconstructed and their purpose in the whole construct. The format of the &lt;code&gt;Partition&lt;/code&gt;-Header for example could now be described as&lt;/p&gt;</description>
    </item>
    <item>
      <title>Position Paper on an Enterprise Organization’s IPv6 Address Strategy</title>
      <link>https://insinuator.net/2017/10/position-paper-on-an-enterprise-organizations-ipv6-address-strategy/</link>
      <pubDate>Mon, 09 Oct 2017 00:00:00 +0000</pubDate>
      <guid>https://insinuator.net/2017/10/position-paper-on-an-enterprise-organizations-ipv6-address-strategy/</guid>
      <description>&lt;p&gt;A while ago I wrote a short paper laying out options for an enterprise organization to get global IPv6 address space from the RIPE NCC, discussing the advantages and disadvantages of different approaches. As I think the topic may be of interest for others, too, I’ve distilled an anonymized version. It can be found &lt;a href=&#34;https://www.ernw.de/download/ERNW_IPv6_Strategy_RIPE.pdf&#34;&gt;here&lt;/a&gt;. I hope some of you find it useful.&lt;/p&gt;&#xA;&lt;p&gt;Cheers, Enno&lt;/p&gt;</description>
    </item>
    <item>
      <title>An Update of PenTesting Tools that (do not) Support IPv6</title>
      <link>https://insinuator.net/2017/09/an-update-of-pentesting-tools-that-do-not-support-ipv6/</link>
      <pubDate>Tue, 19 Sep 2017 00:00:00 +0000</pubDate>
      <guid>https://insinuator.net/2017/09/an-update-of-pentesting-tools-that-do-not-support-ipv6/</guid>
      <description>&lt;p&gt;As you may remember, back in 2014 we published a &lt;a href=&#34;https://www.ernw.de/download/newsletter/ERNW_Newsletter_45_PenTesting_Tools_that_Support_IPv6_v.1.1_en.pdf&#34;&gt;whitepaper&lt;/a&gt; (compiled by &lt;a href=&#34;https://twitter.com/antoniosatlasis&#34;&gt;Antonis Atlasis&lt;/a&gt;) on the support of IPv6 in different pentesting tools. This is almost three years ago and we thought it is time for an update. In short not much has changed. Most of the tools which didn’t support IPv6 are still not supporting it or haven’t got any update since then.&lt;br&gt;&#xA;This post will  cover the tools where we could identify some progress on supporting IPv6.&lt;/p&gt;</description>
    </item>
    <item>
      <title>Local Packet Filtering with IPv6</title>
      <link>https://insinuator.net/2017/07/local-packet-filtering-with-ipv6/</link>
      <pubDate>Thu, 06 Jul 2017 00:00:00 +0000</pubDate>
      <guid>https://insinuator.net/2017/07/local-packet-filtering-with-ipv6/</guid>
      <description>&lt;p&gt;Just recently we discussed IPv6 filter rules for NIC-level firewalls (in a virtualized data center) with a customer. I’d like to take this as an opportunity to lay out potential approaches for local packet filtering of IPv6, which in turn might somewhat depend on the address configuration strategy chosen for the respective systems (for the latter you may refer to &lt;a href=&#34;https://insinuator.net/2016/12/ipv6-configuration-approaches-for-servers/&#34;&gt;this post&lt;/a&gt; or to &lt;a href=&#34;https://www.ernw.de/download/ERNW_TR17_NGI_IPv6_Config_Approach_Servers.pdf&#34;&gt;this talk&lt;/a&gt; from the &lt;a href=&#34;https://www.troopers.de/troopers17/ngi/&#34;&gt;Troopers NGI event&lt;/a&gt;).&lt;/p&gt;&#xA;&lt;p&gt;Some of this has already been discussed in &lt;a href=&#34;https://www.ietf.org/rfc/rfc4890.txt&#34;&gt;RFC 4890 Recommendations for Filtering ICMPv6 Messages in Firewalls&lt;/a&gt; but that document is from 2007 and things may have changed in the interim.&lt;br&gt;&#xA;Let’s start with a quick look at the traffic which might be of interest. We will take a server perspective here, read: which types of IPv6 traffic might have to be accepted by a host/NIC firewall in order to support proper operations? I will discuss the following, with a focus on the implications of filtering them locally:&lt;/p&gt;</description>
    </item>
    <item>
      <title>Testing RFC 6980 Implementations of FreeBSD</title>
      <link>https://insinuator.net/2017/06/testing-rfc-6980-implementations-of-freebsd/</link>
      <pubDate>Fri, 23 Jun 2017 00:00:00 +0000</pubDate>
      <guid>https://insinuator.net/2017/06/testing-rfc-6980-implementations-of-freebsd/</guid>
      <description>&lt;p&gt;Following Enno’s research on “&lt;a href=&#34;https://insinuator.net/2017/03/testing-rfc-6980-implementations-with-chiron/&#34;&gt;Testing RFC 6980 Implementations with Chiron&lt;/a&gt;“, we decided to redo the experiment with FreeBSD targets.&lt;/p&gt;&#xA;&lt;p&gt;The lab setup was very similar:&lt;/p&gt;&#xA;&lt;ul&gt;&#xA;&lt;li&gt;A Cisco Catalyst 3560 switch running the software “C3560c405ex-UNIVERSALK9-M” version 15.2(2)E4 connecting&lt;/li&gt;&#xA;&lt;li&gt;A Linux based attacker system running Chiron and&lt;/li&gt;&#xA;&lt;li&gt;A FreeBSD target system, running different OS versions and configurations and&lt;/li&gt;&#xA;&lt;li&gt;A Linux based laptop running a control script that remotely performed the necessary tasks on the two machines mentioned above&lt;/li&gt;&#xA;&lt;/ul&gt;&#xA;&lt;p&gt;The main question was: Would the impact on the target system and the possible attacks that were observed with the Windows Server 2016 victim be reproducible on other operating systems? Or would those behave totally differently?&lt;/p&gt;</description>
    </item>
    <item>
      <title>GDPR and Pseudonymisation – Easing the Pain of Regulation</title>
      <link>https://insinuator.net/2017/06/gdpr-and-pseudonymisation-easing-the-pain-of-regulation/</link>
      <pubDate>Wed, 21 Jun 2017 00:00:00 +0000</pubDate>
      <guid>https://insinuator.net/2017/06/gdpr-and-pseudonymisation-easing-the-pain-of-regulation/</guid>
      <description>&lt;p&gt;27 April 2016 marked a turning point for a lot of countries as well as a lot businesses worldwide: EU regulation 2016/679 (going by it’s more widely known name General Data Protection Regulation and abbreviated GDPR) was adopted by the European Parliament, the Council as well as the Commission [1]. Especially readers from countries outside of the EU might ask “Why should this be of interest for me?”.&lt;/p&gt;&#xA;&lt;p&gt;The point is: if your business is dealing with data of EU citizens (e.g. because you are having an online shop selling goods in the EU, or you operate a social network platform with customers that are EU citizens) you are liable under GDPR – this is regulated in Article 3, section 2 of the regulation: &lt;em&gt;“This Regulation applies to the processing of personal data of data subjects residing in the Union by a controller not established in the Union, where the processing activities are related to:&lt;/em&gt;&lt;br&gt;&#xA;&lt;em&gt;(a) the offering of goods or services to such data subjects in the Union; or&lt;/em&gt;&lt;br&gt;&#xA;&lt;em&gt;(b) the monitoring of their behaviour.”&lt;/em&gt;&lt;br&gt;&#xA;I’d guess that if you are reading these lines you become aware (if not have been so before) that your business might most probably be affected by GDPR as well. Now, the purpose of this blog post is not to enlighten you on the basics of GDPR but to discuss one special, interesting aspect of this regulation: pseudonymisation and how it might support your way to become compliant with GDPR.&lt;/p&gt;</description>
    </item>
    <item>
      <title>6th No-Spy Conference</title>
      <link>https://insinuator.net/2017/05/6th-no-spy-conference/</link>
      <pubDate>Mon, 22 May 2017 00:00:00 +0000</pubDate>
      <guid>https://insinuator.net/2017/05/6th-no-spy-conference/</guid>
      <description>&lt;p&gt;Last friday Florian and me attended the &lt;a href=&#34;https://no-spy.org/prismcamp/&#34;&gt;6th No-Spy Conference&lt;/a&gt; in Stuttgart, Germany. We gave a talk about surveillance and censorship on modern devices in North Korea and discussed various aspects with the attendees. The atmosphere was very welcoming and we had some nice discussions about various topics which allowed us to better clarify some things. The slides are available &lt;a href=&#34;https://www.ernw.de/download/nospy6_exploring_north_koreas_survelliance_technology.pdf&#34;&gt;here&lt;/a&gt;.&lt;/p&gt;&#xA;&lt;p&gt;Thanks to the organizers for having us!&lt;/p&gt;</description>
    </item>
    <item>
      <title>RIPE74 / Why IPv6 Security Is So Hard</title>
      <link>https://insinuator.net/2017/05/ripe74-/-why-ipv6-security-is-so-hard/</link>
      <pubDate>Fri, 12 May 2017 00:00:00 +0000</pubDate>
      <guid>https://insinuator.net/2017/05/ripe74-/-why-ipv6-security-is-so-hard/</guid>
      <description>&lt;p&gt;I’m on my way back from the &lt;a href=&#34;https://ripe74.ripe.net/&#34;&gt;RIPE74 meeting in Budapest&lt;/a&gt;. It was a great event: quite a few nice technical talks in the plenary, productive working group meetings and some really good hallway discussions.&lt;br&gt;&#xA;Big thanks to the RIPE NCC team for the smooth organization and for taking care of us!&lt;/p&gt;&#xA;&lt;p&gt;Here’s some stuff I found particularly interesting:&lt;/p&gt;&#xA;&lt;ul&gt;&#xA;&lt;li&gt;Andrew Alston’s take on “Anti-Shutdown Policies” (&lt;a href=&#34;https://ripe74.ripe.net/presentations/34-anti-shutdown-ripe.pdf&#34;&gt;slides&lt;/a&gt; and &lt;a href=&#34;https://ripe74.ripe.net/archives/video/41/&#34;&gt;video&lt;/a&gt; incl. extensive mic discussion)&lt;/li&gt;&#xA;&lt;li&gt;&lt;a href=&#34;https://twitter.com/pberndro&#34;&gt;Philip&lt;/a&gt; &amp;amp; &lt;a href=&#34;https://twitter.com/BarbarossaTM&#34;&gt;Maximilian&lt;/a&gt; from &lt;a href=&#34;https://www.freifunk-rheinland.net/&#34;&gt;Freifunk Rheinland&lt;/a&gt; on their efforts (&lt;a href=&#34;https://ripe74.ripe.net/presentations/46-as201701-ripe74.pdf&#34;&gt;slides&lt;/a&gt;, &lt;a href=&#34;https://ripe74.ripe.net/archives/video/47/&#34;&gt;video&lt;/a&gt;)&lt;/li&gt;&#xA;&lt;li&gt;Friso Feenstra on “That’s Why Rabobank Implemented IPv6” (&lt;a href=&#34;https://ripe74.ripe.net/presentations/3-That-is-why-Rabobank-has-IPv6.pdf&#34;&gt;slides&lt;/a&gt;, video) plus some insight into their address planning (&lt;a href=&#34;https://ripe74.ripe.net/presentations/4-Rabobank-corporate-IPv6-numberplan.pdf&#34;&gt;slides&lt;/a&gt;, &lt;a href=&#34;https://ripe74.ripe.net/archives/video/101/&#34;&gt;video&lt;/a&gt;)&lt;/li&gt;&#xA;&lt;li&gt;BCOP work on “&lt;a href=&#34;https://ripe74.ripe.net/presentations/132-Jan_Zorz-IPv6-prefix-delegations-BCOP-v-2.pdf&#34;&gt;IPv6 Prefix Assignments/Prefix Delegation&lt;/a&gt;” and “&lt;a href=&#34;https://ripe74.ripe.net/presentations/40-jan_zorz_IPv6-for-hosting-providers.pdf&#34;&gt;IPv6 Assignments for Hosting Providers&lt;/a&gt;“&lt;/li&gt;&#xA;&lt;li&gt;&lt;a href=&#34;https://twitter.com/lundstromjerry&#34;&gt;Jerry Lundström&lt;/a&gt;‘s DNS Replay Tool (&lt;a href=&#34;https://ripe74.ripe.net/presentations/79-RIPE74-DNSWG-drool.pdf&#34;&gt;slides&lt;/a&gt;, &lt;a href=&#34;https://ripe74.ripe.net/archives/video/161/&#34;&gt;video&lt;/a&gt;, &lt;a href=&#34;https://github.com/DNS-OARC/drool&#34;&gt;code&lt;/a&gt;)&lt;/li&gt;&#xA;&lt;li&gt;Jan Žorž (supported by Sander Steffann) on NAT64 testing (&lt;a href=&#34;https://ripe74.ripe.net/presentations/133-Jan_Zorz-NAT64-Check-v3.4.pdf&#34;&gt;slides&lt;/a&gt;, &lt;a href=&#34;https://ripe74.ripe.net/archives/video/160/&#34;&gt;video&lt;/a&gt;, &lt;a href=&#34;https://github.com/sjm-steffann/nat64check&#34;&gt;code&lt;/a&gt;)&lt;/li&gt;&#xA;&lt;/ul&gt;&#xA;&lt;p&gt;These were my own contributions:&lt;/p&gt;</description>
    </item>
    <item>
      <title>One Step Closer –  RDNSS (RFC 8106) Support in Windows 10 Creators Update</title>
      <link>https://insinuator.net/2017/05/one-step-closer-rdnss-rfc-8106-support-in-windows-10-creators-update/</link>
      <pubDate>Mon, 08 May 2017 00:00:00 +0000</pubDate>
      <guid>https://insinuator.net/2017/05/one-step-closer-rdnss-rfc-8106-support-in-windows-10-creators-update/</guid>
      <description>&lt;p&gt;Good Afternoon,&lt;/p&gt;&#xA;&lt;p&gt;It is a pleasant surprise for many (us included) that Microsoft implemented support for the RDNSS (&lt;a href=&#34;https://tools.ietf.org/html/rfc8106&#34;&gt;RFC 8106&lt;/a&gt;) option in Router Advertisements beginning with the &lt;a href=&#34;https://blogs.technet.microsoft.com/windowsitpro/2017/04/05/whats-new-for-it-pros-in-the-windows-10-creators-update/&#34;&gt;Windows 10 Creators Update&lt;/a&gt;. Interestingly, I wasn’t able to find any official documents from Microsoft stating this. As we are involved in a lot of IPv6 related projects for our customers, the lack of RDNSS support for Windows and DHCPv6 for Android is a major pain point when implementing IPv6 in mixed client segments, as you need to implement both mechanisms to ensure that all clients do get the relevant network parameters. I won’t beat on the dead horse, but Microsoft’s decision is a huge step in the right direction and one can hope that one day Google finds a “compelling use case” to implement at least stateless DHCPv6 for Android.&lt;/p&gt;</description>
    </item>
    <item>
      <title>(Mostly) New, Interesting, and Security-focused Open Source Projects</title>
      <link>https://insinuator.net/2017/04/mostly-new-interesting-and-security-focused-open-source-projects/</link>
      <pubDate>Mon, 03 Apr 2017 00:00:00 +0000</pubDate>
      <guid>https://insinuator.net/2017/04/mostly-new-interesting-and-security-focused-open-source-projects/</guid>
      <description>&lt;p&gt;&lt;a href=&#34;http://www.troopers.de/&#34;&gt;Troopers ’17&lt;/a&gt; – the 10th edition – madness is over and hopefully all of you are well rested and recovered after this special week. Of course the rest of the world did not stand still and thus Google lifted the curtains on a new public portal collecting and promoting the Open Source Software projects developed by employees of Google: &lt;a href=&#34;http://opensource.google.com/&#34;&gt;opensource.google.com&lt;/a&gt;. There are a lot of interesting projects that might incubate new interesting developments. And even security oriented tools and projects (51 at the time of writing to be precise) are publically available [1].&lt;/p&gt;</description>
    </item>
    <item>
      <title>Testing RFC 6980 Implementations with Chiron</title>
      <link>https://insinuator.net/2017/03/testing-rfc-6980-implementations-with-chiron/</link>
      <pubDate>Sat, 11 Mar 2017 00:00:00 +0000</pubDate>
      <guid>https://insinuator.net/2017/03/testing-rfc-6980-implementations-with-chiron/</guid>
      <description>&lt;p&gt;In the &lt;a href=&#34;https://insinuator.net/2017/01/ipv6-properties-of-windows-server-2016-windows-10/&#34;&gt;recent post&lt;/a&gt; on the IPv6 properties of the latest MS Windows versions I announced another one providing details on the &lt;a href=&#34;https://tools.ietf.org/rfc/rfc6980.txt&#34;&gt;RFC 6980&lt;/a&gt; related testing I had performed. So here we go.&lt;/p&gt;&#xA;&lt;p&gt;When doing IPv6 security testing there’s mainly four toolkits which can be used:&lt;/p&gt;&#xA;&lt;ul&gt;&#xA;&lt;li&gt;&lt;a href=&#34;https://twitter.com/AntoniosAtlasis&#34;&gt;Antonios Atlasis&lt;/a&gt;‘ &lt;a href=&#34;https://www.secfu.net/tools-scripts/&#34;&gt;Chiron&lt;/a&gt;&lt;/li&gt;&#xA;&lt;li&gt;Marc Heuse’s &lt;a href=&#34;https://github.com/vanhauser-thc/thc-ipv6&#34;&gt;THC-IPV6&lt;/a&gt;&lt;/li&gt;&#xA;&lt;li&gt;&lt;a href=&#34;https://twitter.com/FernandoGont&#34;&gt;Fernando Gont&lt;/a&gt;‘s &lt;a href=&#34;https://www.si6networks.com/tools/ipv6toolkit/&#34;&gt;IPv6 Toolkit&lt;/a&gt;&lt;/li&gt;&#xA;&lt;li&gt;&lt;a href=&#34;http://www.secdev.org/projects/scapy/&#34;&gt;Scapy&lt;/a&gt; (whose IPv6 capabilities are, afaik, mainly maintained by &lt;a href=&#34;https://twitter.com/guedou&#34;&gt;Guillaume Valadon&lt;/a&gt;. some tutorial on IPv6 packet crafting with scapy can &lt;a href=&#34;https://www.ernw.de/download/Advanced%20Attack%20Techniques%20against%20IPv6%20Networks-final.pdf&#34;&gt;be found here&lt;/a&gt;).&lt;/li&gt;&#xA;&lt;/ul&gt;&#xA;&lt;p&gt;Each of them has specific strenghts &amp;amp; limits, which will not be discussed here. For the testing I performed I chose Chiron as it has the most powerful options when it comes to IPv6 extension headers and fragmentation.&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>Exploitation of IMS in absence of confidentiality and integrity protection</title>
      <link>https://insinuator.net/2017/02/exploitation-of-ims-in-absence-of-confidentiality-and-integrity-protection/</link>
      <pubDate>Fri, 17 Feb 2017 00:00:00 +0000</pubDate>
      <guid>https://insinuator.net/2017/02/exploitation-of-ims-in-absence-of-confidentiality-and-integrity-protection/</guid>
      <description>&lt;p&gt;IP Multimedia Subsystem (IMS) offers many multimedia services to any IP-based access network, such as LTE or DSL. In addition to VoLTE, IMS adds service provider flexibility, better QoS and charging control to the 4th generation of mobile networks. IMS exchanges SIP messages with its users or other IMS and usually these communications are secured by TLS or IPSec. But if an attacker manages to break the confidentiality and the integrity with IMS, he would find it vulnerable to several attacks.&lt;/p&gt;</description>
    </item>
    <item>
      <title>White Paper on Incident Handling First Steps, Preparation Plans, and Process Models</title>
      <link>https://insinuator.net/2017/02/white-paper-on-incident-handling-first-steps-preparation-plans-and-process-models/</link>
      <pubDate>Wed, 01 Feb 2017 00:00:00 +0000</pubDate>
      <guid>https://insinuator.net/2017/02/white-paper-on-incident-handling-first-steps-preparation-plans-and-process-models/</guid>
      <description>&lt;p&gt;We just published my &lt;a href=&#34;https://www.ernw.de/download/newsletter/ERNW_Whitepaper58_IncidentHandlingFirstSteps_signed.pdf&#34;&gt;Whitepaper about First Steps, Preparation Plans, and Process Models for Incident Handling&lt;/a&gt;, that I wrote to pass the time between Christmas and New Year. The whitepaper sums up information that I consider to be useful to prepare for IT security incidents as a conclusion from the incidents in which we supported over the past year.&lt;/p&gt;&#xA;&lt;p&gt;&lt;a href=&#34;https://www.ernw.de/download/newsletter/ERNW_Whitepaper58_IncidentHandlingFirstSteps_signed.pdf&#34;&gt;&lt;img src=&#34;teaser.jpg&#34; alt=&#34;&#34;&gt;&lt;/a&gt;&lt;/p&gt;&#xA;&lt;p&gt;Have you for example thought about classes of incidents that are most likely to affect you and formulated Incident Handling Preparation Plans for those incidents?&lt;/p&gt;</description>
    </item>
    <item>
      <title>Woolim – Lifting the Fog on DPRK’s Latest Tablet PC</title>
      <link>https://insinuator.net/2016/12/woolim-lifting-the-fog-on-dprks-latest-tablet-pc/</link>
      <pubDate>Wed, 28 Dec 2016 00:00:00 +0000</pubDate>
      <guid>https://insinuator.net/2016/12/woolim-lifting-the-fog-on-dprks-latest-tablet-pc/</guid>
      <description>&lt;p&gt;Niklaus, Manuel and me had a great time speaking about one of the latest Tablet PCs from DPRK at &lt;a href=&#34;https://fahrplan.events.ccc.de/congress/2016/Fahrplan/events/8143.html&#34;&gt;33C3 this year&lt;/a&gt;. Our work on &lt;a href=&#34;https://insinuator.net/2015/07/redstar-os-watermarking/&#34;&gt;RedStar OS from last year&lt;/a&gt; revealed a nasty watermarking mechanism that can be used to track the origin and distribution path of media files in North Korea. We have seen some interesting dead code in some of RedStar’s binaries that indicated a more sophisticated mechanism to control the distribution of media files. We got hands on a Tablet PC called “Ul-lim” that implemented this advanced control mechanism.&lt;/p&gt;</description>
    </item>
    <item>
      <title>Research Diary: Bluetooth. Part 2</title>
      <link>https://insinuator.net/2016/12/research-diary-bluetooth.-part-2/</link>
      <pubDate>Wed, 07 Dec 2016 00:00:00 +0000</pubDate>
      <guid>https://insinuator.net/2016/12/research-diary-bluetooth.-part-2/</guid>
      <description>&lt;p&gt;Recently we posted &lt;a href=&#34;https://insinuator.net/2016/11/research-diary-bluetooth/&#34;&gt;first part&lt;/a&gt; of our Bluetooth research diary. Today, we want to continue on that topic and tell you about Bluetooth proxying and packet replay with a new tool.&lt;/p&gt;&#xA;&lt;p&gt;This time we had a new gadget to play with: our colleague Florian Grunow shared with us a curious IoT device – Bluetooth socks… real socks that you control with an app to heat your feet. The future is here… 😉&lt;br&gt;&#xA;&lt;img src=&#34;IMG_20161129_095613.jpg&#34; alt=&#34;img_20161129_095613&#34;&gt;&lt;/p&gt;</description>
    </item>
    <item>
      <title>Research Diary: Bluetooth</title>
      <link>https://insinuator.net/2016/11/research-diary-bluetooth/</link>
      <pubDate>Tue, 22 Nov 2016 00:00:00 +0000</pubDate>
      <guid>https://insinuator.net/2016/11/research-diary-bluetooth/</guid>
      <description>&lt;p&gt;As you probably know we perform research on a regular base at ERNW.&lt;/p&gt;&#xA;&lt;p&gt;We – Olga and Rafael – started with a research project about Bluetooth. Our first goal was to gain some knowledge about the tools used by most Linux systems to communicate with Bluetooth hardware, such as BlueZ. A good help for that was the amazing Bluetooth hacking workshop we had before (check &lt;a href=&#34;https://www.insinuator.net/2016/09/hardware-hacking-week-ernw/&#34;&gt;the link&lt;/a&gt; in our blog!)&lt;/p&gt;&#xA;&lt;p&gt;To get a better understanding of the tools you need some Bluetooth hardware to interact with.&lt;br&gt;&#xA;The hardware we used for our research so far are the very cool TexasInstruments SimpleLink™ Bluetooth low energy/Multi-standard SensorTag (CC2650STK) and a Fitness Wristband found at home.&lt;/p&gt;</description>
    </item>
    <item>
      <title>A Journey Into the Depths of VoWiFi Security</title>
      <link>https://insinuator.net/2016/10/a-journey-into-the-depths-of-vowifi-security/</link>
      <pubDate>Thu, 20 Oct 2016 00:00:00 +0000</pubDate>
      <guid>https://insinuator.net/2016/10/a-journey-into-the-depths-of-vowifi-security/</guid>
      <description>&lt;p&gt;T-mobile pioneered with the native seamless support for WiFi calling technology embedded within the smartphones. This integrated WiFi calling feature is adopted by most major providers as well as many smartphones today. T-mobile introduced VoWiFi in Germany in May 2016. You can make voice calls that allows to switch between LTE and WiFi networks seamlessly. This post is going to be about security analysis of Voice over WiFi (VoWiFi), another name for WiFi calling, from the user end. Before we get started, let me warn you in advance. If you are not familiar with telecommunication network protocols, then you might get lost in the heavy usage of acronyms and abbreviations. I am sorry about that. But trust me, after a while, you get used to it 🙂 .&lt;/p&gt;</description>
    </item>
    <item>
      <title>Welcome to Insinuator.net 2.0</title>
      <link>https://insinuator.net/2016/10/welcome-to-insinuator.net-2.0/</link>
      <pubDate>Fri, 14 Oct 2016 00:00:00 +0000</pubDate>
      <guid>https://insinuator.net/2016/10/welcome-to-insinuator.net-2.0/</guid>
      <description>&lt;p&gt;It’s almost exactly seven years since Enno published the very first blog post on Insinuator.net. Meanwhile, quite a few things changed. It’s not only the &lt;em&gt;ERNW Universe&lt;/em&gt; which grew significantly, but also Insinuator’s place within this universe was slightly adjusted. What started as an almost independent IT-Security blog became more and more the major publication medium of ERNW.&lt;/p&gt;&#xA;&lt;p&gt;Therefore, we thought it would be a good time to reflect these changes. Today we release the 2.0 version of Insinuator.net. 2.0 introduces a new look &amp;amp; feel as well as major redesign from a technical point of view while also reflecting Insinuator’s place between the four major players in the ERNW universe:&lt;/p&gt;</description>
    </item>
    <item>
      <title>Introducing the Kernel Space Invaders</title>
      <link>https://insinuator.net/2016/09/introducing-the-kernel-space-invaders/</link>
      <pubDate>Tue, 20 Sep 2016 00:00:00 +0000</pubDate>
      <guid>https://insinuator.net/2016/09/introducing-the-kernel-space-invaders/</guid>
      <description>&lt;p&gt;Today it is my pleasure to shortly introduce ERNW’s Capture the Flag team, the Kernel Space Invaders. As a long-time CTF enthusiast, I’m really amazed how many of us make the time to tackle IT security challenges also on the weekends or evenings. Even if we cannot participate in all CTFs out there (which would be challenging anyways given the &lt;a href=&#34;https://ctftime.org/&#34;&gt;large number of CTF events&lt;/a&gt; happening nowadays), we started to compile a &lt;a href=&#34;https://github.com/ernw/ctf-writeups/&#34;&gt;repository&lt;/a&gt; of some of our write-ups — I hope some of you will enjoy!&lt;/p&gt;</description>
    </item>
    <item>
      <title>To Control Something</title>
      <link>https://insinuator.net/2016/09/to-control-something/</link>
      <pubDate>Sat, 10 Sep 2016 00:00:00 +0000</pubDate>
      <guid>https://insinuator.net/2016/09/to-control-something/</guid>
      <description>&lt;p&gt;Some years ago I discussed the meaning of the term “control” in &lt;a href=&#34;https://www.insinuator.net/2011/06/broken-trust-part-1-definitions-fundamentals-some-more-reflections-on-rsa/&#34;&gt;this post&lt;/a&gt;, but at the time I was mainly referring to the noun “control”. Given I’ll extensively use the term “control” as a verb in the next parts of “the &lt;a href=&#34;https://www.insinuator.net/2016/08/considerations-on-dmz-design-in-2016-part-1/&#34;&gt;DMZ&lt;/a&gt; &lt;a href=&#34;https://www.insinuator.net/2016/09/considerations-on-dmz-design-in-2016-part-2-a-quick-digression-on-reverse-proxies/&#34;&gt;series&lt;/a&gt;” and some &lt;a href=&#34;http://hardwear.io/schedule_hardwear/&#34;&gt;upcoming&lt;/a&gt; &lt;a href=&#34;http://www.day-con.org/schedule.htm&#34;&gt;talks&lt;/a&gt; I reflected a bit on its meaning (as a verb). In the following I’ll lay out the definition/understanding to be employed at those occasions.&lt;/p&gt;&#xA;&lt;p&gt;&lt;a href=&#34;http://www.merriam-webster.com/dictionary/control&#34;&gt;Merriam-Webster&lt;/a&gt; defines, amongst others, as follows:&lt;/p&gt;</description>
    </item>
    <item>
      <title>Another Perspective in Vulnerability Disclosure</title>
      <link>https://insinuator.net/2016/01/another-perspective-in-vulnerability-disclosure/</link>
      <pubDate>Thu, 07 Jan 2016 00:00:00 +0000</pubDate>
      <guid>https://insinuator.net/2016/01/another-perspective-in-vulnerability-disclosure/</guid>
      <description>&lt;p&gt;As you know we (as in &lt;a href=&#34;https://www.ernw.de/&#34;&gt;ERNW&lt;/a&gt;) are quite involved when it comes to vulnerability disclosure and we’ve tried to contribute to a discussion at several occasions, such as &lt;a href=&#34;https://www.insinuator.net/2015/07/reflections-on-vulnerability-disclosure/&#34;&gt;Reflections on Vulnerability Disclosure&lt;/a&gt; and &lt;a href=&#34;https://www.ernw.de/download/ERNW_Newsletter_50_Vulnerability_Disclosure_Reflections_CaseStudy.pdf&#34;&gt;ERNW Newsletter 50 Vulnerability Disclosure Reflections Case Study&lt;/a&gt;.&lt;/p&gt;&#xA;&lt;p&gt;In this post I want to add (yet) another perspective, motivated by a disclosure procedure which just happened recently.&lt;/p&gt;&#xA;&lt;p&gt;&lt;a href=&#34;https://twitter.com/todb&#34;&gt;todb’s&lt;/a&gt;  article, &lt;a href=&#34;https://community.rapid7.com/community/infosec/blog/2016/01/05/r7-2015-23-comcast-xfinity-home-security-system-insecure-fail-open&#34;&gt;R7-2015-23: Comcast XFINITY Home Security System Insecure Fail Open&lt;/a&gt; is a well planned public forum vulnerability disclosure. The article itself is very well done: It gives credit to the researcher who discovered the vulnerability and it shows a vulnerability disclosure timeline where Rapid7 reached out to Comcast (the vendor). They even go a step further and publish the link showing the process for discovered vulnerabilities in a Rapid7 product as well as how Rapid7 handles disclosing those vulnerabilities they find in external products. For their internal disclosure process, they make sure to release a patch &lt;em&gt;before&lt;/em&gt; “publicly announcing the vulnerability in the release notes of the update”(&lt;a href=&#34;http://www.rapid7.com/disclosure.jsp&#34;&gt;rapid7 disclosure&lt;/a&gt;).&lt;/p&gt;</description>
    </item>
    <item>
      <title>Sending Mixed Signals – What Can Happen in the Course of Vulnerability Disclosure</title>
      <link>https://insinuator.net/2015/09/sending-mixed-signals-what-can-happen-in-the-course-of-vulnerability-disclosure/</link>
      <pubDate>Thu, 10 Sep 2015 00:00:00 +0000</pubDate>
      <guid>https://insinuator.net/2015/09/sending-mixed-signals-what-can-happen-in-the-course-of-vulnerability-disclosure/</guid>
      <description>&lt;p&gt;&lt;strong&gt;Update:&lt;/strong&gt;&lt;/p&gt;&#xA;&lt;p&gt;Given there’s quite some speculation and, as we think, misinformation going around we think it’s helpful to add/clarify the following information:&lt;/p&gt;&#xA;&lt;ul&gt;&#xA;&lt;li&gt;we fully comply with the injunction and we have no intentions to violate it. we do not plan to publish any technical information besides the report (agreed upon with FireEye themselves) and the slides (based on the former) anyway. No 3rd parties except for the ones involved (FireEye, lawyers) have received any additional technical information from our side, let alone an earlier version of the report.&lt;/li&gt;&#xA;&lt;li&gt;the injunction covers accompanying details mostly within the architecture space, but not the core vulnerabilities themselves. Those are not part of the injunction.&lt;/li&gt;&#xA;&lt;li&gt;we stand by the timeline as provided below. In particular, the following two points:&lt;br&gt;&#xA;– FireEye received a draft version of the report which had the objectionable material (as identified by the cease and desist letter) fully removed on August 11th.&lt;br&gt;&#xA;– according to the cease and desist letter FireEye’s lawyer sent us, they were informed – from our side – about the planned talk at 44CON on Jul 23rd.&lt;/li&gt;&#xA;&lt;li&gt;there’s an injunction, but not a lawsuit. I used the term “sue” after consulting &lt;a href=&#34;http://www.merriam-webster.com/dictionary/sue&#34;&gt;Merriam-Webster&lt;/a&gt; which states: “sue: to seek justice or right from (a person) by legal process”, but this might have been misinterpreted by some readers. As stated, there’s a pending injunction, but not a lawsuit.&lt;/li&gt;&#xA;&lt;/ul&gt;&#xA;&lt;p&gt;Please note that we won’t share legal documents with 3rd parties or publish them as we consider this inappropriate.&lt;br&gt;&#xA;Please note further that, during the whole process, our goal was to perform a responsible disclosure procedure with its inherent objectives (namely vulnerability remediation by vendor and education of various stakeholders involved, see also &lt;a href=&#34;https://www.ernw.de/download/ERNW_Newsletter_50_Vulnerability_Disclosure_Reflections_CaseStudy.pdf&#34;&gt;here&lt;/a&gt; or &lt;a href=&#34;https://www.insinuator.net/2015/07/reflections-on-vulnerability-disclosure/&#34;&gt;here&lt;/a&gt;). We consider this disclosure process as concluded. We don’t see a need to add technical details from our side as we feel that the objectives of responsible disclosure are met (not least as patches are released since quite some time and both &lt;a href=&#34;https://www.fireeye.com/content/dam/fireeye-www/support/pdfs/fireeye-ernw-vulnerability.pdf&#34;&gt;vendor&lt;/a&gt; &amp;amp; finder have released reports).&lt;/p&gt;</description>
    </item>
    <item>
      <title>Solving sound issues when using WebEx with Linux and Firefox</title>
      <link>https://insinuator.net/2015/07/solving-sound-issues-when-using-webex-with-linux-and-firefox/</link>
      <pubDate>Wed, 15 Jul 2015 00:00:00 +0000</pubDate>
      <guid>https://insinuator.net/2015/07/solving-sound-issues-when-using-webex-with-linux-and-firefox/</guid>
      <description>&lt;p&gt;Hello everybody,&lt;/p&gt;&#xA;&lt;p&gt;Some of you might use WebEx in their daily life. And some of you might use Linux (as I and many of us do). However, this combination often results in issues with your PC’s sound or microphone use in a WebEx session.&lt;/p&gt;&#xA;&lt;p&gt;The problem here is that WebEx won’t run as intended with Firefox and JRE x64. But the solution is quite easy! Use the x86-versions of each.&lt;/p&gt;</description>
    </item>
    <item>
      <title>Reflections on Vulnerability Disclosure</title>
      <link>https://insinuator.net/2015/07/reflections-on-vulnerability-disclosure/</link>
      <pubDate>Tue, 14 Jul 2015 00:00:00 +0000</pubDate>
      <guid>https://insinuator.net/2015/07/reflections-on-vulnerability-disclosure/</guid>
      <description>&lt;p&gt;In this post I’ll discuss some aspects of vulnerability disclosure. I don’t want to delve into an abstract &amp;amp; general discussion of vulnerability disclosure (for those interested &lt;a href=&#34;http://googleprojectzero.blogspot.de/2015/02/feedback-and-data-driven-updates-to.html&#34;&gt;here’s some discussion&lt;/a&gt; in the context of Google’s Project Zero, &lt;a href=&#34;http://www.cert.org/vulnerability-analysis/vul-disclosure.cfm&#34;&gt;this is the well-known CERT/CC approach&lt;/a&gt;, &lt;a href=&#34;http://weis2006.econinfosec.org/docs/17.pdf&#34;&gt;this a paper from WEIS 2006&lt;/a&gt; laying out some variants, and finally &lt;a href=&#34;https://www.schneier.com/essays/archives/2007/01/schneier_full_disclo.html&#34;&gt;some statement by Bruce Schneier back in 2007&lt;/a&gt;). Instead I will lay out which approach we followed in the past (and why we did so) and which developments make us consider it necessary to re-think our way of handling. The post is not meant to provide definitive answers; it was also written not least to provide clarity for ourselves (“write down a problem in order to better penetrate it”) and, maybe, to serve as a starting point for a discussion which will help the community (and us) to find a position on some of the inherent challenges.&lt;/p&gt;</description>
    </item>
    <item>
      <title>Main IPv6 Related Mailing Lists</title>
      <link>https://insinuator.net/2015/01/main-ipv6-related-mailing-lists/</link>
      <pubDate>Sat, 17 Jan 2015 00:00:00 +0000</pubDate>
      <guid>https://insinuator.net/2015/01/main-ipv6-related-mailing-lists/</guid>
      <description>&lt;p&gt;We’re sometimes approached with the question “Which IPv6 mailing lists do you guys read/subscribe to?” – here’s a quick overview of the main ones guys like Christopher, Patrick, Rafael, Antonios and myself are periodically lurking at, to discuss IPv6 (network|security) related stuff with other practitioners and to learn from them:&lt;/p&gt;&#xA;&lt;p&gt;ipv6-ops.&lt;br&gt;&#xA;This list is a forum for people who are actually deploying IPv6 in the Internet. Its focus is on OPERATIONAL issues.&lt;br&gt;&#xA;&lt;a href=&#34;http://lists.cluenet.de/mailman/listinfo/ipv6-ops/&#34;&gt;http://lists.cluenet.de/mailman/listinfo/ipv6-ops/&lt;/a&gt;&lt;/p&gt;</description>
    </item>
    <item>
      <title>Skeleton Key – a Nasty Piece of Malware. Some Remarks.</title>
      <link>https://insinuator.net/2015/01/skeleton-key-a-nasty-piece-of-malware.-some-remarks./</link>
      <pubDate>Thu, 15 Jan 2015 00:00:00 +0000</pubDate>
      <guid>https://insinuator.net/2015/01/skeleton-key-a-nasty-piece-of-malware.-some-remarks./</guid>
      <description>&lt;p&gt;Just recently, Dell SecureWorks Counter Threat Unit(TM) (CTU) researchers published details (see &lt;a href=&#34;http://www.secureworks.com/cyber-threat-intelligence/threats/skeleton-key-malware-analysis/&#34;&gt;http://www.secureworks.com/cyber-threat-intelligence/threats/skeleton-key-malware-analysis/&lt;/a&gt; ) on a especially nasty piece of malware that bypasses authentication on Active Directory (AD) systems which implement single-factor (password only) authentication. Once deployed the malware stays quite noiseless in the Domain Controller´s (DC) RAM, and the DC´s replication issues caused by it weren´t interpreted – in this case – during months as a hint for system compromise. Probably the malware´s modification on the LSASS process reduced the DC´s ability to perform DC-to-DC authentication, but this is only speculation and not where we would like to go today.&lt;/p&gt;</description>
    </item>
    <item>
      <title>Security Implications of Disruptive Technologies</title>
      <link>https://insinuator.net/2014/09/security-implications-of-disruptive-technologies/</link>
      <pubDate>Sat, 20 Sep 2014 00:00:00 +0000</pubDate>
      <guid>https://insinuator.net/2014/09/security-implications-of-disruptive-technologies/</guid>
      <description>&lt;p&gt;Yesterday I gave a talk with the above title in a private setting. Given it might be of interest for some of you, the slides can be found &lt;a href=&#34;https://www.ernw.de/download/ERNW_Security_Implications_of_Disruptive_Technologies_web.pdf&#34;&gt;here&lt;/a&gt;.&lt;/p&gt;&#xA;&lt;p&gt;Have a great weekend everybody&lt;/p&gt;&#xA;&lt;p&gt;Enno&lt;/p&gt;</description>
    </item>
    <item>
      <title>ASCII Protocol Scheme Generator</title>
      <link>https://insinuator.net/2014/05/ascii-protocol-scheme-generator/</link>
      <pubDate>Thu, 08 May 2014 00:00:00 +0000</pubDate>
      <guid>https://insinuator.net/2014/05/ascii-protocol-scheme-generator/</guid>
      <description>&lt;p&gt;As we historically have a strong connection to network technologies (not surprising, given the “NW” in “ERNW” stands for “Networks”), I developed a small script to create RFC-style ASCII representations of protocol schemes. The following listing shows an example created for a fictitious protocol:&lt;/p&gt;&#xA;&lt;pre&gt;&lt;code&gt; 0                   1                   2                   3  &#xA; 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1&#xA;+---------------------------------------------------------------+&#xA;|             type              |              id               |&#xA;+---------------------------------------------------------------+&#xA;|     flags     |                   reserved                    |&#xA;+---------------------------------------------------------------+&#xA;|                            payload                            |&#xA;+---------------------------------------------------------------+&#xA;&lt;/code&gt;&lt;/pre&gt;&#xA;&lt;p&gt; &lt;/p&gt;</description>
    </item>
    <item>
      <title>The Impact of Pervasive Monitoring on Corporate InfoSec</title>
      <link>https://insinuator.net/2013/10/the-impact-of-pervasive-monitoring-on-corporate-infosec/</link>
      <pubDate>Wed, 23 Oct 2013 00:00:00 +0000</pubDate>
      <guid>https://insinuator.net/2013/10/the-impact-of-pervasive-monitoring-on-corporate-infosec/</guid>
      <description>&lt;p&gt;A few weeks ago I gave a presentation with the above title at some corporate infosec event. Given I’ve been asked for the slides many times now, I’ve converted them to a PDF which can be found &lt;a href=&#34;https://www.ernw.de/download/ERNW_Pervasive_Monitoring_Corporate_InfoSec_web.pdf&#34;&gt;here&lt;/a&gt;.&lt;/p&gt;&#xA;&lt;p&gt;We hope to contribute to the necessary debate thereby…&lt;/p&gt;&#xA;&lt;p&gt;Have a good one,&lt;/p&gt;&#xA;&lt;p&gt;Enno&lt;/p&gt;</description>
    </item>
    <item>
      <title>Responsible Disclosure and Academic Freedom, Again</title>
      <link>https://insinuator.net/2013/07/responsible-disclosure-and-academic-freedom-again/</link>
      <pubDate>Sat, 27 Jul 2013 00:00:00 +0000</pubDate>
      <guid>https://insinuator.net/2013/07/responsible-disclosure-and-academic-freedom-again/</guid>
      <description>&lt;p&gt;Reading &lt;a href=&#34;http://www.guardian.co.uk/technology/2013/jul/26/scientist-banned-revealing-codes-cars&#34;&gt;this article&lt;/a&gt; from the Guardian,  on &lt;a href=&#34;http://www.cs.ru.nl/~flaviog/&#34;&gt;this guy&lt;/a&gt; apparently being banned from fully discussing research results in &lt;a href=&#34;https://www.usenix.org/conference/usenixsecurity13/dismantling-megamos-crypto-wirelessly-lockpicking-vehicle-immobilizer&#34;&gt;his talk&lt;/a&gt; at upcoming &lt;a href=&#34;https://www.usenix.org/conference/usenixsecurity13&#34;&gt;USENIX Security&lt;/a&gt;, leaves me scratching my head once more. Things might (as so often) be more complex than they seem, but this looks like yet-another misconception as for the contribution of security research (and its public discussion) to the greater good of us all. Which is unfortunate for the speakers (I’ve been in a similar situation once, receiving a threatening legal letter from a very large organization one day before one of our Black Hat presentations and can tell you that stuff like that doesn’t add to one’s anticipation of the talk or the event…), for the audience (including some ERNW guys who will be a USENIX-SEC, so, btw, expect a summary post here) and for the whole community of security researchers.&lt;/p&gt;</description>
    </item>
    <item>
      <title>Ganz Gallien?</title>
      <link>https://insinuator.net/2013/07/ganz-gallien/</link>
      <pubDate>Sun, 14 Jul 2013 00:00:00 +0000</pubDate>
      <guid>https://insinuator.net/2013/07/ganz-gallien/</guid>
      <description>&lt;p&gt;“Nein! Ein von unbeugsamen Galliern bevölkertes Dorf hört nicht auf, dem Eindringling Widerstand zu leisten.”&lt;/p&gt;&#xA;&lt;p&gt;This is a famous quote pretty much every German kid used to know. Not sure if this still applies though, my three haven’t touched Asterix comics so far. Anyhow, you might ask why I cite this.&lt;/p&gt;&#xA;&lt;p&gt;Simple answer: see &lt;a href=&#34;http://www.guardian.co.uk/world/2013/jul/09/xmission-isp-customers-privacy-nsa&#34;&gt;this recent article&lt;/a&gt; from the Guardian on a Utah-based ISP “resisting some pressure”. That’s the spirit…&lt;/p&gt;&#xA;&lt;p&gt;Have a great Sunday everybody,&lt;/p&gt;</description>
    </item>
    <item>
      <title>The 5 Myths of Web Application Firewalls</title>
      <link>https://insinuator.net/2012/04/the-5-myths-of-web-application-firewalls/</link>
      <pubDate>Mon, 16 Apr 2012 00:00:00 +0000</pubDate>
      <guid>https://insinuator.net/2012/04/the-5-myths-of-web-application-firewalls/</guid>
      <description>&lt;p&gt;Some days ago a security advisory related to web application firewalls (WAFs) was published on Full Disclosure. Wendel Guglielmetti Henrique found another bug in the IBM Web Application Firewall which can be used to circumvent the WAF and execute typical web application attacks like SQL injection (click &lt;a href=&#34;http://lists.grok.org.uk/pipermail/full-disclosure/2011-June/081605.html&#34;&gt;here&lt;/a&gt; for details). Wendel talked already (look &lt;a href=&#34;http://troopers09.org/content/e644/e649/TROOPERS09_gauci_henrique_web_application_firewalls.pdf%20&#34;&gt;here&lt;/a&gt;) at the &lt;a href=&#34;http://www.troopers.de&#34;&gt;Troopers&lt;/a&gt; Conference in 2009 about the different techniques to identify and bypass WAFs, so this kind of bypass methods are not quite new.&lt;/p&gt;</description>
    </item>
    <item>
      <title>Sell Your Own Device – A Field Study on Decommissioning of Mobile Devices</title>
      <link>https://insinuator.net/2012/02/sell-your-own-device-a-field-study-on-decommissioning-of-mobile-devices/</link>
      <pubDate>Tue, 28 Feb 2012 00:00:00 +0000</pubDate>
      <guid>https://insinuator.net/2012/02/sell-your-own-device-a-field-study-on-decommissioning-of-mobile-devices/</guid>
      <description>&lt;p&gt;On Friday we released our latest technical newsletter with the fancy title &lt;em&gt;“Sell Your Own Device – A Field Study on Decommissioning of Mobile Devices”&lt;/em&gt;. It is the result of a field study on decommissioned mobile business devices bought on eBay and about how stored data may be extracted in different ways.&lt;/p&gt;&#xA;&lt;p&gt;As always we love to share plenty of practical advise: At the end of the newsletter you will find the mitigating controls to securely handle mobile devices at the end of their life cycle process.&lt;/p&gt;</description>
    </item>
    <item>
      <title>On the discussion about the iTunes 10.5.1 update</title>
      <link>https://insinuator.net/2011/11/on-the-discussion-about-the-itunes-10.5.1-update/</link>
      <pubDate>Mon, 28 Nov 2011 00:00:00 +0000</pubDate>
      <guid>https://insinuator.net/2011/11/on-the-discussion-about-the-itunes-10.5.1-update/</guid>
      <description>&lt;p&gt;Currently there’s &lt;a href=&#34;http://krebsonsecurity.com/2011/11/apple-took-3-years-to-fix-finfisher-trojan-hole/&#34;&gt;quite some discussion&lt;/a&gt; ongoing why it took Apple so long to fix a &lt;a href=&#34;http://support.apple.com/kb/HT5030&#34;&gt;severe vulnerability in the update process&lt;/a&gt; of iTunes. A severe vulnerability which could easily be exploited by means of an automated tool called &lt;a href=&#34;http://www.infobytesec.com/down/isr-evilgrade-Readme.txt&#34;&gt;evilgrade&lt;/a&gt; which can be downloaded &lt;a href=&#34;http://www.infobytesec.com/developments.html&#34;&gt;here&lt;/a&gt; (Hi Francisco!). Just one small note here: did you know that evilgrade was first shown and released at the &lt;a href=&#34;http://www.troopers08.org/content/&#34;&gt;2008 edition&lt;/a&gt; of &lt;a href=&#34;http://www.troopers.de&#34;&gt;Troopers&lt;/a&gt;? We had a number of initial releases of tools in the last years (like &lt;a href=&#34;http://code.google.com/p/waffit/source/browse/trunk/wafw00f.py&#34;&gt;wafw00f&lt;/a&gt; at the &lt;a href=&#34;http://www.troopers09.org/content/&#34;&gt;2009 edition&lt;/a&gt; and &lt;a href=&#34;http://vasto.nibblesec.org/&#34;&gt;VASTO&lt;/a&gt; at the &lt;a href=&#34;http://www.troopers10.org/content/e3/index_eng.html&#34;&gt;2010 edition&lt;/a&gt;) and we will continue this fine tradition in 2012. I can already promise that some nice code is going to be released for the first time at Troopers12…&lt;/p&gt;</description>
    </item>
    <item>
      <title>Call me Snake</title>
      <link>https://insinuator.net/2011/11/call-me-snake/</link>
      <pubDate>Wed, 16 Nov 2011 00:00:00 +0000</pubDate>
      <guid>https://insinuator.net/2011/11/call-me-snake/</guid>
      <description>&lt;p&gt;Once again there’s a &lt;a href=&#34;http://www.insinuator.net/2011/09/today-i-feel-like-stansfield/&#34;&gt;reference&lt;/a&gt; to some action movie here, as some of you may have immediately spotted ;-).&lt;/p&gt;&#xA;&lt;p&gt;For the record: this one is from “Snake Plissken”, the main protagonist in John Carpenter’s “Escape from New York”. There’s another well-known quote of the same character in the kind-of sequel “Escape from L.A.” which goes like: “The more things change, the more they stay the same”. I’m aware that this is not the initial source (but French novelist Jean-Baptiste Alphonse Karr presumably is, at the time in French ;-)); still this gives a nice  transition to today’s topic.&lt;/p&gt;</description>
    </item>
    <item>
      <title>“What’s so special about Troopers?”</title>
      <link>https://insinuator.net/2011/11/whats-so-special-about-troopers/</link>
      <pubDate>Fri, 11 Nov 2011 00:00:00 +0000</pubDate>
      <guid>https://insinuator.net/2011/11/whats-so-special-about-troopers/</guid>
      <description>&lt;p&gt;This week I stayed some days in Zurich, to give a workshop and to meet both clients and fellow researchers (kudos again to C. for the awesome office tour @Google). In the course of one of those dinners somehow Troopers was mentioned and a guy asked: “I’ve heard of the conference. What’s so special about it?”&lt;/p&gt;&#xA;&lt;p&gt;Funnily enough I didn’t even have to respond myself as a &lt;a href=&#34;http://www.troopers.de/archives/troopers11/agenda/&#34;&gt;2011&lt;/a&gt; attendee coincidentally present at the table jumped in and started praising the event (“best con ever. great spirit, great talks”). Obviously this gave me a big grin… but it reminded as well me that some of you might ask themselves the very same question.&lt;/p&gt;</description>
    </item>
    <item>
      <title>Short iCloud Follow-Up</title>
      <link>https://insinuator.net/2011/10/short-icloud-follow-up/</link>
      <pubDate>Mon, 31 Oct 2011 00:00:00 +0000</pubDate>
      <guid>https://insinuator.net/2011/10/short-icloud-follow-up/</guid>
      <description>&lt;p&gt;After the basic iCloud discussion in &lt;a href=&#34;http://www.insinuator.net/2011/10/itrust-or-not/&#34;&gt;this&lt;/a&gt; post, I would like to add some more technical information. The following items are just a loose compilation of facts about the mentioned controls which allow the restriction of iCloud usage. The basic iCloud usage, consisting of backup, document sync, and photo stream, can be deactivated using the most recent version of the &lt;a href=&#34;http://support.apple.com/kb/dl851&#34;&gt;iPhone Configuration Utility&lt;/a&gt;:&lt;/p&gt;&#xA;&lt;p&gt;&lt;a href=&#34;http://www.insinuator.net/wp-content/uploads/2011/10/icloud_config_icloud.png&#34;&gt;&lt;img src=&#34;http://www.insinuator.net/wp-content/uploads/2011/10/icloud_config_icloud.png&#34; alt=&#34;&#34; title=&#34;icloud_config_icloud&#34;&gt;&lt;/a&gt;&lt;/p&gt;&#xA;&lt;p&gt;Since there are no default settings for these values, it is necessary to include the disabled entries in existing configuration profiles.&lt;/p&gt;</description>
    </item>
    <item>
      <title>Today I feel like Stansfield</title>
      <link>https://insinuator.net/2011/09/today-i-feel-like-stansfield/</link>
      <pubDate>Tue, 20 Sep 2011 00:00:00 +0000</pubDate>
      <guid>https://insinuator.net/2011/09/today-i-feel-like-stansfield/</guid>
      <description>&lt;p&gt;… the corrupt DEA agent in Luc Besson’s great movie “Léon (The Professional)”. I’m sure quite some of you, dear readers, know the plot…&lt;br&gt;&#xA;Just before the final shootout, when sending the first men of the NYPD ESU team into Léon’s apartment, he tells them to “Be careful!”. After learning those men got killed he just comments: “I told you”.&lt;br&gt;&#xA;[btw: before yelling to bring “EEEEEEEVERYONE!!!!”, as those familiar with the piece will certainly remember ;-)].&lt;/p&gt;</description>
    </item>
    <item>
      <title>Appstore security: 5 lines of defence against malware</title>
      <link>https://insinuator.net/2011/09/appstore-security-5-lines-of-defence-against-malware/</link>
      <pubDate>Sat, 17 Sep 2011 00:00:00 +0000</pubDate>
      <guid>https://insinuator.net/2011/09/appstore-security-5-lines-of-defence-against-malware/</guid>
      <description>&lt;p&gt;A few days ago the European Network and Information Security Agency (ENISA) published &lt;a href=&#34;http://www.enisa.europa.eu/act/application-security/smartphone-security-1/appstore-security-5-lines-of-defence-against-malware/at_download/fullReport%20&#34;&gt;this quite interesting document&lt;/a&gt; with the exact title. Here’s what it covers:&lt;/p&gt;&#xA;&lt;p&gt;“The booming smartphone industry has a special way of delivering software to end-users: appstores. Popular appstores have hundreds of thousands of apps for anything from online banking to mosquito repellent, and the most popular stores (Apple Appstore, Google Android market) claim billions of app downloads. But appstores have not escaped the attention of cyber attackers. Over the course of 2011 numerous malicious apps were found, across a variety of smartphone models. Using malicious apps, attackers can easily tap into the vast amount of private data processed on smartphones such as confidential business emails, location data, phone calls, SMS messages and so on. Starting from a threat model for appstores, this paper identifies five lines of defence that must be in place to address malware in appstores: app review, reputation, kill-switches, device security and jails.”&lt;/p&gt;</description>
    </item>
    <item>
      <title>Ross Anderson on Responsible Disclosure and Academic Freedom</title>
      <link>https://insinuator.net/2011/01/ross-anderson-on-responsible-disclosure-and-academic-freedom/</link>
      <pubDate>Thu, 06 Jan 2011 00:00:00 +0000</pubDate>
      <guid>https://insinuator.net/2011/01/ross-anderson-on-responsible-disclosure-and-academic-freedom/</guid>
      <description>&lt;p&gt;Hi,&lt;/p&gt;&#xA;&lt;p&gt;just a short, somewhat non-technical,  post today: I really like &lt;a href=&#34;http://www.cl.cam.ac.uk/~rja14/Papers/ukca.pdf&#34;&gt;this response&lt;/a&gt; Ross Anderson gave to the “UK Cards Association” asking Cambridge University for taking offline a thesis of one of their students. It (the letter) pretty much summarizes how security research should be treated and backed by those interested in a more secure world we live in.&lt;/p&gt;&#xA;&lt;p&gt;On a personal note I’d like to add that Ross’ main volume “Security Engineering: A Guide to Building Dependable Distributed Systems”, initially published in 2001 and updated in the interim with a second edition in 2008, has been the most influential security book for me on my long way in the infosec space (which started back in 1997, with some workshops on firewalls I gave for IT auditors). If I could take only one infosec book to a lonely island, it would be this one.&lt;/p&gt;</description>
    </item>
    <item>
      <title>Cloud needn’t be daunting | Guide to legal aspects for non-legals</title>
      <link>https://insinuator.net/2010/12/cloud-neednt-be-daunting-guide-to-legal-aspects-for-non-legals/</link>
      <pubDate>Thu, 23 Dec 2010 00:00:00 +0000</pubDate>
      <guid>https://insinuator.net/2010/12/cloud-neednt-be-daunting-guide-to-legal-aspects-for-non-legals/</guid>
      <description>&lt;p&gt;The British Standards Institution recently published “Cloud Computing. A Practical Introduction to the Legal Issues”. I ordered an electronic copy yesterday (I did that &lt;a href=&#34;http://shop.bsigroup.com/en/ProductDetail/?pid=000000000030215581&#34;&gt;here&lt;/a&gt;, for GBP 30) and after a first glance can say there’s lots of valuable information in it.&lt;/p&gt;&#xA;&lt;p&gt;Merry christmas to everybody, have some peaceful and relaxing days&lt;/p&gt;&#xA;&lt;p&gt;Enno&lt;/p&gt;</description>
    </item>
    <item>
      <title>The OSSTMM 3 – What I like about it</title>
      <link>https://insinuator.net/2010/12/the-osstmm-3-what-i-like-about-it/</link>
      <pubDate>Mon, 13 Dec 2010 00:00:00 +0000</pubDate>
      <guid>https://insinuator.net/2010/12/the-osstmm-3-what-i-like-about-it/</guid>
      <description>&lt;p&gt;Given the upcoming public release of &lt;a href=&#34;http://www.isecom.org&#34;&gt;ISECOM&lt;/a&gt;‘s &lt;a href=&#34;http://www.isecom.org/osstmm/&#34;&gt;Open Source Security Testing Methodology Manual (OSSTMM)&lt;/a&gt; version 3, I took the opportunity to have a closer look at it. While we at ERNW never adopted the OSSTMM for our own way of performing security assessments (mostly due to the fact that performing assessments is our main business since 2001 and our approach has been developed and constantly honed since then so that we’re simply used to doing it “our way”) I’ve followed parts of ISECOM’s work quite closely as some of the brightest minds in the security space are contributing to it and they come up with innovative ideas regularly.&lt;br&gt;&#xA;So I was eager to get an early copy of it to spend some weekend time going through it (where I live we have about 40 cm of snow currently so there’s “plenty of occasions for a cosy reading session” ;-))&lt;br&gt;&#xA;One can read the OSSTMM (at least) two ways: as a manual for performing security testing or as a “whole philosophy of approaching [information] security”. I did the latter and will comment on it in a two-part post, covering the things I liked first and taking a more critical perspective on some portions in the second. Here we go with the first, in an unordered manner:&lt;/p&gt;</description>
    </item>
    <item>
      <title>Trust &amp; Control in the Age of Virtualization and the Cloud</title>
      <link>https://insinuator.net/2010/11/trust-control-in-the-age-of-virtualization-and-the-cloud/</link>
      <pubDate>Wed, 17 Nov 2010 00:00:00 +0000</pubDate>
      <guid>https://insinuator.net/2010/11/trust-control-in-the-age-of-virtualization-and-the-cloud/</guid>
      <description>&lt;p&gt;Two days ago I gave the keynote at an industry event, reflecting on the changing role of traditional security controls in the age of virtualization and the cloud. As this was an updated version of the stuff distributed in the conference proceedings, some people have asked for it. Voilà, &lt;a href=&#34;http://www.ernw.de/content/e7/e181/e1612/download1614/ERNW_LANline_VirtCloudSec_Keynote_ger.pdf&#34;&gt;here we go&lt;/a&gt;.&lt;/p&gt;&#xA;&lt;p&gt;have a good one,&lt;/p&gt;&#xA;&lt;p&gt;Enno&lt;/p&gt;</description>
    </item>
    <item>
      <title>ERNW to contribute to government sponsored research project on telco security</title>
      <link>https://insinuator.net/2010/10/ernw-to-contribute-to-government-sponsored-research-project-on-telco-security/</link>
      <pubDate>Wed, 20 Oct 2010 00:00:00 +0000</pubDate>
      <guid>https://insinuator.net/2010/10/ernw-to-contribute-to-government-sponsored-research-project-on-telco-security/</guid>
      <description>&lt;p&gt;Today we dare to (mis-) use the blog for a shameless self promotion 😉&lt;br&gt;&#xA;We’re happy to announce that ERNW will contribute to a government sponsored research project called &lt;a href=&#34;http://www.asmonia.de&#34;&gt;ASMONIA&lt;/a&gt; (which stands for the German title of the project that is &lt;em&gt;Angriffsanalyse und Schutzkonzepte für MObilfunkbasierte Netzinfrastrukturen unterstützt durch kooperativen InformationsAustausch&lt;/em&gt; [&lt;em&gt;Attack analysis and Security concepts for MObile Network infrastructures, supported by collaborative Information exchAnge&lt;/em&gt;]. those readers familiar with that kind of projects will have an idea of the importance of such acronyms ;-).&lt;/p&gt;</description>
    </item>
    <item>
      <title>Intel’s &lt;i&gt;Known Good&lt;/i&gt; Approach — Chances for a Paradigm Shift?</title>
      <link>https://insinuator.net/2010/09/intels-iknown-good/i-approach-chances-for-a-paradigm-shift/</link>
      <pubDate>Sat, 18 Sep 2010 00:00:00 +0000</pubDate>
      <guid>https://insinuator.net/2010/09/intels-iknown-good/i-approach-chances-for-a-paradigm-shift/</guid>
      <description>&lt;p&gt;During the keynote of the &lt;a href=&#34;http://download.intel.com/newsroom/kits/idf/2010_fall/pdfs/Day1_IDF_Keynote_Transcript_Otellini.pdf&#34;&gt;Intel Developer Forum&lt;/a&gt;, Intel’s CEO Paul Otellini explained their motivation for the acquisition of McAfee. Basically, Intel wants to provide a possibility to shift computer security from &lt;em&gt;a known bad model to something that is a known good model&lt;/em&gt;.&lt;/p&gt;&#xA;&lt;p&gt;Coming back to some of our &lt;a href=&#34;http://www.insinuator.net/2010/08/just-a-quick-note-on-the-library-loading-binary-planting-stuff/&#34;&gt;recent&lt;/a&gt; &lt;a href=&#34;http://www.insinuator.net/2010/09/that-new-worm/&#34;&gt;blog posts&lt;/a&gt;, we think that a reliable and working approach to implement application whitelisting would increase security in corporate environments — especially when thinking of the latest vulnerabilities with exploit code in the wild that could not be catched up by any AV solution. As covered by &lt;a href=&#34;http://feeds.arstechnica.com/~r/arstechnica/everything/~3/ZyQ42S4_7PU/intels-walled-garden-plan-to-put-av-vendors-out-of-business.ars&#34;&gt;this article&lt;/a&gt;, the possibility that such an approach succeeds depends heavily on the critical mass that would use it. The widespread &lt;a href=&#34;http://www.intel.com/Assets/PDF/manual/253666.pdf&#34;&gt;x86 architecture&lt;/a&gt; therefore is the perfect plattform for accomplishing a widely used known good model. Presuming the possibility for flexibel and secure operation, Intel’s efforts could be the chance to shift the paradigm of corporate security from a reactive to a preventive model.&lt;/p&gt;</description>
    </item>
    <item>
      <title>That “new worm”…</title>
      <link>https://insinuator.net/2010/09/that-new-worm/</link>
      <pubDate>Mon, 13 Sep 2010 00:00:00 +0000</pubDate>
      <guid>https://insinuator.net/2010/09/that-new-worm/</guid>
      <description>&lt;p&gt;Recently I noticed &lt;a href=&#34;http://www.h-online.com/security/news/item/New-email-worm-on-the-move-1076585.html&#34;&gt;this news&lt;/a&gt; titled “New email worm on the move”. At roughly the same time I received an email from a senior security responsible from a large customer asking for mitigation advice as they got “hit pretty hard” (by this exact piece of malware).&lt;br&gt;&#xA;Given I’m mainly an infrastructure and architecture guy usually I’m not too involved in malware protection stuff (besides my continuous ranting that – from an architectural point of view – endpoint based antivirus has a bad security benefit vs. capex/opex ratio). So I’m by no means an expert in this field. Still I keep scratching my head when I read the associated announcements (like &lt;a href=&#34;http://blog.trendmicro.com/old-malware-out-of-its-shell/&#34;&gt;this&lt;/a&gt;, &lt;a href=&#34;http://www.avertlabs.com/research/blog/index.php/2010/09/09/widespread-reporting-of-here-you-have-virus/&#34;&gt;this&lt;/a&gt; or &lt;a href=&#34;http://www.symantec.com/business/security_response/writeup.jsp?docid=2010-090922-4703-99&#34;&gt;this&lt;/a&gt;) from major “antivirus”, “malware protection” or “endpoint security” vendors – to save typing, in the remainder of the post I call them SNAKE vendors (where “SNAKE” stands for “Smart Nimble APT Kombat Execution”… or sth equally ingenious of the valued reader’s choice… 😉&lt;/p&gt;</description>
    </item>
    <item>
      <title>The Emperor’s New Security Indicators</title>
      <link>https://insinuator.net/2010/07/the-emperors-new-security-indicators/</link>
      <pubDate>Sun, 18 Jul 2010 00:00:00 +0000</pubDate>
      <guid>https://insinuator.net/2010/07/the-emperors-new-security-indicators/</guid>
      <description>&lt;p&gt;Interesting research from Stuart Schechter et.al. &lt;a href=&#34;http://usablesecurity.org/emperor/&#34;&gt;here&lt;/a&gt;.&lt;br&gt;&#xA;They evaluated the effect that the removal or modification of online banking sites’ security features had on the users’ behavior (as for entering or withholding their passwords). Maybe for some of you not too surprising it turned out that the vast majority of users entered their passwords even if obviously alarming clues were present on the websites.&lt;br&gt;&#xA;This, again, shows how important it is to understand how users behave, what their motives and incentives are and how to build environments that help them acting securely. This even more applies to corporate space. At times, bringing an industrial/organizational psychologist in might be a much better investment than writing yet-another-ignored-piece-of-policy.&lt;/p&gt;</description>
    </item>
    <item>
      <title>Welcome to insinuator.net</title>
      <link>https://insinuator.net/2009/10/welcome-to-insinuator.net/</link>
      <pubDate>Tue, 20 Oct 2009 00:00:00 +0000</pubDate>
      <guid>https://insinuator.net/2009/10/welcome-to-insinuator.net/</guid>
      <description>&lt;p&gt;Welcome to insinuator.net, the semi-official blog of &lt;a href=&#34;http://www.ernw.net&#34; title=&#34;ERNW Website&#34;&gt;ERNW GmbH&lt;/a&gt;.&lt;br&gt;&#xA;You may ask: Why yet another infosec blog? Aren’t there already just too many around? Well, possibly. But that opulence is part of blogging in general, isn’t it? 😉&lt;br&gt;&#xA;Given we are trying to contribute to “public space &amp;amp; opinion” in a number of ways anyway [e.g. by our &lt;a href=&#34;http://www.ernw.de/content/e7/e181/index_eng.html&#34; title=&#34;Event Archives&#34;&gt;presentations&lt;/a&gt; or our &lt;a href=&#34;http://www.ernw.net/nl&#34; title=&#34;ERNW Newsletter&#34;&gt;newsletter&lt;/a&gt;] it seemed just too logical – and we’ve been asked by various people as well – to add another element to global blogosphere. Voilà, here we go!&lt;br&gt;&#xA;What can you, dear reader, expect? Of course all kinds of shameless self-references, maybe occasionally a little bit of insight or even wisdom (yes, you’re right: modesty is not amongst our key virtues, at times) and – hopefully – some entertainment.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
