Repository navigation
Mshta.exe - proxy execution of an attacker DLL via user-writable InProcServer32 (not COM activation) - #540
Open
xhaabx wants to merge 1 commit into
Open
Mshta.exe - proxy execution of an attacker DLL via user-writable InProcServer32 (not COM activation)#540xhaabx wants to merge 1 commit into
xhaabx wants to merge 1 commit into
Conversation
Standard-user DLL proxy execution via the user-writable HKCU InProcServer32 value
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Binary: mshta.exe (C:\Windows\System32\mshta.exe, C:\Windows\SysWOW64\mshta.exe)
Summary
On Windows 11 24H2/25H2, mshta.exe reads the default value of
HKCU\Software\Classes\CLSID\{25336920-03F9-11CF-8FD0-00AA00686F13}\InProcServer32and passes it directly to LoadLibrary, loading that DLL in-process with no signature or path validation. A standard user can set this value (HKCU, no elevation) to an attacker-controlled DLL and get code execution inside the signed mshta.exe, with an empty command line - bypassing all command-line and script-content detection.This is NOT COM activation / COM hijacking (the obvious objection), and it is falsifiable:
Precedent
This is the same shape as the already-accepted cmstp.exe /nf entry ("Proxy execution of a DLL through a registry modification" - it reads CmstpExtensionDll and passes it to LoadLibrary). This one is arguably stronger: cmstp /nf requires Administrator (HKLM), whereas this works as a standard user (HKCU).
Proposed addition
New Command on the existing Mshta entry (passes validation.py and yamllint):
Plus two detection IOCs, and reporter credit in Acknowledgement. Happy to adjust framing, MitreID, or wording per maintainer preference.