|
|
|
CAPEC-478: Modification of Windows Service Configuration |
Description An adversary exploits a weakness in access control to modify the execution parameters of a Windows service. The goal of this attack is to execute a malicious binary in place of an existing service. Likelihood Of Attack Typical Severity Execution Flow Explore Determine target system: The adversary must first determine the system they wish to modify the registry of. This needs to be a windows machine as this attack only works on the windows registry.
Experiment Gain access to the system: The adversary needs to gain access to the system in some way so that they can modify the windows registry. Techniques |
---|
Gain physical access to a system either through shoulder surfing a password or accessing a system that is left unlocked. | Gain remote access to a system through a variety of means. |
Exploit Modify windows registry: The adversary will modify the windows registry by changing the configuration settings for a service. Specifically, the adversary will change the path settings to define a path to a malicious binary to be executed.
Prerequisites
The adversary must have the capability to write to the Windows Registry on the targeted system. |
Resources Required
None: No specialized resources are required to execute this type of attack. |
Consequences This table specifies different individual consequences associated with the attack pattern. The Scope identifies the security property that is violated, while the Impact describes the negative technical impact that arises if an adversary succeeds in their attack. The Likelihood provides information about how likely the specific consequence is expected to be seen relative to the other consequences in the list. For example, there may be high likelihood that a pattern will be used to achieve a certain impact, but a low likelihood that it will be exploited to achieve a different impact.Scope | Impact | Likelihood |
---|
Integrity | Execute Unauthorized Commands | |
Mitigations
Ensure proper permissions are set for Registry hives to prevent users from modifying keys for system components that may lead to privilege escalation. |
Taxonomy Mappings CAPEC mappings to ATT&CK techniques leverage an inheritance model to streamline and minimize direct CAPEC/ATT&CK mappings. Inheritance of a mapping is indicated by text stating that the parent CAPEC has relevant ATT&CK mappings. Note that the ATT&CK Enterprise Framework does not use an inheritance model as part of the mapping to CAPEC.Relevant to the ATT&CK taxonomy mapping (also see parent) Entry ID | Entry Name |
---|
1574.011 | Hijack Execution Flow:Service Registry Permissions Weakness | 1543.003 | Create or Modify System Process:Windows Service |
Content History Submissions |
---|
Submission Date | Submitter | Organization |
---|
2018-04-25 (Version 2.11) | CAPEC Content Team | The MITRE Corporation | | Modifications |
---|
Modification Date | Modifier | Organization |
---|
2019-04-04 (Version 3.1) | CAPEC Content Team | The MITRE Corporation | Updated Related_Weaknesses | 2020-07-30 (Version 3.3) | CAPEC Content Team | The MITRE Corporation | Updated Taxonomy_Mappings | 2021-10-21 (Version 3.6) | CAPEC Content Team | The MITRE Corporation | Updated Description, Execution_Flow |
More information is available — Please select a different filter.
|