wmiutils.dll

Part of the HijackLibs project.

Type

Environment Variable-based DLL Hijacking (2 EXEs) By changing the %SYSTEMROOT% environment variable to an attacker-controlled directory, it is possible to trick a vulnerable application into loading a malicious wmiutils.dll from the attacker-controled location. See also MITRE ATT&CK® technique T1574: Hijack Execution Flow.

Vendor

Microsoft

Resources

https://wietze.github.io/blog/save-the-environment-variables

Acknowledgements

Thanks to Wietze (@wietze).

Last updated

Unknown

Expected Locations

The file wmiutils.dll is normally found in the following paths:

%SYSTEM32%\wbem
%SYSWOW64%\wbem

Vulnerable Executables

The following executables attempt to load wmiutils.dll:

%SYSTEM32%\stordiag.exe by changing %SYSTEMROOT%
%SYSTEM32%\tasklist.exe by changing %SYSTEMROOT%

Detection

Below a sample Sigma rule that will find processes that loaded wmiutils.dll located in a folder that is not one of the expected locations (see above).

title: Possible DLL Hijacking of wmiutils.dll
id: 9676101b-2897-48a3-6541-5b9ff8669284
status: experimental
description: Detects possible DLL hijacking of wmiutils.dll by looking for suspicious image loads, loading this DLL from unexpected locations.
references:
    - https://hijacklibs.net/entries/microsoft/built-in/wmiutils.html
author: "Wietze Beukema"
date: 2022-05-21
tags:
    - attack.defense_evasion
    - attack.T1574
logsource:
    product: windows
    category: image_load
detection:
    selection:
        ImageLoaded: '*\wmiutils.dll'
    filter:
        ImageLoaded:
            - 'c:\windows\system32\wbem\*'
            - 'c:\windows\syswow64\wbem\*'

    condition: selection and not filter
falsepositives:
    - False positives are likely. This rule is more suitable for hunting than for generating detections.

title: Possible preparation for wmiutils.dll DLL Hijacking
id: 9676102b-2897-48a3-6541-5b9ff8669284
status: experimental
description: Detects possible DLL hijacking of wmiutils.dll by looking for suspicious file writes of this DLL, to unexpected locations.
references:
    - https://hijacklibs.net/entries/microsoft/built-in/wmiutils.html
author: "Wietze Beukema"
date: 2022-05-21
tags:
    - attack.defense_evasion
    - attack.T1574
logsource:
    product: windows
    category: file_event
detection:
    selection:
        TargetFileName: '*\wmiutils.dll'
    filter:
        TargetFileName:
            - 'c:\windows\system32\wbem\*'
            - 'c:\windows\syswow64\wbem\*'
            - 'c:\windows\winsxs\*'
            - 'c:\$windows.~bt\*'
            - 'c:\windows\softwaredistribution\*'

    condition: selection and not filter
falsepositives:
    - False positives are likely. This rule is more suitable for hunting than for generating detections.

Note that this rule is also included in the Sigma feed that comprises all DLL Hijacking entries part of this project.

FAQs

Why should I care about this?
DLL Hijacking enables the execution of malicious code through a signed and/or trusted executable. Defensive measures such as AV and EDR solutions may not pick up on this activity out of the box, and allow-list applications such as AppLocker may not block the execution of the untrusted code. There are numerous examples of threat actors that have been observed to leaverage DLL Hijacking to achieve their objectives. As such, this project wants to encourage you to monitor for unusual activity involving wmiutils.dll.

How do I abuse this vulnerability?
As a red teamer, you will have to compile your own version of wmiutils.dll. There are various guides on how this can be achieved.

How could the vendor have prevented this vulnerability?
Most DLL Hijacking vulnerabilities are introduced by the 'lazy' loading of DLL files, which relies on Windows' default DLL search order. Explicitly specifying where a required DLL is located is easy and often already helps a lot. This doesn't have to hurt portability if Windows API calls are used to obtain paths, e.g. GetSystemDirectory to get the path of the System32 folder. Even better is to check the signature of required DLLs prior to loading them; most platforms, frameworks and/or runtimes offer means to verify DLL signatures with minimal performance impact.

This DLL Hijack doesn't seem to work (anymore), why is it still included?
Luckily, vendors regularly patch vulnerable applications in order to prevent DLL Hijacking from taking place. Nevertheless, older versions will remain vulnerable; for that reason, the entry won't be deleted from this project. To help others, you may want to open a pull request updating the 'precondition' tag on this entry to make the community aware of the reduced scope.

Homepage | API | Contributors