<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>Research &#8211; SCRT Team Blog</title>
	<atom:link href="/category/research/feed/" rel="self" type="application/rss+xml" />
	<link>/</link>
	<description>Orange Cyberdefense Switzerland&#039;s technical blog</description>
	<lastBuildDate>Tue, 22 Sep 2026 07:34:59 +0000</lastBuildDate>
	<language>en-US</language>
	<sy:updatePeriod>
	hourly	</sy:updatePeriod>
	<sy:updateFrequency>
	1	</sy:updateFrequency>
	<generator>https://wordpress.org/?v=6.9.8</generator>

<image>
	<url>/wp-content/uploads/2024/10/cropped-favicon-32x32-1-32x32.png</url>
	<title>Research &#8211; SCRT Team Blog</title>
	<link>/</link>
	<width>32</width>
	<height>32</height>
</image> 
	<item>
		<title>How One Twitch Chat Message Became Code Execution on a Streamer’s PC</title>
		<link>/2026/09/22/how-one-twitch-chat-message-became-code-execution-on-a-streamers-pc/</link>
		
		<dc:creator><![CDATA[Dylan Iffrig-Bourfa]]></dc:creator>
		<pubDate>Tue, 22 Sep 2026 07:06:37 +0000</pubDate>
				<category><![CDATA[Exploit]]></category>
		<category><![CDATA[Research]]></category>
		<category><![CDATA[Vulnerability]]></category>
		<guid isPermaLink="false">/?p=7426</guid>

					<description><![CDATA[A vulnerable chat overlay, an unsandboxed Chromium renderer, and a V8 bug already exploited in the wild were enough to turn viewer-controlled text into native code execution, with OBS itself left at its default settings. I found a Twitch chat overlay that rendered viewer messages as raw HTML inside an OBS Browser Source. That gives &#8230; <a href="/2026/09/22/how-one-twitch-chat-message-became-code-execution-on-a-streamers-pc/" class="more-link">Continue reading <span class="screen-reader-text">How One Twitch Chat Message Became Code Execution on a Streamer’s PC</span></a>]]></description>
		
		
		<enclosure url="/wp-content/uploads/2026/08/output2.mp4" length="864002" type="video/mp4" />

			</item>
		<item>
		<title>HP One Agent: local privilege escalation through race condition [CVE-2026-5064]</title>
		<link>/2026/09/08/hp-one-agent-local-privilege-escalation-through-race-condition-cve-2026-5064/</link>
		
		<dc:creator><![CDATA[Alain Mowat]]></dc:creator>
		<pubDate>Tue, 08 Sep 2026 07:05:53 +0000</pubDate>
				<category><![CDATA[Exploit]]></category>
		<category><![CDATA[Pentest]]></category>
		<category><![CDATA[Research]]></category>
		<category><![CDATA[Vulnerability]]></category>
		<guid isPermaLink="false">/?p=7408</guid>

					<description><![CDATA[One type of assessment we perform a lot, especially last year with Windows 10 coming to the end of its life, is what we call a workstation assessment. The goal is to identify weaknesses and vulnerabilities within a standard image or build and determine whether they can be exploited from various standpoints. During such an &#8230; <a href="/2026/09/08/hp-one-agent-local-privilege-escalation-through-race-condition-cve-2026-5064/" class="more-link">Continue reading <span class="screen-reader-text">HP One Agent: local privilege escalation through race condition [CVE-2026-5064]</span></a>]]></description>
		
		
		
			</item>
		<item>
		<title>From a Regular Red Team Exercise to Developing a Custom C2 Channel over MS Teams</title>
		<link>/2026/04/21/from-a-regular-red-team-exercise-to-developing-a-custom-c2-channel-over-ms-teams/</link>
		
		<dc:creator><![CDATA[Clément Labro]]></dc:creator>
		<pubDate>Tue, 21 Apr 2026 12:47:26 +0000</pubDate>
				<category><![CDATA[Pentest]]></category>
		<category><![CDATA[Research]]></category>
		<guid isPermaLink="false">/?p=7207</guid>

					<description><![CDATA[It&#8217;s early June 2025, we are preparing our C2 infrastructure and payload for an upcoming red team engagement. We know the client, we also know some aspects of their infrastructure because we do a lot of regular pentests for them throughout the year. We don&#8217;t need to worry about the social engineering part because it &#8230; <a href="/2026/04/21/from-a-regular-red-team-exercise-to-developing-a-custom-c2-channel-over-ms-teams/" class="more-link">Continue reading <span class="screen-reader-text">From a Regular Red Team Exercise to Developing a Custom C2 Channel over MS Teams</span></a>]]></description>
		
		
		
			</item>
		<item>
		<title>Blinding EDRs: A deep dive into WFP manipulation</title>
		<link>/2025/08/25/blinding-edrs-a-deep-dive-into-wfp-manipulation/</link>
		
		<dc:creator><![CDATA[Florian Audon]]></dc:creator>
		<pubDate>Mon, 25 Aug 2025 08:22:56 +0000</pubDate>
				<category><![CDATA[Pentest]]></category>
		<category><![CDATA[Research]]></category>
		<guid isPermaLink="false">/?p=7176</guid>

					<description><![CDATA[This article complements existing research referenced in the Further Reading section. Endpoint Detection and Response (EDR) solutions are essential to modern defensive architectures. Their abilities to monitor, block, and respond to threats are important for containment and remediation. However, like all complex systems, EDRs rely on components that can be turned against them. One of &#8230; <a href="/2025/08/25/blinding-edrs-a-deep-dive-into-wfp-manipulation/" class="more-link">Continue reading <span class="screen-reader-text">Blinding EDRs: A deep dive into WFP manipulation</span></a>]]></description>
		
		
		
			</item>
		<item>
		<title>SonicDoor &#8211; Cracking SonicWall&#8217;s SMA 500</title>
		<link>/2025/06/04/sonicdoor-attacking-sonicwalls-sma-500/</link>
		
		<dc:creator><![CDATA[Alain Mowat]]></dc:creator>
		<pubDate>Wed, 04 Jun 2025 09:36:07 +0000</pubDate>
				<category><![CDATA[Research]]></category>
		<category><![CDATA[Vulnerability]]></category>
		<guid isPermaLink="false">/?p=6642</guid>

					<description><![CDATA[While attempting to compare the security level of various VPN vendors, I kept falling down the path of searching for vulnerabilities instead. This blog post details the ones I discovered in SonicWall&#8217;s SMA 500, which were patched in December 2024. This post has been delayed to coincide with my talk at SecurityFest on this exact &#8230; <a href="/2025/06/04/sonicdoor-attacking-sonicwalls-sma-500/" class="more-link">Continue reading <span class="screen-reader-text">SonicDoor &#8211; Cracking SonicWall&#8217;s SMA 500</span></a>]]></description>
		
		
		
			</item>
		<item>
		<title>The effect of granting Azure Reader role on Azure Container Registry instances</title>
		<link>/2024/12/13/understanding-azure-container-registry-permissions-a-security-concern/</link>
		
		<dc:creator><![CDATA[Quentin Brusa]]></dc:creator>
		<pubDate>Fri, 13 Dec 2024 08:27:13 +0000</pubDate>
				<category><![CDATA[Research]]></category>
		<category><![CDATA[azure]]></category>
		<category><![CDATA[cloud]]></category>
		<category><![CDATA[research]]></category>
		<guid isPermaLink="false">/?p=6672</guid>

					<description><![CDATA[We observed that granting Azure Reader role at subscription or resource group level allows users to pull container images from Azure Container Registry instances, thus potentially reveling confidential or sensitive data to unauthorised parties. In a recent security configuration review of one our client’s Azure workloads,&#160;we uncovered a significant issue regarding the Azure Container Registry &#8230; <a href="/2024/12/13/understanding-azure-container-registry-permissions-a-security-concern/" class="more-link">Continue reading <span class="screen-reader-text">The effect of granting Azure Reader role on Azure Container Registry instances</span></a>]]></description>
		
		
		
			</item>
		<item>
		<title>Attacking Cortex XDR from an unprivileged user perspective</title>
		<link>/2024/12/05/attacking-cortex-xdr-from-an-unprivileged-user-perspective/</link>
		
		<dc:creator><![CDATA[Romain Melchiorre]]></dc:creator>
		<pubDate>Thu, 05 Dec 2024 12:49:41 +0000</pubDate>
				<category><![CDATA[Antivirus]]></category>
		<category><![CDATA[Research]]></category>
		<category><![CDATA[Vulnerability]]></category>
		<guid isPermaLink="false">/?p=6405</guid>

					<description><![CDATA[In late 2023, we launched a new form of service where multiple customers could co-fund research time on a given product they are all using. The goal of the Co-funded research is to find vulnerabilities and possible weaknesses within the product that could impact not only our customers&#8217; security, but anyone using the product. The &#8230; <a href="/2024/12/05/attacking-cortex-xdr-from-an-unprivileged-user-perspective/" class="more-link">Continue reading <span class="screen-reader-text">Attacking Cortex XDR from an unprivileged user perspective</span></a>]]></description>
		
		
		
			</item>
		<item>
		<title>Arbitrary web root file read in Sitecore before v10.4.0 rev. 010422</title>
		<link>/2024/11/25/arbitrary-web-root-file-read-in-sitecore-before-v10-4-0-rev-010422/</link>
		
		<dc:creator><![CDATA[Alain Mowat]]></dc:creator>
		<pubDate>Mon, 25 Nov 2024 13:34:08 +0000</pubDate>
				<category><![CDATA[Exploit]]></category>
		<category><![CDATA[Research]]></category>
		<category><![CDATA[Vulnerability]]></category>
		<guid isPermaLink="false">/?p=5725</guid>

					<description><![CDATA[As part of our continuous pentesting offering, we try to identify solutions used by multiple clients to guide our research efforts to deliver the greatest impact. That is why, recently, we spent some time searching for vulnerabilities within Sitecore to find what we initially thought to be a 0-day, but ended up having been already &#8230; <a href="/2024/11/25/arbitrary-web-root-file-read-in-sitecore-before-v10-4-0-rev-010422/" class="more-link">Continue reading <span class="screen-reader-text">Arbitrary web root file read in Sitecore before v10.4.0 rev. 010422</span></a>]]></description>
		
		
		
			</item>
		<item>
		<title>Exploiting KsecDD through Server Silos</title>
		<link>/2024/11/11/exploiting-ksecdd-through-server-silos/</link>
		
		<dc:creator><![CDATA[Clément Labro]]></dc:creator>
		<pubDate>Mon, 11 Nov 2024 13:13:58 +0000</pubDate>
				<category><![CDATA[Exploit]]></category>
		<category><![CDATA[Research]]></category>
		<guid isPermaLink="false">/?p=5731</guid>

					<description><![CDATA[Earlier this year, an intriguing admin-to-kernel technique was published by @floesen_ in the form of a proof-of-concept (PoC) on GitHub. The author mentioned a strong limitation involving LSASS and Server Silos, without providing much details about it. This piqued our interest, so we decided to give it a second look&#8230; This blog post was coauthored &#8230; <a href="/2024/11/11/exploiting-ksecdd-through-server-silos/" class="more-link">Continue reading <span class="screen-reader-text">Exploiting KsecDD through Server Silos</span></a>]]></description>
		
		
		
			</item>
		<item>
		<title>Privilege escalation through TPM Sniffing when BitLocker PIN is enabled</title>
		<link>/2024/10/28/privilege-escalation-through-tpm-sniffing-when-bitlocker-pin-is-enabled/</link>
		
		<dc:creator><![CDATA[Julien Oberson]]></dc:creator>
		<pubDate>Mon, 28 Oct 2024 08:45:51 +0000</pubDate>
				<category><![CDATA[Hardware]]></category>
		<category><![CDATA[Research]]></category>
		<guid isPermaLink="false">/?p=6045</guid>

					<description><![CDATA[This blog post offers additional insights following the presentation delivered at the Swiss Cyber Storm conference in Bern on October 22, 2024. Introduction TPM sniffing attacks are well documented and have been used for at least the last five years. In a nutshell, these attacks take advantage of two weaknesses related to the way discrete &#8230; <a href="/2024/10/28/privilege-escalation-through-tpm-sniffing-when-bitlocker-pin-is-enabled/" class="more-link">Continue reading <span class="screen-reader-text">Privilege escalation through TPM Sniffing when BitLocker PIN is enabled</span></a>]]></description>
		
		
		
			</item>
	</channel>
</rss>
