Detailedseverity: LowDraft
CAPEC-383Harvesting Information via API Event Monitoring
Abstraction
Detailed
Status
Draft
Severity
Low
Description
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.
Related weaknesses· 4
MITRE ATT&CK crosswalk· 1
Related attack patterns· 2
Exploits4
| Type | Target | Confidence | Tier |
|---|---|---|---|
| Weakness | Client-Side Enforcement of Server-Side Securitycwe-602 | 100% | live |
| Weakness | Cleartext Transmission of Sensitive Informationcwe-319 | 100% | live |
| Weakness | Unprotected Primary Channelcwe-419 | 100% | live |
| Weakness | Missing Encryption of Sensitive Datacwe-311 | 100% | live |
Related to1
| Type | Target | Confidence | Tier |
|---|---|---|---|
| SubTechnique | Credential API Hookingt1056.004 | 100% | live |
Related by meaning· 6
Nearest entities by semantic similarity across the cs-graph corpus.