<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>(Web-)Insecurity Blog</title><link>https://security.lauritz-holtmann.de/</link><description>Recent content on (Web-)Insecurity Blog</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Tue, 23 Dec 2025 08:00:00 +0200</lastBuildDate><atom:link href="https://security.lauritz-holtmann.de/index.xml" rel="self" type="application/rss+xml"/><item><title>Turning List-Unsubscribe into an SSRF/XSS Gadget</title><link>https://security.lauritz-holtmann.de/post/xss-ssrf-list-unsubscribe/</link><pubDate>Tue, 23 Dec 2025 08:00:00 +0200</pubDate><guid>https://security.lauritz-holtmann.de/post/xss-ssrf-list-unsubscribe/</guid><description>&lt;p&gt;The &lt;code&gt;List-Unsubscribe&lt;/code&gt; SMTP header is standardized but often overlooked during security assessments. It allows email clients to provide an easy way for end-users to unsubscribe from mailing lists.&lt;/p&gt;
&lt;p&gt;This post discusses how this header can be abused to perform &lt;em&gt;Cross-Site Scripting (XSS)&lt;/em&gt; and &lt;em&gt;Server-Side Request Forgery (SSRF)&lt;/em&gt; attacks in certain scenarios.
Real-world examples involving &lt;em&gt;Horde Webmail&lt;/em&gt; (&lt;a href="https://www.cve.org/CVERecord?id=CVE-2025-68673"&gt;&lt;strong&gt;CVE-2025-68673&lt;/strong&gt;&lt;/a&gt;) and &lt;em&gt;Nextcloud Mail App&lt;/em&gt; are provided to illustrate the risks.&lt;/p&gt;</description></item><item><title>Trainings und Workshops</title><link>https://security.lauritz-holtmann.de/training/</link><pubDate>Wed, 10 Dec 2025 00:00:00 +0200</pubDate><guid>https://security.lauritz-holtmann.de/training/</guid><description>&lt;p&gt;Gerne unterstütze ich Sie als Freelancer bei der Erarbeitung und Durchführung maßgeschneiderter Workshops und Trainings:&lt;/p&gt;</description></item><item><title>Dead Domain Discovery: Discover Expired or Unregistered Domains</title><link>https://security.lauritz-holtmann.de/tools/dead-domain-discovery/</link><pubDate>Sat, 01 Nov 2025 10:00:00 +0200</pubDate><guid>https://security.lauritz-holtmann.de/tools/dead-domain-discovery/</guid><description>&lt;p&gt;Dead Domains are an often overlooked, yet impactful bug class that can lead to significant security vulnerabilities, including Cross-Site Scripting, Information Disclosure, and even Remote Code Execution. Attackers can exploit these vulnerabilities by registering expired or unregistered domains that were previously owned by legitimate entities.&lt;/p&gt;
&lt;p&gt;But: How can security researchers and penetration testers efficiently identify these dead domains?&lt;/p&gt;</description></item><item><title>Android App Links autoVerify=false Allowed Hijacking Authentication Flows</title><link>https://security.lauritz-holtmann.de/post/sso-android-autoverify/</link><pubDate>Wed, 18 Dec 2024 18:00:00 +0200</pubDate><guid>https://security.lauritz-holtmann.de/post/sso-android-autoverify/</guid><description>&lt;p&gt;&lt;em&gt;Research is a constant process of failure and iteration. However, in most cases, you only see the one-in-a-thousand (successful) attempt. To normalize f*ck ups, and because I believe the behavior we identified in the course of this research is still relevant and interesting, this post is published for educational purposes.&lt;/em&gt;&lt;/p&gt;
&lt;p&gt;Implementing secure &lt;em&gt;Single-Sign-On&lt;/em&gt; (SSO) flows on mobile platforms is a continuos challenge. This post discusses an Android feature which potentially enabled a malicious Android app to hijack &lt;em&gt;arbitrary&lt;/em&gt; SSO flows. As the feature existed on platform level (prior Android 12), it affected not only &lt;em&gt;misconfigured&lt;/em&gt; apps, but also (web-)applications that follow OAuth best current practice&lt;sup id="fnref:1"&gt;&lt;a href="#fn:1" class="footnote-ref" role="doc-noteref"&gt;1&lt;/a&gt;&lt;/sup&gt;.&lt;/p&gt;
&lt;p&gt;The vulnerability was reported to Google via the &lt;a href="https://bughunters.google.com/about/rules/android-friends/6171833274204160/android-and-google-devices-security-reward-program-rules"&gt;Android and Google Devices Security Reward Program
&lt;/a&gt; on November, 29th 2024. Shortly after submission, Google highlighted a crucial thing that was missed before: Due to major rework of the &lt;em&gt;App Link&lt;/em&gt; behavior, the reported issues do only work on Android versions prior to &lt;em&gt;Android 12&lt;/em&gt;.&lt;/p&gt;</description></item><item><title>Sign-in with World ID: XSS and ATO via OIDC Form Post Response Mode</title><link>https://security.lauritz-holtmann.de/advisories/tfh-form_post-xss-ato/</link><pubDate>Wed, 19 Jun 2024 00:00:00 +0200</pubDate><guid>https://security.lauritz-holtmann.de/advisories/tfh-form_post-xss-ato/</guid><description>&lt;p&gt;Recently, &lt;a href="https://www.toolsforhumanity.com/"&gt;Tools for Humanity&lt;/a&gt; partnered with the &lt;a href="https://h1.community/germany-hackerone-club/"&gt;German HackerOne Club&lt;/a&gt; to run a one-week virtual and in-person &lt;a href="https://h1.community/events/details/hackerone-germany-hackerone-club-presents-hackerone-hacking-meetup-tools-for-humanity-x-hackerone-club-germany/"&gt;&lt;em&gt;Hacking Meetup&lt;/em&gt;&lt;/a&gt;. In the course of the meetup, a critical vulnerability within the &lt;a href="https://docs.worldcoin.org/sign-in"&gt;Sign-in with World ID&lt;/a&gt; implementation was found, which affected the &lt;em&gt;OpenID Connect&lt;/em&gt; &lt;code&gt;form_post&lt;/code&gt; Response Mode and could allow malicious actors to take over end-user accounts at third-party applications that utilize the &lt;em&gt;Sign-in with World ID&lt;/em&gt; mechanism. The vulnerability &lt;a href="https://github.com/worldcoin/world-id-sign-in/commit/3c147bd3cfe4361d7b535f0bbad9f429672b2474"&gt;was addressed&lt;/a&gt; within a few hours after triage.&lt;/p&gt;</description></item><item><title>POST to XSS: Leveraging Pseudo Protocols to Gain JavaScript Evaluation in SSO Flows</title><link>https://security.lauritz-holtmann.de/post/sso-security-redirect-uri-iii/</link><pubDate>Fri, 10 May 2024 12:00:00 +0200</pubDate><guid>https://security.lauritz-holtmann.de/post/sso-security-redirect-uri-iii/</guid><description>&lt;p&gt;In 2020, a &lt;a href="https://security.lauritz-holtmann.de/post/sso-security-redirect-uri/"&gt;blog post&lt;/a&gt; was published here about the real-world security implications of a vague specification of the &lt;em&gt;Redirect URI&lt;/em&gt; within the &lt;em&gt;OAuth 2.0 RFC&lt;/em&gt;&lt;sup id="fnref:1"&gt;&lt;a href="#fn:1" class="footnote-ref" role="doc-noteref"&gt;1&lt;/a&gt;&lt;/sup&gt;. At that time, I focussed on &lt;em&gt;redirect-based flows&lt;/em&gt;. This post uncovers additional protocol-level issues that lead to security vulnerabilities in popular and well-audited SSO implementations such as &lt;em&gt;Authentik&lt;/em&gt; (CVE-2024-21637), &lt;em&gt;Keycloak&lt;/em&gt; (CVE-2023-6134), and &lt;em&gt;FusionAuth&lt;/em&gt;. Notably, the vulnerabilities were identified in the context of the &lt;em&gt;OAuth 2.0 Form Post Response Mode&lt;/em&gt;&lt;sup id="fnref:2"&gt;&lt;a href="#fn:2" class="footnote-ref" role="doc-noteref"&gt;2&lt;/a&gt;&lt;/sup&gt; &lt;strong&gt;and&lt;/strong&gt; the &lt;em&gt;SAML POST-Binding&lt;/em&gt;&lt;sup id="fnref:3"&gt;&lt;a href="#fn:3" class="footnote-ref" role="doc-noteref"&gt;3&lt;/a&gt;&lt;/sup&gt; and therefore are not limited to OAuth 2.0 and OpenID Connect, but also affect SAML-based SSO-Flows.&lt;/p&gt;
&lt;p&gt;In this post, we will dive into specification inaccuracies regarding the use of dangerous &lt;em&gt;pseudo-schemes&lt;/em&gt; (JavaScript-URIs) in combination with POST-based SSO flows such as the &lt;em&gt;OAuth 2.0 Form Post Response Mode&lt;/em&gt;&lt;sup id="fnref1:2"&gt;&lt;a href="#fn:2" class="footnote-ref" role="doc-noteref"&gt;2&lt;/a&gt;&lt;/sup&gt; and the &lt;em&gt;SAML POST-Bindings&lt;/em&gt;&lt;sup id="fnref1:3"&gt;&lt;a href="#fn:3" class="footnote-ref" role="doc-noteref"&gt;3&lt;/a&gt;&lt;/sup&gt;, resulting in a &lt;em&gt;protocol-level&lt;/em&gt; Cross-Site Scripting (XSS) vulnerability pattern.&lt;/p&gt;</description></item><item><title>SSO Gadgets II: Unauthenticated Client-Side Template Injection to Account Takeover using SSO Gadget Chain</title><link>https://security.lauritz-holtmann.de/post/csti-xss-sso-gadget-chain/</link><pubDate>Fri, 30 Jun 2023 00:00:00 +0200</pubDate><guid>https://security.lauritz-holtmann.de/post/csti-xss-sso-gadget-chain/</guid><description>&lt;p&gt;The following unauthenticated &lt;em&gt;Client-Side Template Injection&lt;/em&gt; (CSTI) resulting in a &lt;em&gt;Cross-Site Scripting&lt;/em&gt; (XSS) vulnerability was discovered in a private bug bounty program. While the vulnerability could only be exploited in case a user had no active session at the application, chained with an &lt;a href="https://security.lauritz-holtmann.de/post/xss-ato-gadgets/"&gt;&lt;em&gt;SSO gadget&lt;/em&gt;&lt;/a&gt;, a malicious actor could have still gained access to the user&amp;rsquo;s account and performed actions on behalf of the user.&lt;/p&gt;</description></item><item><title>SSO Gadgets: Escalate (Self-)XSS to ATO</title><link>https://security.lauritz-holtmann.de/post/xss-ato-gadgets/</link><pubDate>Sat, 04 Feb 2023 00:00:00 +0200</pubDate><guid>https://security.lauritz-holtmann.de/post/xss-ato-gadgets/</guid><description>&lt;p&gt;With the rise of &lt;em&gt;Single-Sign-On&lt;/em&gt; (SSO) and especially &lt;em&gt;OAuth 2.0&lt;/em&gt; and &lt;em&gt;OpenID Connect (OIDC)&lt;/em&gt;, the attack surface of web applications has increased significantly. In this post, I will show how to escalate a Cross-Site Scripting (XSS) vulnerability to an Account Takeover (ATO) by abusing OAuth2/OIDC gadgets and how to prevent such attacks.&lt;/p&gt;</description></item><item><title>Sie wurden von einem Hacker kontaktiert?</title><link>https://security.lauritz-holtmann.de/kontaktiert-von-einem-hacker/</link><pubDate>Tue, 10 Jan 2023 00:00:00 +0100</pubDate><guid>https://security.lauritz-holtmann.de/kontaktiert-von-einem-hacker/</guid><description>&lt;p&gt;Ein &amp;ldquo;Hacker&amp;rdquo; hat Sie kontaktiert um vermeintliche Sicherheitslücken zu melden? Das hat wahrscheinlich schon jeder, der eine Webseite betreibt, einmal erlebt. Doch was bedeutet das nun für Sie und Ihr Unternehmen? Welche Schritte sollten Sie kurz- und langfristig ergreifen?&lt;/p&gt;</description></item><item><title>Consulting und Pentests</title><link>https://security.lauritz-holtmann.de/pentest/</link><pubDate>Mon, 01 Aug 2022 00:00:00 +0200</pubDate><guid>https://security.lauritz-holtmann.de/pentest/</guid><description>&lt;p&gt;Gerne unterstütze ich Sie als Freelancer auf dem Weg zu sichereren Anwendungen und besserem Schutz Ihrer Kundendaten.&lt;/p&gt;</description></item><item><title>Personal Access Token Disclosure in Asana Desktop Application</title><link>https://security.lauritz-holtmann.de/advisories/asana-desktop-credential-disclosure/</link><pubDate>Sat, 18 Jun 2022 00:00:00 +0100</pubDate><guid>https://security.lauritz-holtmann.de/advisories/asana-desktop-credential-disclosure/</guid><description>&lt;p&gt;This post gives an insight into a sensitive data exposure vulnerability in &lt;a href="https://asana.com/download"&gt;&lt;em&gt;Asana for Mac&lt;/em&gt;&lt;/a&gt; that was rated as &lt;a href="https://bugcrowd.com/disclosures/caf10f76-f1fb-4dea-8434-9ed2c56a40bb/asana-desktop-application-includes-personal-access-token"&gt;&lt;em&gt;P1&lt;/em&gt;&lt;/a&gt; and was awarded a bounty.&lt;/p&gt;
&lt;p&gt;This was the very first report of that kind for me. Still, I think this type of deployment and build chain issue is more common than one may think.&lt;/p&gt;</description></item><item><title>About</title><link>https://security.lauritz-holtmann.de/about/</link><pubDate>Sat, 18 Dec 2021 00:00:00 +0200</pubDate><guid>https://security.lauritz-holtmann.de/about/</guid><description>&lt;p&gt;Hi there 👋



