Mmc — CraftedSignal Threat Feedhttps://feed.craftedsignal.io/tags/mmc/Trending threats, MITRE ATT&CK coverage, and detection metadata — refreshed continuously.Hugoenhello@craftedsignal.iohello@craftedsignal.ioWed, 24 Jan 2024 10:00:00 +0000UAC Bypass via Windows Firewall MMC Snap-In Hijackhttps://feed.craftedsignal.io/briefs/2024-01-uac-bypass-winfw-mmc/Wed, 24 Jan 2024 10:00:00 +0000hello@craftedsignal.iohttps://feed.craftedsignal.io/briefs/2024-01-uac-bypass-winfw-mmc/Attackers bypass User Account Control (UAC) by hijacking the Microsoft Management Console (MMC) Windows Firewall snap-in to execute code with elevated permissions, potentially leading to system compromise.This threat involves the exploitation of a User Account Control (UAC) bypass technique on Windows systems. Attackers leverage the Microsoft Management Console (MMC) and its Windows Firewall snap-in (WF.msc) to execute arbitrary code with elevated privileges. By hijacking this trusted process, malicious actors can circumvent security measures designed to restrict unauthorized access and modifications to the system. This UAC bypass method allows attackers to stealthily execute code, potentially leading to privilege escalation, malware installation, or data exfiltration. The technique is relevant to defenders because it enables attackers to bypass standard security controls, increasing the risk of successful compromise. This activity has been observed in various forms and can be adapted to deliver a range of malicious payloads.

Attack Chain

  1. User executes a seemingly benign application or script.
  2. The application triggers the execution of mmc.exe with the WF.msc argument, launching the Windows Firewall snap-in.
  3. A malicious process is spawned as a child process of mmc.exe. This is the key indicator of compromise.
  4. The malicious process exploits a vulnerability or misconfiguration within the MMC snap-in or related components.
  5. The exploited process gains elevated privileges, bypassing UAC restrictions.
  6. The attacker uses these elevated privileges to perform malicious actions, such as installing malware or modifying system settings.
  7. The attacker achieves persistence through registry modifications or scheduled tasks.
  8. The final objective is achieved, such as data exfiltration, system compromise, or lateral movement within the network.

Impact

A successful UAC bypass can lead to a significant compromise of the targeted system. Attackers can install persistent backdoors, escalate privileges, and gain control over critical system functions. This can result in data theft, system instability, or complete system takeover. The impact is amplified in environments where UAC is relied upon as a primary security control, potentially affecting a large number of systems across an organization.

Recommendation

  • Deploy the Sigma rule “UAC Bypass via Windows Firewall MMC Snap-In Hijack” to your SIEM to detect suspicious processes spawned by mmc.exe with the “WF.msc” argument.
  • Monitor process creation events for unexpected child processes of mmc.exe using process monitoring tools and tune the Sigma rule accordingly.
  • Enable process auditing and Sysmon event logging (Event ID 1) to capture detailed information about process creations, as specified in the setup instructions of the original rule.
  • Investigate any alerts generated by the Sigma rule, focusing on the parent process chain and the actions performed by the spawned process.
  • Refer to the references provided for more information on UAC bypass techniques and mitigation strategies.
]]>mediumadvisoryuac-bypassprivilege-escalationwindows-firewallmmc