Service Registry Permissions Weakness Check

Severity: medium
Author: frack113
Source: upstream

Adversaries may execute their own malicious payloads by hijacking the Registry entries used by services. Adversaries may use flaws in the permissions for registry to redirect from the originally specified executable to one that they control, in order to launch their own code at Service start. Windows stores local service configuration information in the Registry under HKLM\SYSTEM\CurrentControlSet\Services

MITRE ATT&CK coverage

Tactic	Techniques
Persistence	`T1574.011` Hijack Execution Flow: Services Registry Permissions Weakness
Privilege Escalation	`T1574.011` Hijack Execution Flow: Services Registry Permissions Weakness
Defense Evasion	`T1574.011` Hijack Execution Flow: Services Registry Permissions Weakness

Event coverage

Provider	Event ID	Title
PowerShell	4104	Creating Scriptblock text (MessageNumber of MessageTotal).

Stages and Predicates

Stage 1: `selection`

ScriptBlockText|contains: 'REGISTRY::HKLM\SYSTEM\CurrentControlSet\Services\'
ScriptBlockText|contains: get-acl

Indicators

Each row is a field, operator, and value that the rule matches. The corpus column counts how many other rules in the catalog look for the same combination: high numbers point to widely-used, community-vetted indicators. Blank or 1 shows that the indicator is specific to this rule.

Field	Kind	Values
`ScriptBlockText`	match	`REGISTRY::HKLM\SYSTEM\CurrentControlSet\Services\` `get-acl`

Neighbors

Broader alternatives (more inclusive than this rule)

These rules match a superset of what this rule catches. They cover the same events plus more. Use them if you want wider coverage and can absorb more false positives.

Potential PowerShell Obfuscation via Invalid Escape Sequences [elastic] (cross-vendor) (drops 2 filters this rule applies) (first-stage match only; downstream stages may differ)
Potential PowerShell Obfuscation via Backtick-Escaped Variable Expansion [elastic] (cross-vendor) (drops 2 filters this rule applies) (first-stage match only; downstream stages may differ)
Potential PowerShell Obfuscation via Character Array Reconstruction [elastic] (cross-vendor) (drops 2 filters this rule applies) (first-stage match only; downstream stages may differ)
Potential PowerShell Obfuscation via Concatenated Dynamic Command Invocation [elastic] (cross-vendor) (drops 2 filters this rule applies) (first-stage match only; downstream stages may differ)
Potential PowerShell Obfuscation via High Numeric Character Proportion [elastic] (cross-vendor) (drops 2 filters this rule applies) (first-stage match only; downstream stages may differ)
Potential Dynamic IEX Reconstruction via Environment Variables [elastic] (cross-vendor) (drops 2 filters this rule applies) (first-stage match only; downstream stages may differ)
Dynamic IEX Reconstruction via Method String Access [elastic] (cross-vendor) (drops 2 filters this rule applies) (first-stage match only; downstream stages may differ)
PowerShell Obfuscation via Negative Index String Reversal [elastic] (cross-vendor) (drops 2 filters this rule applies) (first-stage match only; downstream stages may differ)
Potential PowerShell Obfuscation via Reverse Keywords [elastic] (cross-vendor) (drops 2 filters this rule applies) (first-stage match only; downstream stages may differ)
Potential PowerShell Obfuscation via String Concatenation [elastic] (cross-vendor) (drops 2 filters this rule applies) (first-stage match only; downstream stages may differ)
Potential PowerShell Obfuscation via String Reordering [elastic] (cross-vendor) (drops 2 filters this rule applies) (first-stage match only; downstream stages may differ)
Potential PowerShell Obfuscation via Special Character Overuse [elastic] (cross-vendor) (drops 2 filters this rule applies) (first-stage match only; downstream stages may differ)