An adversary actively probes the target in a manner that is designed to solicit information that could be leveraged for malicious purposes.
|
|
| ID | CAPEC-116 |
| Latest Sync Date | 11/05/25 15:15:38 |
| Original ID | 116 |
| Abstraction | Meta |
| Status | Stable |
| Alternate Terms | |
| Likelihood Of Attack | High |
| Typical Severity | Medium |
| Related Attack Patterns | ::NATURE:CanPrecede:CAPEC ID:163:: |
| Execution Flow | |
| Prerequisites | ::An adversary requires some way of interacting with the system.:: |
| Skills Required | |
| Resources Required | ::A tool, such as an Adversary in the Middle (CAPEC-94) Proxy or a fuzzer, that is capable of generating and injecting custom inputs to be used in the attack.:: |
| Indicators | |
| Consequences | ::SCOPE:Confidentiality:TECHNICAL IMPACT:Read Data:: |
| Mitigations | ::Minimize error/response output to only what is necessary for functional use or corrective language.::Remove potentially sensitive information that is not necessary for the application's functionality.:: |
| Example Instances | |
| Related Weaknesses | ::200::1243:: |
| Taxonomy Mappings | |
| Notes | TYPE:Other:NOTE:Large quantities of data is often moved from the target system to some other adversary controlled system. Data found on a target system might require extensive resources to be fully analyzed. Using these resources on the target system might enable a defender to detect the adversary. Additionally, proper analysis tools required might not be available on the target system.::::TYPE:Other:NOTE:This attack differs from Data Interception and other data collection attacks in that the attacker actively queries the target rather than simply watching for the target to reveal information.:: |