CAPEC-383 Harvesting Information via API Event Monitoring

CAPEC ID: 383

CAPEC-383 Metadata

Likelihood of Attack

High

Typical Severity

Low

Overview

Summary

An adversary hosts an event within an application framework and then monitors the data exchanged during the course of the event for the purpose of harvesting any important data leaked during the transactions. One example could be harvesting lists of usernames or userIDs for the purpose of sending spam messages to those users. One example of this type of attack involves the adversary creating an event within the sub-application. Assume the adversary hosts a "virtual sale" of rare items. As other users enter the event, the attacker records via AiTM (CAPEC-94) proxy the user_ids and usernames of everyone who attends. The adversary would then be able to spam those users within the application using an automated script.

Prerequisites

The target software is utilizing application framework APIs

Potential Solutions / Mitigations

Leverage encryption techniques during information transactions so as to protect them from attack patterns of this kind.

Related Weaknesses (CWE)

CWE ID Description
CWE-311 Missing Encryption of Sensitive Data
CWE-319 Cleartext Transmission of Sensitive Information
CWE-419 Unprotected Primary Channel
CWE-602 Client-Side Enforcement of Server-Side Security

Related CAPECs

CAPEC ID Description
CAPEC-94 An adversary targets the communication between two components (typically client and server), in order to alter or obtain data from transactions. A general approach entails the adversary placing themself within the communication channel between the two components.
CAPEC-407 An adversary engages in pretexting behavior to solicit information from target persons, or manipulate the target into performing some action that serves the adversary's interests. During a pretexting attack, the adversary creates an invented scenario, assuming an identity or role to persuade a targeted victim to release information or perform some action. It is more than just creating a lie; in some cases it can be creating a whole new identity and then using that identity to manipulate the receipt of information.

Taxonomy Mappings

Taxonomy: ATTACK

Entry ID Entry Name
1056.004 Input Capture: Credential API Hooking

Stay Ahead of Attack Patterns

Understanding CAPEC patterns helps security professionals anticipate and thwart potential attacks. Leverage these insights to enhance threat modeling, strengthen your software development lifecycle, and train your security teams effectively.