CMSTP UAC Bypass via COM Object Access
Detects UAC Bypass Attempt Using Microsoft Connection Manager Profile Installer Autoelevate-capable COM Objects (e.g. UACMe ID of 41, 43, 58 or 65)
Detection logic
Detection requirements
- Platform
- Windows
The rule states no platform. This is derived from the 2 ATT&CK techniques it maps to.
- Log source product
- windows
- Log source category
- process_creation
Known benign triggers
- Legitimate CMSTP use (unlikely in modern enterprise environments)
MITRE ATT&CK mappings
0 exclusive techniques.This is coverage no other published rule has; it is not this rule's total technique count.
References
| Reference | Cited by |
|---|---|
| github.com/hfiref0x/UACME | 33from 3 sources |
| medium.com/falconforce/falconfriday-detecting-uac-bypasses-0xff16-86c2a9107abf | 3 |
| twitter.com/hFireF0X/status/897640081053364225 | Only this detection cites it |
| web.archive.org/web/20190720093911/http://www.endurant.io/cmstp/detecting-cmstp-enabled-code-execution-and-uac-bypass-with-sysmon/ | 5 |
From the source
- At source
- Open at source
- Upstream identifier
- 4b60e6f2-bf39-47b4-b4ea-398e33cfe253
- Tagged by the source as
- attack.executionattack.g0069attack.privilege-escalationattack.stealthcar.2019-04-001
Licence
- Published under
- Detection Rule License 1.1Read the licence
- Attribution
- Required
Authorship
- Published
- Aug 26, 2026
- Version
- 1