| Name |
Modification of Registry Run Keys |
|
| Likelyhood of attack |
Typical severity |
| Medium |
Medium |
|
| Summary |
An adversary adds a new entry to the "run keys" in the registry so that an application of their choosing is executed when a user logs in. In this way, the adversary can get their executable to operate and run on the target system with the authorized user's level of permissions. |
| Prerequisites |
The adversary must have gained access to the target system via physical or logical means in order to carry out this attack. |
| Solutions | Identify programs that may be used to acquire process information and block them by using a software restriction policy or tools that restrict program execution by using a process allowlist. |
| Related Weaknesses |
|
CWE ID
|
Description
|
| CWE-15 |
External Control of System or Configuration Setting |
|
| 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
|
| 1547.001 |
Boot or Logon Autostart Execution:Registry Run Keys – Start Folder |
|