&lt;img src="https://security.lauritz-holtmann.de/images/portrait.png" alt="Portrait" width="200" height="200" style="float: right; width: 200px; border-radius: 50%;"&gt;

&lt;/p&gt;
&lt;p&gt;My name is Lauritz and I am an IT-Security researcher and penetration tester based in Germany.&lt;/p&gt;
&lt;p&gt;This is my personal website where I publish thoughts and advisories about my research.&lt;/p&gt;
&lt;p&gt;You can find me on various bug bounty platforms:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;&lt;a href="https://hackerone.com/lauritz?type=user"&gt;Hackerone&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="https://app.intigriti.com/profile/_lauritz_"&gt;Intigriti&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="https://bugcrowd.com/h/lauritz"&gt;Bugcrowd&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="https://yeswehack.com/hunters/lauritz"&gt;YesWeHack&lt;/a&gt;&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;Since 2024, I am also a &lt;a href="https://h1.community/u/mn666n/"&gt;Hackerone Brand Ambassador&lt;/a&gt; and I am happy to help you with any questions you might have about bug bounty hunting. Make sure to check out the &lt;a href="https://h1.community/germany-hackerone-club/"&gt;German Hackerone Club&lt;/a&gt; and feel free to contact me via the contact form on this website.&lt;/p&gt;</description></item><item><title>Flickr Account Takeover</title><link>https://security.lauritz-holtmann.de/advisories/flickr-account-takeover/</link><pubDate>Sat, 18 Dec 2021 00:00:00 +0200</pubDate><guid>https://security.lauritz-holtmann.de/advisories/flickr-account-takeover/</guid><description>&lt;p&gt;This post gives a deep dive into a critical security flaw that was present in &lt;a href="https://www.flickr.com/"&gt;Flickr&lt;/a&gt;&amp;rsquo;s login flow.&lt;/p&gt;
&lt;p&gt;The authentication at &lt;a href="https://identity.flickr.com/"&gt;identity.flickr.com&lt;/a&gt; is implemented using &lt;a href="https://aws.amazon.com/cognito/"&gt;AWS Cognito&lt;/a&gt;. By exploiting configuration issues and violations of the &lt;a href="https://openid.net/connect/"&gt;OpenID Connect&lt;/a&gt; specification, it was possible to takeover any Flickr account without user interaction.&lt;/p&gt;</description></item><item><title>AuRA: Auth. Request Analyser</title><link>https://security.lauritz-holtmann.de/tools/aura-auth-request-analyser/</link><pubDate>Wed, 24 Nov 2021 17:00:00 +0200</pubDate><guid>https://security.lauritz-holtmann.de/tools/aura-auth-request-analyser/</guid><description>&lt;p&gt;The &lt;em&gt;Auth. Request Analyser&lt;/em&gt; (AuRA) Chromium extension aims to support the analysis of &lt;em&gt;OAuth&lt;/em&gt; and &lt;em&gt;OpenID Connect&lt;/em&gt; implementations, by offering semi-automated analysis and attack capabilities for &lt;a href="https://datatracker.ietf.org/doc/html/rfc6749#section-4.1.1"&gt;Authorization/Authentication Requests&lt;/a&gt;.&lt;/p&gt;</description></item><item><title>Custom and flexible OAuth/OIDC SP and IdP implementations</title><link>https://security.lauritz-holtmann.de/tools/oidc-oauth-sp-idp/</link><pubDate>Wed, 24 Nov 2021 17:00:00 +0200</pubDate><guid>https://security.lauritz-holtmann.de/tools/oidc-oauth-sp-idp/</guid><description>&lt;p&gt;During my master&amp;rsquo;s thesis, I created custom &lt;em&gt;OpenID Connect&lt;/em&gt; Service Provider (SP) and Identity Provider (IdP) implementations for research and Proof-of-Concept purposes. Both implementations use &lt;em&gt;NodeJS&lt;/em&gt;. This post outlines their capabilities and how they can be extended.&lt;/p&gt;</description></item><item><title>Insufficient Redirect URI validation: The risk of allowing to dynamically add arbitrary query parameters and fragments to the redirect_uri</title><link>https://security.lauritz-holtmann.de/post/sso-security-redirect-uri-ii/</link><pubDate>Sat, 06 Nov 2021 17:00:00 +0200</pubDate><guid>https://security.lauritz-holtmann.de/post/sso-security-redirect-uri-ii/</guid><description>&lt;p&gt;In this post, I will discuss an OAuth 2.0 and OpenID Connect 1.0 implementation flaw pattern that was or is present even in well-known implementations from &lt;a href="https://developer.github.com/v3/oauth/"&gt;Github&lt;/a&gt;, &lt;a href="https://api.stackexchange.com/docs/authentication"&gt;Stackoverflow&lt;/a&gt; and &lt;a href="https://docs.microsoft.com/en-us/azure/active-directory/develop/active-directory-v2-protocols"&gt;Microsoft&lt;/a&gt;.&lt;/p&gt;</description></item><item><title>XSS in Large Messenger and Payment App - a Shout Out to Parameter Guessing</title><link>https://security.lauritz-holtmann.de/post/xss-parameter-guessing/</link><pubDate>Fri, 02 Apr 2021 18:00:00 +0200</pubDate><guid>https://security.lauritz-holtmann.de/post/xss-parameter-guessing/</guid><description>&lt;p&gt;This is a post about a &lt;em&gt;Cross-Site-Scripting&lt;/em&gt; (XSS) vulnerability that was identified within the web version of a large Chinese messenger and payment platform. The vulnerability could have been missed easily, as the vulnerable parameter was manually guessed.&lt;/p&gt;</description></item><item><title>TikTok Careers Portal Account Takeover</title><link>https://security.lauritz-holtmann.de/advisories/tiktok-account-takeover/</link><pubDate>Tue, 15 Dec 2020 00:00:00 +0200</pubDate><guid>https://security.lauritz-holtmann.de/advisories/tiktok-account-takeover/</guid><description>&lt;p&gt;The following (slightly modified) vulnerability report was sent to TikTok using Hackerone on 17th October 2020 and was resolved within 12 days.&lt;/p&gt;</description></item><item><title>Real-life OIDC Security (VII): Responsible Disclosure</title><link>https://security.lauritz-holtmann.de/post/sso-security-responsible-disclosure/</link><pubDate>Thu, 19 Nov 2020 13:00:00 +0200</pubDate><guid>https://security.lauritz-holtmann.de/post/sso-security-responsible-disclosure/</guid><description>&lt;p&gt;This is the &lt;em&gt;final&lt;/em&gt; post of a series on Single Sign-On and OpenID Connect 1.0 security. In this post, Responsible Disclosure processes with five vendors and maintainers of popular OpenID Connect implementations are outlined. We reported vulnerabilities and security issues in &lt;a href="https://aws.amazon.com/cognito/"&gt;Amazon Cognito&lt;/a&gt;, &lt;a href="https://www.atlassian.com/software/bitbucket"&gt;Bitbucket Server&lt;/a&gt;, &lt;a href="https://about.gitlab.com/install/"&gt;GitLab&lt;/a&gt;, &lt;a href="https://www.keycloak.org/"&gt;Keycloak&lt;/a&gt;, and &lt;a href="salesforce.com"&gt;Salesforce&lt;/a&gt;.&lt;/p&gt;</description></item><item><title>Real-life OIDC Security (VI): Reusable state leads to DoS Amplification</title><link>https://security.lauritz-holtmann.de/post/sso-security-state/</link><pubDate>Tue, 17 Nov 2020 18:00:00 +0200</pubDate><guid>https://security.lauritz-holtmann.de/post/sso-security-state/</guid><description>&lt;p&gt;This is the &lt;em&gt;sixth&lt;/em&gt; post of a series on Single Sign-On and OpenID Connect 1.0 security. This post outlines how the missing requirement of the &lt;code&gt;state&lt;/code&gt; value within the OpenID Connect Core specification leads to real-life security issues. Namely, the &lt;em&gt;Denial-of-Service Amplification&lt;/em&gt; attack is introduced with &lt;em&gt;CVE-2020-14302&lt;/em&gt; (&lt;a href="https://www.keycloak.org/"&gt;Keycloak&lt;/a&gt;) as an example.&lt;/p&gt;</description></item><item><title>Real-life OIDC Security (V): Redirect URI</title><link>https://security.lauritz-holtmann.de/post/sso-security-redirect-uri/</link><pubDate>Thu, 12 Nov 2020 17:00:00 +0200</pubDate><guid>https://security.lauritz-holtmann.de/post/sso-security-redirect-uri/</guid><description>&lt;p&gt;This is the &lt;em&gt;fifth&lt;/em&gt; post of a series on Single Sign-On and OpenID Connect 1.0 security. This post outlines how the vague specification of the Redirect URI within the OpenID Connect Core specification leads to real-life security issues. Finally, we show a real-world example of such an issue with &lt;em&gt;CVE-2020-10776&lt;/em&gt; (&lt;a href="https://www.keycloak.org/"&gt;Keycloak&lt;/a&gt;) as an example.&lt;/p&gt;</description></item><item><title>Real-life OIDC Security (IV): Server-Side-Request-Forgery</title><link>https://security.lauritz-holtmann.de/post/sso-security-ssrf/</link><pubDate>Tue, 10 Nov 2020 20:00:00 +0200</pubDate><guid>https://security.lauritz-holtmann.de/post/sso-security-ssrf/</guid><description>&lt;p&gt;This is the &lt;em&gt;fourth&lt;/em&gt; post of a series on Single Sign-On and OpenID Connect 1.0 security. In this post, SSRF vulnerabilities that were discovered in popular OIDC implementations (&lt;a href="https://www.keycloak.org/"&gt;Keycloak&lt;/a&gt; (&lt;em&gt;CVE-2020-10770&lt;/em&gt;) and &lt;a href="https://aws.amazon.com/cognito/"&gt;Amazon Cognito&lt;/a&gt;) are explained in detail.&lt;/p&gt;</description></item><item><title>Real-life OIDC Security (III): CRLF Injections</title><link>https://security.lauritz-holtmann.de/post/sso-security-crlf-injection/</link><pubDate>Thu, 05 Nov 2020 17:00:00 +0200</pubDate><guid>https://security.lauritz-holtmann.de/post/sso-security-crlf-injection/</guid><description>&lt;p&gt;This is the &lt;em&gt;third&lt;/em&gt; post of a series on Single Sign-On and OpenID Connect 1.0 security. In this post, a more common CRLF injection in the context of OIDC is discussed in detail. We present issues discovered in &lt;a href="https://about.gitlab.com/install/"&gt;GitLab&lt;/a&gt; (Severity: High - Critical) and &lt;a href="https://www.atlassian.com/software/bitbucket"&gt;Bitbucket Server&lt;/a&gt; (Severity: Informative - Low).&lt;/p&gt;</description></item><item><title>Real-life OIDC Security (II): Login Confusion</title><link>https://security.lauritz-holtmann.de/post/sso-security-login-confusion/</link><pubDate>Mon, 02 Nov 2020 17:00:00 +0200</pubDate><guid>https://security.lauritz-holtmann.de/post/sso-security-login-confusion/</guid><description>&lt;p&gt;This is the &lt;em&gt;second&lt;/em&gt; post of a series on Single Sign-On and OpenID Connect 1.0 security. In this post, the novel &lt;em&gt;Login Confusion&lt;/em&gt; attack is described in detail. We use &lt;a href="https://www.atlassian.com/software/bitbucket"&gt;Bitbucket Server&lt;/a&gt; as an example.&lt;/p&gt;</description></item><item><title>CVE-2020-13294</title><link>https://security.lauritz-holtmann.de/advisories/cve-2020-13294/</link><pubDate>Sun, 01 Nov 2020 11:00:00 +0200</pubDate><guid>https://security.lauritz-holtmann.de/advisories/cve-2020-13294/</guid><description>&lt;p&gt;The following (slightly modified) advisory was sent to GitLab using Hackerone on 19th June 2020.&lt;/p&gt;</description></item><item><title>Real-life OIDC Security (I): Overview</title><link>https://security.lauritz-holtmann.de/post/sso-security-overview/</link><pubDate>Fri, 30 Oct 2020 18:21:19 +0200</pubDate><guid>https://security.lauritz-holtmann.de/post/sso-security-overview/</guid><description>&lt;p&gt;This is the &lt;em&gt;first&lt;/em&gt; post of a series on Single Sign-On and OpenID Connect 1.0 security. This post presents a high-level overview of observed issue patterns during my research on real-life OIDC security and proposes additions to the specification&amp;rsquo;s security considerations.&lt;/p&gt;</description></item><item><title>macOS Catalina: PostScript evaluation to Remote Denial-of-Service</title><link>https://security.lauritz-holtmann.de/advisories/apple-postscript/</link><pubDate>Sun, 11 Oct 2020 11:00:00 +0200</pubDate><guid>https://security.lauritz-holtmann.de/advisories/apple-postscript/</guid><description>&lt;p&gt;The following (slightly modified) advisory regarding macOS 10.15.6. (Catalina) was sent to &lt;a href="mailto:product-security@apple.com"&gt;Apple Product Security&lt;/a&gt; on 25th August 2020.&lt;/p&gt;</description></item><item><title>Hello World</title><link>https://security.lauritz-holtmann.de/post/hello-world/</link><pubDate>Thu, 08 Oct 2020 22:55:45 +0200</pubDate><guid>https://security.lauritz-holtmann.de/post/hello-world/</guid><description>&lt;p&gt;This is the very first actual &amp;ldquo;blog post&amp;rdquo; on this site. As the main structure might indicate, future content will be categorized either as dedicated advisory on an observed vulnerability or as blog post on more high-level observations.&lt;/p&gt;</description></item><item><title>Privacy Policy</title><link>https://security.lauritz-holtmann.de/privacy/</link><pubDate>Wed, 25 Sep 2019 13:51:22 +0200</pubDate><guid>https://security.lauritz-holtmann.de/privacy/</guid><description>&lt;p&gt;When I set up this blog, privacy and security were key reasons for choosing a static site generator, namely the awesome Hugo framework: &lt;a href="https://gohugo.io/"&gt;https://gohugo.io/&lt;/a&gt;.&lt;/p&gt;
&lt;p&gt;Thus, &lt;a href="https://security.lauritz-holtmann.de"&gt;https://security.lauritz-holtmann.de&lt;/a&gt; does not set cookies nor aims to track you on application level.&lt;/p&gt;
&lt;h2 id="hosting--logging-hetzner"&gt;Hosting &amp;amp; Logging (Hetzner)&lt;/h2&gt;
&lt;p&gt;This website is hosted by &lt;a href="https://www.hetzner.com/"&gt;Hetzner Online GmbH&lt;/a&gt;.&lt;br&gt;
The web server configuration avoids creating unnecessary logs — no access or error logs are intentionally stored by me.&lt;/p&gt;
&lt;p&gt;However, Hetzner automatically processes certain anonymized technical data for operational and security reasons. This may include:&lt;/p&gt;</description></item><item><title>CVE-2019-11832</title><link>https://security.lauritz-holtmann.de/advisories/cve-2019-11832/</link><pubDate>Thu, 09 May 2019 13:51:22 +0200</pubDate><guid>https://security.lauritz-holtmann.de/advisories/cve-2019-11832/</guid><description>&lt;p&gt;The following (slightly modified) advisory was sent to the TYPO3 security team (&lt;a href="mailto:security@typo3.org"&gt;security@typo3.org&lt;/a&gt;) on 28th January 2019.&lt;/p&gt;</description></item><item><title>Impressum</title><link>https://security.lauritz-holtmann.de/impressum/</link><pubDate>Thu, 09 May 2019 13:51:22 +0200</pubDate><guid>https://security.lauritz-holtmann.de/impressum/</guid><description>&lt;div class='impressum'&gt;
&lt;h4&gt;Angaben gemäß § 5 TMG&lt;/h4&gt;
&lt;p&gt;Lauritz Holtmann &lt;br&gt; 
Südring 25&lt;br&gt; 
44787 Bochum&lt;br&gt; 

