<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/"><channel><title>Microsoft Diagnostics Troubleshooting Wizard - CraftedSignal Threat Feed</title><link>https://feed.craftedsignal.io/products/microsoft-diagnostics-troubleshooting-wizard/</link><description>Trending threats, MITRE ATT&amp;CK coverage, and detection metadata. Fed continuously.</description><generator>Hugo</generator><language>en</language><managingEditor>hello@craftedsignal.io</managingEditor><webMaster>hello@craftedsignal.io</webMaster><lastBuildDate>Tue, 02 Jan 2024 12:00:00 +0000</lastBuildDate><atom:link href="https://feed.craftedsignal.io/products/microsoft-diagnostics-troubleshooting-wizard/feed.xml" rel="self" type="application/rss+xml"/><item><title>Microsoft Diagnostics Troubleshooting Wizard (MSDT) Proxy Execution Abuse</title><link>https://feed.craftedsignal.io/briefs/2024-01-02-msdt-proxy-execution/</link><pubDate>Tue, 02 Jan 2024 12:00:00 +0000</pubDate><author>hello@craftedsignal.io</author><guid isPermaLink="true">https://feed.craftedsignal.io/briefs/2024-01-02-msdt-proxy-execution/</guid><description>The Microsoft Diagnostics Troubleshooting Wizard (MSDT) can be abused to proxy malicious command or binary execution via malicious process arguments, potentially leading to defense evasion and arbitrary code execution.</description><content:encoded><![CDATA[<p>The Microsoft Diagnostics Troubleshooting Wizard (MSDT) is a legitimate Windows tool designed to diagnose and resolve system issues. However, attackers can abuse MSDT to execute malicious commands or binaries by manipulating its process arguments. This technique, often referred to as &quot;living off the land,&quot; allows adversaries to bypass traditional security measures by proxying their malicious actions through a trusted system utility. This particular rule focuses on identifying instances where MSDT is used with suspicious arguments or from unusual locations. Observed exploitation has been linked to the abuse of the &quot;Follina&quot; vulnerability (CVE-2022-30190), although this rule is designed to detect broader MSDT abuse patterns, not just specific CVE exploitation. This technique allows attackers to evade detection by blending in with legitimate system activity and potentially gaining elevated privileges.</p>
<h2 id="attack-chain">Attack Chain</h2>
<ol>
<li>The attacker gains initial access via an arbitrary code execution vulnerability or other means.</li>
<li>The attacker crafts a malicious payload designed to execute commands via MSDT. This payload often involves manipulating process arguments to achieve code execution.</li>
<li>A process such as <code>cmd.exe</code>, <code>powershell.exe</code>, or <code>mshta.exe</code> is used to launch <code>msdt.exe</code> with malicious arguments. This may include arguments like <code>IT_RebrowseForFile=*</code>, <code>*FromBase64*</code>, or arguments designed to trigger the execution of arbitrary code.</li>
<li><code>msdt.exe</code> is executed with the malicious arguments, effectively proxying the attacker's commands through a trusted system utility.</li>
<li>The attacker's commands are executed within the context of <code>msdt.exe</code>, potentially allowing them to bypass security restrictions or evade detection.</li>
<li>The attacker may use the proxied execution to download and execute additional payloads, establish persistence, or perform other malicious activities.</li>
<li>The attacker leverages the established foothold to move laterally within the network, compromising additional systems and escalating privileges.</li>
<li>The final objective is achieved, such as data exfiltration, ransomware deployment, or disruption of critical systems.</li>
</ol>
<h2 id="impact">Impact</h2>
<p>Successful exploitation of MSDT proxy execution can lead to a wide range of adverse impacts, including arbitrary code execution, privilege escalation, data theft, and system compromise. The use of a trusted system utility like MSDT makes it difficult to detect and prevent these attacks, potentially allowing attackers to operate undetected for extended periods. Specific impact depends on the attacker's goals but may include widespread data loss, financial damage, and reputational harm.</p>
<h2 id="recommendation">Recommendation</h2>
<ul>
<li>Deploy the &quot;Suspicious Microsoft Diagnostics Wizard Execution&quot; Sigma rule to your SIEM to detect suspicious <code>msdt.exe</code> executions.</li>
<li>Monitor process creation events for <code>msdt.exe</code> with suspicious command-line arguments, such as <code>IT_RebrowseForFile=*</code>, <code>*FromBase64*</code>, or <code>*/../../../*</code> (see Sigma rule).</li>
<li>Investigate any instances of <code>msdt.exe</code> being launched by unexpected parent processes, such as <code>cmd.exe</code>, <code>powershell.exe</code>, or <code>mshta.exe</code> (see Sigma rule).</li>
<li>Ensure that <code>msdt.exe</code> is running from a legitimate file path (<code>?:\\Windows\\system32\\msdt.exe</code> or <code>?:\\Windows\\SysWOW64\\msdt.exe</code>) and investigate any deviations.</li>
</ul>
]]></content:encoded><category domain="severity">high</category><category domain="type">advisory</category><category>defense-evasion</category><category>proxy-execution</category><category>msdt</category></item></channel></rss>