CAPEC-383: Harvesting Information via API Event Monitoring
ID
CAPEC-383
Typical Severity
Low
Status
Draft
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.
Weaknesses
Taxonomiy Mapping
Type | # ID | Name |
---|---|---|
ATTACK | 1056.004 | Input Capture: Credential API Hooking |