<?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>Windows Server — CraftedSignal Threat Feed</title><link>https://feed.craftedsignal.io/products/windows-server/</link><description>Trending threats, MITRE ATT&amp;CK coverage, and detection metadata — refreshed continuously.</description><generator>Hugo</generator><language>en</language><managingEditor>hello@craftedsignal.io</managingEditor><webMaster>hello@craftedsignal.io</webMaster><lastBuildDate>Wed, 03 Jan 2024 12:00:00 +0000</lastBuildDate><atom:link href="https://feed.craftedsignal.io/products/windows-server/feed.xml" rel="self" type="application/rss+xml"/><item><title>Abuse of dnscmd.exe to Modify DNS ServerLevelPluginDLL</title><link>https://feed.craftedsignal.io/briefs/2024-01-dnscmd-serverlevelplugin/</link><pubDate>Wed, 03 Jan 2024 12:00:00 +0000</pubDate><author>hello@craftedsignal.io</author><guid isPermaLink="true">https://feed.craftedsignal.io/briefs/2024-01-dnscmd-serverlevelplugin/</guid><description>Attackers can use dnscmd.exe with administrative privileges to configure the Microsoft DNS ServerLevelPluginDll setting, allowing them to load arbitrary DLLs and execute code within the DNS service context for persistence and privilege escalation.</description><content:encoded><![CDATA[<p>The Microsoft DNS ServerLevelPluginDll setting allows the DNS service to load arbitrary DLLs. An attacker with DNS administrative privileges can abuse <code>dnscmd.exe</code> to modify this setting and load a malicious DLL. This grants the attacker code execution in the context of the DNS service. This technique can be leveraged for persistence, privilege escalation, and even domain compromise. The abuse of this setting is particularly concerning because the DNS service often runs with elevated privileges, making it a highly desirable target for attackers. This technique has been observed in the wild and documented publicly, highlighting its potential for real-world impact. Defenders should monitor for unauthorized modifications to the ServerLevelPluginDll setting via <code>dnscmd.exe</code> to mitigate this threat.</p>
<h2 id="attack-chain">Attack Chain</h2>
<ol>
<li>An attacker gains initial access through existing compromises or leveraging exploits.</li>
<li>The attacker escalates privileges to obtain DNS administrative rights.</li>
<li>The attacker executes <code>dnscmd.exe</code> with the <code>/config</code> and <code>/serverlevelplugindll</code> parameters to set a malicious DLL.</li>
<li>The DNS service loads the attacker-controlled DLL.</li>
<li>The malicious DLL executes arbitrary code within the context of the DNS service.</li>
<li>The attacker achieves persistence by ensuring the malicious DLL is loaded on each DNS service restart.</li>
<li>The attacker leverages the elevated privileges of the DNS service to perform actions such as lateral movement or data exfiltration.</li>
</ol>
<h2 id="impact">Impact</h2>
<p>Successful exploitation allows attackers to execute arbitrary code within the highly privileged context of the Windows DNS Server service. This can lead to complete domain compromise, allowing the attacker to control critical network infrastructure. The impact can range from data theft and service disruption to complete takeover of the Active Directory environment. The number of potential victims is significant, encompassing any organization running Windows DNS Server.</p>
<h2 id="recommendation">Recommendation</h2>
<ul>
<li>Monitor process execution for <code>dnscmd.exe</code> with command-line arguments containing <code>/config</code> and <code>/serverlevelplugindll</code> using the provided Sigma rule.</li>
<li>Enable Sysmon Event ID 1 and Windows Event Log Security 4688 to capture process creation events.</li>
<li>Investigate any instances of <code>dnscmd.exe</code> modifying the ServerLevelPluginDll setting.</li>
<li>Implement strict access controls to limit who can administer the DNS service.</li>
<li>Deploy the Sigma rules in this brief to your SIEM and tune for your environment.</li>
</ul>
]]></content:encoded><category domain="severity">high</category><category domain="type">advisory</category><category>persistence</category><category>privilege-escalation</category><category>windows</category></item></channel></rss>