<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>RDP on THALIUM</title><link>/tags/rdp/</link><description>Recent content in RDP on THALIUM</description><generator>Hugo</generator><language>en-us</language><copyright>Copyright (c) 2026, all rights reserved.</copyright><lastBuildDate>Fri, 14 Oct 2022 00:00:00 +0000</lastBuildDate><atom:link href="/tags/rdp/index.xml" rel="self" type="application/rss+xml"/><item><title>Fuzzing RDPEGFX with "what the fuzz"</title><link>/posts/rdpegfx/</link><pubDate>Fri, 14 Oct 2022 00:00:00 +0000</pubDate><guid>/posts/rdpegfx/</guid><description>Microsoft’s Remote Desktop Protocol (RDP) client was fuzzed by various teams in the past few years, it thus seemed like a good target to try a recent snapshot fuzzer: &lt;a href="https://github.com/0vercl0k/wtf"&gt;what the fuzz (wtf)&lt;/a&gt; (of which we are only users). In this companion post to our &lt;a href="https://www.hexacon.fr/conference/speakers/#fuzzing_rdpegfx"&gt;Hexacon 2022 talk&lt;/a&gt; (&lt;a href="/posts/misc/rdpegfx/Hexacon2022-Fuzzing_RDPEGFX_with_wtf.pdf"&gt;slides&lt;/a&gt;, &lt;a href="https://youtu.be/4pftjmKqeoM"&gt;video&lt;/a&gt;) we’ll show how we took advantage of wtf flexibility in order to efficiently fuzz the RDPEGFX channel of Microsoft RDP client and uncover &lt;a href="https://msrc.microsoft.com/update-guide/en-US/vulnerability/CVE-2022-30221"&gt;CVE-2022-30221&lt;/a&gt;.</description></item><item><title>Remote Deserialization Bug in Microsoft's RDP Client through Smart Card Extension (CVE-2021-38666)</title><link>/posts/deserialization-bug-through-rdp-smart-card-extension/</link><pubDate>Fri, 10 Dec 2021 06:00:01 +0100</pubDate><guid>/posts/deserialization-bug-through-rdp-smart-card-extension/</guid><description>&lt;p&gt;This is the &lt;strong&gt;third installment&lt;/strong&gt; in my three-part series of articles on fuzzing Microsoft&amp;rsquo;s RDP client, where I explain a bug I found by fuzzing the &lt;strong&gt;smart card extension&lt;/strong&gt;.&lt;/p&gt;</description></item><item><title>Remote ASLR Leak in Microsoft's RDP Client through Printer Cache Registry (CVE-2021-38665)</title><link>/posts/leaking-aslr-through-rdp-printer-cache-registry/</link><pubDate>Fri, 10 Dec 2021 06:00:00 +0100</pubDate><guid>/posts/leaking-aslr-through-rdp-printer-cache-registry/</guid><description>&lt;p&gt;This is the &lt;strong&gt;second installment&lt;/strong&gt; in my three-part series of articles on fuzzing Microsoft&amp;rsquo;s RDP client. I will explain a bug I found by fuzzing the &lt;strong&gt;printer sub-protocol&lt;/strong&gt;, and how I exploited it.&lt;/p&gt;</description></item><item><title>Fuzzing Microsoft's RDP Client using Virtual Channels: Overview &amp; Methodology</title><link>/posts/fuzzing-microsoft-rdp-client-using-virtual-channels/</link><pubDate>Wed, 10 Nov 2021 12:00:00 +0000</pubDate><guid>/posts/fuzzing-microsoft-rdp-client-using-virtual-channels/</guid><description>&lt;p&gt;This article begins my three-part series on fuzzing Microsoft&amp;rsquo;s RDP client. In this &lt;strong&gt;first installment&lt;/strong&gt;, I set up a methodology for &lt;strong&gt;fuzzing Virtual Channels&lt;/strong&gt; using WinAFL and share some of my findings.&lt;/p&gt;</description></item></channel></rss>