| Name |
Manipulate Registry Information |
|
| Likelyhood of attack |
Typical severity |
| High |
Medium |
|
| Summary |
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. |
| Prerequisites |
The targeted application must rely on values stored in a registry. The adversary must have a means of elevating permissions in order to access and modify registry content through either administrator privileges (e.g., credentialed access), or a remote access tool capable of editing a registry through an API. |
| Solutions | Ensure proper permissions are set for Registry hives to prevent users from modifying keys. Employ a robust and layered defensive posture in order to prevent unauthorized users on your system. Employ robust identification and audit/blocking using an allowlist of applications on your system. Unnecessary applications, utilities, and configurations will have a presence in the system registry that can be leveraged by an adversary through this attack pattern. |
| Related Weaknesses |
|
CWE ID
|
Description
|
| CWE-15 |
External Control of System or Configuration Setting |
|
| Related CAPECS |
|
CAPEC ID
|
Description
|
| CAPEC-176 |
An attacker manipulates files or settings external to a target application which affect the behavior of that application. For example, many applications use external configuration files and libraries - modification of these entities or otherwise affecting the application's ability to use them would constitute a configuration/environment manipulation attack. |
|
| Taxonomy: ATTACK |
|
Entry ID
|
Entry Name
|
| 1112 |
Modify Registry |
| 1647 |
Plist Modification |
|