Microsoft Management Console File — CraftedSignal Threat Feedhttps://feed.craftedsignal.io/products/microsoft-management-console-file/Trending threats, MITRE ATT&CK coverage, and detection metadata — refreshed continuously.Hugoenhello@craftedsignal.iohello@craftedsignal.ioWed, 03 Jul 2024 10:00:00 +0000Microsoft Management Console File Execution from Unusual Pathhttps://feed.craftedsignal.io/briefs/2024-07-mmc-untrusted-path/Wed, 03 Jul 2024 10:00:00 +0000hello@craftedsignal.iohttps://feed.craftedsignal.io/briefs/2024-07-mmc-untrusted-path/Adversaries may use Microsoft Management Console (MMC) files from untrusted paths to bypass security controls for initial access and execution on Windows systems.Attackers may exploit Microsoft Management Console (MMC) by executing .msc files from non-standard directories to bypass security controls. This technique can be used for initial access and execution. This detection focuses on identifying the execution of mmc.exe with .msc files from paths outside the typical system directories, which are generally considered trusted. By monitoring process executions and filtering out known legitimate paths, analysts can identify potentially malicious activity related to the misuse of MMC. The rule aims to detect deviations from standard administrative practices that could indicate unauthorized access or command execution via malicious or compromised .msc files. The detection logic specifically excludes executions from common directories like System32, SysWOW64, and Program Files.

Attack Chain

  1. An attacker gains initial access to the system through an unspecified method.
  2. The attacker places a malicious .msc file in an unusual or untrusted directory (e.g., C:\Users\Public).
  3. The attacker executes mmc.exe with the malicious .msc file as an argument from the untrusted path.
  4. mmc.exe processes the .msc file, potentially executing embedded commands or scripts.
  5. The malicious .msc file performs unauthorized actions on the system, such as modifying system settings or executing arbitrary code.
  6. The attacker leverages the execution context of mmc.exe to bypass security controls and escalate privileges.
  7. The attacker may establish persistence by creating a scheduled task or modifying registry keys to execute the malicious .msc file automatically.

Impact

Successful exploitation can lead to unauthorized access, command execution, and privilege escalation, potentially compromising the entire system. While specific victim counts or sector targeting are not available, the technique is applicable across various Windows environments. The use of a trusted system binary like mmc.exe for malicious purposes can evade traditional security measures, making detection more challenging.

Recommendation

  • Implement the Sigma rule Microsoft Management Console File from Unusual Path to detect the execution of mmc.exe with .msc files from untrusted paths.
  • Enable process creation logging with command-line arguments to provide the necessary data for the Sigma rule to function effectively.
  • Investigate any alerts generated by the Sigma rule, focusing on the origin and content of the .msc file.
  • Consider implementing application control policies to restrict the execution of .msc files to authorized directories only.
  • Review and audit the use of MMC in the environment to identify any legitimate use cases that might trigger false positives.
]]>mediumadvisoryexecutiondefense-evasionwindows