&lt;h4&gt;Umsatzsteuer-Identifikationsnummer&lt;/h4&gt;
&lt;p&gt;USt-IdNr: DE453537805&lt;br&gt;&lt;/p&gt;
&lt;hr&gt;
&lt;/p&gt;
&lt;h4&gt;Vertreten durch: &lt;/h4&gt;
Lauritz Holtmann&lt;br&gt;
&lt;/p&gt;
&lt;h4&gt;Kontakt:&lt;/h4&gt;
E-Mail: &lt;a href='mailto:security@lauritz-holtmann.de'&gt;security@lauritz-holtmann.de&lt;/a&gt;&lt;/br&gt;&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;Haftungsausschluss: &lt;/strong&gt;&lt;br&gt;&lt;br&gt;&lt;strong&gt;Haftung für Inhalte&lt;/strong&gt;&lt;br&gt;&lt;br&gt;
Die Inhalte unserer Seiten wurden mit größter Sorgfalt erstellt. Für die Richtigkeit, Vollständigkeit und Aktualität der Inhalte können wir jedoch keine Gewähr übernehmen. Als Diensteanbieter sind wir gemäß § 7 Abs.1 TMG für eigene Inhalte auf diesen Seiten nach den allgemeinen Gesetzen verantwortlich. Nach §§ 8 bis 10 TMG sind wir als Diensteanbieter jedoch nicht verpflichtet, übermittelte oder gespeicherte fremde Informationen zu überwachen oder nach Umständen zu forschen, die auf eine rechtswidrige Tätigkeit hinweisen. Verpflichtungen zur Entfernung oder Sperrung der Nutzung von Informationen nach den allgemeinen Gesetzen bleiben hiervon unberührt. Eine diesbezügliche Haftung ist jedoch erst ab dem Zeitpunkt der Kenntnis einer konkreten Rechtsverletzung möglich. Bei Bekanntwerden von entsprechenden Rechtsverletzungen werden wir diese Inhalte umgehend entfernen.&lt;br&gt;&lt;br&gt;&lt;strong&gt;Haftung für Links&lt;/strong&gt;&lt;br&gt;&lt;br&gt;
Unser Angebot enthält Links zu externen Webseiten Dritter, auf deren Inhalte wir keinen Einfluss haben. Deshalb können wir für diese fremden Inhalte auch keine Gewähr übernehmen. Für die Inhalte der verlinkten Seiten ist stets der jeweilige Anbieter oder Betreiber der Seiten verantwortlich. Die verlinkten Seiten wurden zum Zeitpunkt der Verlinkung auf mögliche Rechtsverstöße überprüft. Rechtswidrige Inhalte waren zum Zeitpunkt der Verlinkung nicht erkennbar. Eine permanente inhaltliche Kontrolle der verlinkten Seiten ist jedoch ohne konkrete Anhaltspunkte einer Rechtsverletzung nicht zumutbar. Bei Bekanntwerden von Rechtsverletzungen werden wir derartige Links umgehend entfernen.&lt;br&gt;&lt;br&gt;&lt;strong&gt;Urheberrecht&lt;/strong&gt;&lt;br&gt;&lt;br&gt;
Die durch die Seitenbetreiber erstellten Inhalte und Werke auf diesen Seiten unterliegen dem deutschen Urheberrecht. Die Vervielfältigung, Bearbeitung, Verbreitung und jede Art der Verwertung außerhalb der Grenzen des Urheberrechtes bedürfen der schriftlichen Zustimmung des jeweiligen Autors bzw. Erstellers. Downloads und Kopien dieser Seite sind nur für den privaten, nicht kommerziellen Gebrauch gestattet. Soweit die Inhalte auf dieser Seite nicht vom Betreiber erstellt wurden, werden die Urheberrechte Dritter beachtet. Insbesondere werden Inhalte Dritter als solche gekennzeichnet. Sollten Sie trotzdem auf eine Urheberrechtsverletzung aufmerksam werden, bitten wir um einen entsprechenden Hinweis. Bei Bekanntwerden von Rechtsverletzungen werden wir derartige Inhalte umgehend entfernen.&lt;/p&gt;</description></item></channel></rss>