615 indexed
CAPECCAPEC attack patterns
615 MITRE CAPEC entries — attack patterns at meta, standard, and detailed abstraction levels. Filter by abstraction. Authored by Adam Lundqvist.
Showing 1–50 of 77 in Meta · page 1 of 2
| ID | Title | Summary |
|---|---|---|
| CAPEC-112 | Brute Force | In this attack, some asset (information, functionality, identity, etc.) is protected by a finite secret value. The attacker attempts to gain access to this ass… |
| CAPEC-113 | Interface Manipulation | An adversary manipulates the use or processing of an interface (e.g. Application Programming Interface (API) or System-on-Chip (SoC)) resulting in an adverse i… |
| CAPEC-114 | Authentication Abuse | An attacker obtains unauthorized access to an application, service or device either through knowledge of the inherent weaknesses of an authentication mechanism… |
| CAPEC-115 | Authentication Bypass | An attacker gains access to application, service, or device with the privileges of an authorized or privileged user by evading or circumventing an authenticati… |
| CAPEC-116 | Excavation | An adversary actively probes the target in a manner that is designed to solicit information that could be leveraged for malicious purposes. Metadata: meta CAP… |
| CAPEC-117 | Interception | An adversary monitors data streams to or from the target for information gathering purposes. This attack may be undertaken to solely gather sensitive informati… |
| CAPEC-122 | Privilege Abuse | An adversary is able to exploit features of the target that should be reserved for privileged users or administrators but are exposed to use by lower or non-pr… |
| CAPEC-123 | Buffer Manipulation | An adversary manipulates an application's interaction with a buffer in an attempt to read or modify data they shouldn't have access to. Buffer attacks are dist… |
| CAPEC-124 | Shared Resource Manipulation | An adversary exploits a resource shared between multiple applications, an application pool or hardware pin multiplexing to affect behavior. Resources may be sh… |
| CAPEC-125 | Flooding | An adversary consumes the resources of a target by rapidly engaging in a large number of interactions with the target. This type of attack generally exposes a … |
| CAPEC-129 | Pointer Manipulation | This attack pattern involves an adversary manipulating a pointer within a target application resulting in the application accessing an unintended memory locati… |
| CAPEC-130 | Excessive Allocation | An adversary causes the target to allocate excessive resources to servicing the attackers' request, thereby reducing the resources available for legitimate ser… |
| CAPEC-131 | Resource Leak Exposure | An adversary utilizes a resource leak on the target to deplete the quantity of the resource available to service legitimate requests. Metadata: meta CAPEC pat… |
| CAPEC-137 | Parameter Injection | An adversary manipulates the content of request parameters for the purpose of undermining the security of the target. Some parameter encodings use text charact… |
| CAPEC-148 | Content Spoofing | An adversary modifies content to make it contain something other than what the original content producer intended while keeping the apparent source of the cont… |
| CAPEC-151 | Identity Spoofing | Identity Spoofing refers to the action of assuming (i.e., taking on) the identity of some other entity (human or non-human) and then using that identity to acc… |
| CAPEC-153 | Input Data Manipulation | An attacker exploits a weakness in input validation by controlling the format, structure, and composition of data to an input-processing interface. By supplyin… |
| CAPEC-154 | Resource Location Spoofing | An adversary deceives an application or user and convinces them to request a resource from an unintended location. By spoofing the location, the adversary can … |
| CAPEC-161 | Infrastructure Manipulation | An attacker exploits characteristics of the infrastructure of a network entity in order to perpetrate attacks or information gathering on network objects or ef… |
| CAPEC-165 | File Manipulation | An attacker modifies file contents or attributes (such as extensions or names) of files in a manner to cause incorrect processing by an application. Attackers … |
| CAPEC-169 | Footprinting | An adversary engages in probing and exploration activities to identify constituents and properties of the target. Metadata: meta CAPEC pattern, status stable,… |
| CAPEC-171 | DEPRECATED: Variable Manipulation | This attack pattern has been deprecated as it is a duplicate of the existing attack pattern "CAPEC-77 : Manipulating User-Controlled Variables". Please refer t… |
| CAPEC-173 | Action Spoofing | An adversary is able to disguise one action for another and therefore trick a user into initiating one type of action when they intend to initiate a different … |
| CAPEC-175 | Code Inclusion | An adversary exploits a weakness on the target to force arbitrary code to be retrieved locally or from a remote location and executed. This differs from code i… |
| CAPEC-176 | Configuration/Environment Manipulation | An attacker manipulates files or settings external to a target application which affect the behavior of that application. For example, many applications use ex… |
| CAPEC-184 | Software Integrity Attack | An attacker initiates a series of events designed to cause a user, program, server, or device to perform actions which undermine the integrity of software code… |
| CAPEC-188 | Reverse Engineering | An adversary discovers the structure, function, and composition of an object, resource, or system by using a variety of analysis techniques to effectively dete… |
| CAPEC-192 | Protocol Analysis | An adversary engages in activities to decipher and/or decode protocol information for a network or application communication protocol used for transmitting inf… |
| CAPEC-21 | Exploitation of Trusted Identifiers | Metadata: meta CAPEC pattern, status stable, likelihood high, severity high. Underlying weaknesses: CWE-290, CWE-302, CWE-346, CWE-539, CWE-6 (and 4 more). Map… |
| CAPEC-212 | Functionality Misuse | An adversary leverages a legitimate capability of an application in such a way as to achieve a negative technical impact. The system functionality is not alter… |
| CAPEC-216 | Communication Channel Manipulation | An adversary manipulates a setting or parameter on communications channel in order to compromise its security. This can result in information exposure, inserti… |
| CAPEC-22 | Exploiting Trust in Client | An attack of this type exploits vulnerabilities in client/server communication channel authentication and data integrity. It leverages the implicit trust a ser… |
| CAPEC-224 | Fingerprinting | An adversary compares output from a target system to known indicators that uniquely identify specific details about the target. Most commonly, fingerprinting i… |
| CAPEC-227 | Sustained Client Engagement | An adversary attempts to deny legitimate users access to a resource by continually engaging a specific resource in an attempt to keep the resource tied up as l… |
| CAPEC-233 | Privilege Escalation | An adversary exploits a weakness enabling them to elevate their privilege and perform an action that they are not supposed to be authorized to perform. Metada… |
| CAPEC-240 | Resource Injection | An adversary exploits weaknesses in input validation by manipulating resource identifiers enabling the unintended modification or specification of a resource. … |
| CAPEC-241 | DEPRECATED: Code Injection | This attack pattern has been deprecated as it is a duplicate of the existing attack pattern "CAPEC-242 : Code Injection". Please refer to this other CAPEC goin… |
| CAPEC-242 | Code Injection | An adversary exploits a weakness in input validation on the target to inject new code into that which is currently executing. This differs from code inclusion … |
| CAPEC-248 | Command Injection | An adversary looking to execute a command of their choosing, injects new items into an existing command thus modifying interpretation away from what was intend… |
| CAPEC-25 | Forced Deadlock | The adversary triggers and exploits a deadlock condition in the target software to cause a denial of service. A deadlock can occur when two or more competing a… |
| CAPEC-257 | DEPRECATED: Abuse of Transaction Data Structure | This attack pattern has been deprecated as it was deemed not to be a legitimate attack pattern. Metadata: meta CAPEC pattern, status deprecated. Metadata: me… |
| CAPEC-26 | Leveraging Race Conditions | The adversary targets a race condition occurring when multiple processes access and manipulate the same resource concurrently, and the outcome of the execution… |
| CAPEC-264 | DEPRECATED: Environment Variable Manipulation | This attack pattern has been deprecated as it is a duplicate of the existing attack pattern "CAPEC-13 : Subverting Environment Variable Values". Please refer t… |
| CAPEC-265 | DEPRECATED: Global variable manipulation | This attack pattern has been deprecated as it is a duplicate of the existing attack pattern "CAPEC-77 : Manipulating User-Controlled Variables". Please refer t… |
| CAPEC-266 | DEPRECATED: Manipulate Canonicalization | This attack pattern has been deprecated. Metadata: meta CAPEC pattern, status deprecated. Metadata: meta CAPEC pattern, status deprecated. |
| CAPEC-269 | DEPRECATED: Registry Manipulation | This pattern has been deprecated as it was determined to be a duplicate of another pattern. Please refer to the pattern CAPEC-203 : Manipulate Application Regi… |
| CAPEC-272 | Protocol Manipulation | An adversary subverts a communications protocol to perform an attack. This type of attack can allow an adversary to impersonate others, discover sensitive info… |
| CAPEC-28 | Fuzzing | In this attack pattern, the adversary leverages fuzzing to try to identify weaknesses in the system. Fuzzing is a software security and functionality testing m… |
| CAPEC-288 | DEPRECATED: ICMP Echo Request Ping | This attack pattern has been deprecated as it is a duplicate of the existing attack pattern "CAPEC-285". Please refer to this other CAPEC going forward. Metad… |
| CAPEC-289 | DEPRECATED: Infrastructure-based footprinting | This attack pattern has been deprecated as it was determined to be an unnecessary layer of abstraction. Please refer to the meta level pattern CAPEC-169 : goin… |