| Name |
Modification of Windows Service Configuration |
|
| Likelyhood of attack |
Typical severity |
| Low |
High |
|
| Summary |
An adversary exploits a weakness in access control to modify the execution parameters of a Windows service. Specifically, if the permissions for users and groups are not properly assigned and allow access to the registry keys used to store the configuration information for a service, then an adversary could change settings defining the path to the executable and cause a malicious binary to be executed. |
| Prerequisites |
The adversary must have the capability to write to the Windows Registry on the targeted system. |
| Solutions | Ensure proper permissions are set for Registry hives to prevent users from modifying keys for system components that may lead to privilege escalation. |
| Related Weaknesses |
|
CWE ID
|
Description
|
| CWE-284 |
Improper Access Control |
|
| Related CAPECS |
|
CAPEC ID
|
Description
|
| CAPEC-203 |
An adversary exploits a weakness in authorization in order to modify content within a registry (e.g., Windows Registry, Mac plist, application registry). Editing registry information can permit the adversary to hide configuration information or remove indicators of compromise to cover up activity. Many applications utilize registries to store configuration and service information. As such, modification of registry information can affect individual services (affecting billing, authorization, or even allowing for identity spoofing) or the overall configuration of a targeted application. For example, both Java RMI and SOAP use registries to track available services. Changing registry values is sometimes a preliminary step towards completing another attack pattern, but given the long term usage of many registry values, manipulation of registry information could be its own end. |
|
| Taxonomy: ATTACK |
|
Entry ID
|
Entry Name
|
| 1574.011 |
Hijack Execution Flow:Service Registry Permissions Weakness |
| 1543.003 |
Create or Modify System Process:Windows Service |
|