msidcrl40.dll

There are executables that allow msidcrl40.dll to be DLL hijacked.

DLL Hijacking type

DLL Sideloading

DLL Vendor

Microsoft

Last updated

Unknown

Expected Locations

The file msidcrl40.dll is normally found in the following path:

%PROGRAMFILES%\msn messenger

Resources

Acknowledgements

Thanks to Jai Minton of Huntress (@cyberrraiju).

Vulnerable Executables

DLL Sideloading (1 EXE)

By copying (and optionally renaming) any of the following vulnerable applications to a user-writeable folder, alongside a malicious msidcrl40.dll, arbitrary code can be executed through it.

%PROGRAMFILES%\msn messenger\livecall.exe

Detection

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

title: Possible DLL Hijacking of msidcrl40.dll
id: 2253401b-4592-48a3-2807-5b9ff8762429
status: experimental
description: Detects possible DLL hijacking of msidcrl40.dll by looking for suspicious image loads, loading this DLL from unexpected locations.
references:
    - https://hijacklibs.net/entries/microsoft/external/msidcrl40.html
author: "Jai Minton - HuntressLabs"
date: 2024-05-29
tags:
    - attack.defense_evasion
    - attack.T1574.001
logsource:
    product: windows
    category: image_load
detection:
    selection:
        ImageLoaded: '*\msidcrl40.dll'
    filter:
        ImageLoaded:
            - 'c:\program files\msn messenger\\*'
            - 'c:\program files (x86)\msn messenger\\*'

    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 msidcrl40.dll DLL Hijacking
id: 2253402b-4592-48a3-2807-5b9ff8762429
status: experimental
description: Detects possible DLL hijacking of msidcrl40.dll by looking for suspicious file writes of this DLL, to unexpected locations.
references:
    - https://hijacklibs.net/entries/microsoft/external/msidcrl40.html
author: "Jai Minton - HuntressLabs"
date: 2024-05-29
tags:
    - attack.defense_evasion
    - attack.T1574.001
logsource:
    product: windows
    category: file_event
detection:
    selection:
        TargetFileName: '*\msidcrl40.dll'
    filter:
        TargetFileName:
            - 'c:\program files\msn messenger\\*'
            - 'c:\program files (x86)\msn messenger\\*'

    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 Detection Content Feeds that comprise all DLL Hijacking entries part of HijackLibs.

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 msidcrl40.dll.

How do I abuse this vulnerability?

As a red teamer, you will have to compile your own version of msidcrl40.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