<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Malte Heinzelmann on Insinuator.net - Bold Statements</title>
    <link>https://insinuator.net/authors/malte-heinzelmann/</link>
    <description>Recent content in Malte Heinzelmann on Insinuator.net - Bold Statements</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Tue, 17 Feb 2026 00:00:00 +0000</lastBuildDate>
    <atom:link href="https://insinuator.net/authors/malte-heinzelmann/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Vulnerability Disclosure: JWT Authentication Bypass in OpenID Connect Authenticator for Tomcat</title>
      <link>https://insinuator.net/2026/02/vulnerability-disclosure-jwt-authentication-bypass-in-openid-connect-authenticator-for-tomcat/</link>
      <pubDate>Tue, 17 Feb 2026 00:00:00 +0000</pubDate>
      <guid>https://insinuator.net/2026/02/vulnerability-disclosure-jwt-authentication-bypass-in-openid-connect-authenticator-for-tomcat/</guid>
      <description>&lt;p&gt;During a customer project we identified an issue with the validation of JWT&#xA;tokens that allowed us to bypass the authentication by using unsigned tokens&#xA;with arbitrary payloads. During analysis we found out that this is caused by a&#xA;vulnerability within the library&#xA;&lt;a href=&#34;https://github.com/boylesoftware/tomcat-oidcauth&#34;&gt;OpenID Connect Authenticator for Tomcat&lt;/a&gt;.&lt;/p&gt;&#xA;&lt;p&gt;&lt;a href=&#34;https://github.com/boylesoftware/tomcat-oidcauth&#34;&gt;OpenID Connect Authenticator for Tomcat&lt;/a&gt;&#xA;between versions 2.0.0 and 2.5.0, as well as the current state on branch&#xA;&lt;code&gt;master&lt;/code&gt; contain a security flaw (introduced with commit &lt;code&gt;64e9a99&lt;/code&gt;) that allows&#xA;attackers to bypass JWT signature validation easily.&lt;/p&gt;</description>
    </item>
    <item>
      <title>Vulnerability Disclosure: Stealing Emails via Prompt Injections</title>
      <link>https://insinuator.net/2025/09/vulnerability-disclosure-stealing-emails-via-prompt-injections/</link>
      <pubDate>Tue, 02 Sep 2025 00:00:00 +0000</pubDate>
      <guid>https://insinuator.net/2025/09/vulnerability-disclosure-stealing-emails-via-prompt-injections/</guid>
      <description>&lt;p&gt;With the rise of AI assistance features in an increasing number of products, we&#xA;have begun to focus some of our research efforts on refining our internal&#xA;detection and testing guidelines for LLMs by taking a brief look at the new AI&#xA;integrations we discover.&lt;/p&gt;&#xA;&lt;p&gt;Alongside the rise of applications with LLM integrations, an increasing number&#xA;of customers come to ERNW to specifically assess AI applications. Our colleagues&#xA;&lt;a href=&#34;https://www.linkedin.com/in/fgrunow&#34;&gt;Florian Grunow&lt;/a&gt; and&#xA;&lt;a href=&#34;https://www.linkedin.com/in/hannesmohr/&#34;&gt;Hannes Mohr&lt;/a&gt; analyzed the novel attack&#xA;vectors that emerged and presented the results at&#xA;&lt;a href=&#34;https://troopers.de/troopers24/talks/vnwhm8/&#34;&gt;TROOPERS24&lt;/a&gt; already.&lt;/p&gt;</description>
    </item>
    <item>
      <title>Vulnerability Disclosure: Restricted Shell Breakout (CVE-2025-1950) and Privilege Escalation (CVE-2025-1951) in IBM Power Hardware Management Console (HMC)</title>
      <link>https://insinuator.net/2025/04/vulnerability-disclosure-restricted-shell-breakout-cve-2025-1950-and-privilege-escalation-cve-2025-1951-in-ibm-power-hardware-management-console-hmc/</link>
      <pubDate>Fri, 25 Apr 2025 00:00:00 +0000</pubDate>
      <guid>https://insinuator.net/2025/04/vulnerability-disclosure-restricted-shell-breakout-cve-2025-1950-and-privilege-escalation-cve-2025-1951-in-ibm-power-hardware-management-console-hmc/</guid>
      <description>&lt;p&gt;We discovered a private key for accessing an IBM Hardware Management Console&#xA;(HMC) during a recent red team engagement. The IBM Hardware Management Console&#xA;(HMC) is a dedicated management system used to control and manage IBM servers,&#xA;especially those running on Power Systems (like IBM Power9/Power10) and&#xA;mainframes (z Systems). After brief research, we identified two security&#xA;vulnerabilities that can be leveraged to gain root access to the HMC.&lt;/p&gt;&#xA;&lt;p&gt;Access for most users via SSH is limited through the &lt;code&gt;hmcbash&lt;/code&gt;, a restricted&#xA;shell environment. Using &lt;code&gt;LD_PRELOAD&lt;/code&gt;, attackers can break out of the restricted&#xA;bash and gain access to additional binaries installed on the system. With the&#xA;restrictions lifted, attackers can use a &lt;code&gt;setuid&lt;/code&gt; binary, &lt;code&gt;copysshkey&lt;/code&gt;, to&#xA;elevate privileges to &lt;code&gt;root&lt;/code&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>DNS exfiltration case study</title>
      <link>https://insinuator.net/2020/03/dns-exfiltration-case-study/</link>
      <pubDate>Wed, 04 Mar 2020 00:00:00 +0000</pubDate>
      <guid>https://insinuator.net/2020/03/dns-exfiltration-case-study/</guid>
      <description>&lt;p&gt;Lately, we came across a remote code execution in a Tomcat web service by utilizing &lt;a href=&#34;https://docs.oracle.com/javaee/6/tutorial/doc/gjddd.html&#34;&gt;Expression Language&lt;/a&gt;. The vulnerable POST body field expected a number. When sending &lt;code&gt;${1+2}&lt;/code&gt; instead, the web site included a Java error message about a failed conversion to &lt;code&gt;java.lang.Long&lt;/code&gt; from &lt;code&gt;java.lang.String&lt;/code&gt; with value &lt;code&gt;&amp;quot;3&amp;quot;&lt;/code&gt;.&lt;/p&gt;&#xA;&lt;p&gt;From that error message we learned a couple of things:&lt;/p&gt;&#xA;&lt;ul&gt;&#xA;&lt;li&gt;The application uses Java&lt;/li&gt;&#xA;&lt;li&gt;We are able to execute EL expressions&lt;/li&gt;&#xA;&lt;li&gt;Output from the EL engine is always returned as &lt;code&gt;String&lt;/code&gt;&lt;/li&gt;&#xA;&lt;/ul&gt;&#xA;&lt;p&gt;Whenever you are able to execute code within a Java Context, the most interesting part is to check whether we can get a &lt;code&gt;Runtime&lt;/code&gt; object and execute arbitrary OS commands.&lt;/p&gt;</description>
    </item>
    <item>
      <title>Troopers 19 – Badge Hardware</title>
      <link>https://insinuator.net/2019/07/troopers-19-badge-hardware/</link>
      <pubDate>Thu, 18 Jul 2019 00:00:00 +0000</pubDate>
      <guid>https://insinuator.net/2019/07/troopers-19-badge-hardware/</guid>
      <description>&lt;p&gt;This post by Jeff (@jeffmakes) was delayed due to interferences with other projects but nevertheless, enjoy!&lt;/p&gt;&#xA;&lt;p&gt;This year, it was my great honour to design the hardware for the Troopers19 badge.&lt;/p&gt;&#xA;&lt;p&gt;We wanted to make a wifi-connected MicroPython-powered badge; something that would be fun to take home and hack on. It was a nice opportunity to use a microcontroller platform that I hadn’t tried before. I also used the project as a chance to finally migrate my PCB workflow from Eagle to Kicad. Inevitably it was a painful transition, which resulted in quite some delay to the project as I floundered around in the new tool, but it does mean the design files are in an open format which I hope will benefit the community of Troopers attendees and future badge designers!&lt;/p&gt;</description>
    </item>
    <item>
      <title>Troopers 19 – Hack your badge</title>
      <link>https://insinuator.net/2019/04/troopers-19-hack-your-badge/</link>
      <pubDate>Mon, 15 Apr 2019 00:00:00 +0000</pubDate>
      <guid>https://insinuator.net/2019/04/troopers-19-hack-your-badge/</guid>
      <description>&lt;p&gt;Sadly, TROOPERS 19 is already over. I had great fun meeting all of you, helping you with your badge problems and seeing others hacking on their badges for example to get custom images on there.&lt;/p&gt;&#xA;&lt;p&gt;With this year’s badge we wanted to give you something you can reuse after the conference, learn new things new build something on your own.&lt;/p&gt;&#xA;&lt;p&gt;As promised in our &lt;a href=&#34;https://www.youtube.com/watch?v=5ZJDIMuPRtY&#34;&gt;talk&lt;/a&gt; Jeff and I would like to give you a short introduction into the badge internals. Along with this post we will release the source code for the badge firmware, the provisioning server and the schematics for the PCB.&lt;/p&gt;</description>
    </item>
    <item>
      <title>A few notes on WordPress Security</title>
      <link>https://insinuator.net/2018/08/a-few-notes-on-wordpress-security/</link>
      <pubDate>Wed, 22 Aug 2018 00:00:00 +0000</pubDate>
      <guid>https://insinuator.net/2018/08/a-few-notes-on-wordpress-security/</guid>
      <description>&lt;p&gt;Taking a look at the &lt;a href=&#34;https://cve.mitre.org/cgi-bin/cvekey.cgi?keyword=wordpress&#34;&gt;CVE List for WordPress&lt;/a&gt;, most vulnerabilities aren’t found within the WordPress core but inside of third-party plugins and themes.&lt;/p&gt;&#xA;&lt;p&gt;Today, let’s talk about WordPress.&lt;/p&gt;&#xA;&lt;p&gt;Performing a WordPress assessment might seem boring at first as core functionality [tested] and configuration does not allow for extensive security misconfigurations. Luckily, most instances use plugins and themes to add features not offered by the WordPress core.&lt;/p&gt;&#xA;&lt;p&gt;In this blog post I would like to discuss the findings and how I discovered them. Also, I will describe different vendor responsiveness reaching from not responding at all, to not understanding the issue to fast and professional responses kindly asking for a review of the updated code ready for deployment.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
