CAPECattack pattern

CAPEC-385 Transaction or Event Tampering via Application API Manipulation

Medium Official page ↗
Abstraction
Detailed
Status
Draft
Typical severity
Medium
CAPEC version
3.9

Description

An attacker hosts or joins an event or transaction within an application framework in order to change the content of messages or items that are being exchanged. Performing this attack allows the attacker to manipulate content in such a way as to produce messages or content that look authentic but may contain deceptive links, substitute one item or another, spoof an existing item and conduct a false exchange, or otherwise change the amounts or identity of what is being exchanged. The techniques require use of specialized software that allow the attacker to man-in-the-middle communications between the web browser and the remote system in order to change the content of various application elements. Often, items exchanged in game can be monetized via sales for coin, virtual dollars, etc. The purpose of the attack is for the attack to scam the victim by trapping the data packets involved the exchange and altering the integrity of the transfer process.

Prerequisites

• Targeted software is utilizing application framework APIs

Related

Child of · CAPEC (1)

  • CAPEC-384 Application API Message Manipulation via Man-in-the-Middle attack pattern

Weakness · CWE (5)

  • CWE-311 Missing Encryption of Sensitive Data weakness
  • CWE-345 Insufficient Verification of Data Authenticity weakness
  • CWE-346 Origin Validation Error weakness
  • CWE-471 Modification of Assumed-Immutable Data (MAID) weakness
  • CWE-602 Client-Side Enforcement of Server-Side Security weakness

Referenced by CWE · attack pattern (5)

  • CWE-311 Missing Encryption of Sensitive Data weakness
  • CWE-345 Insufficient Verification of Data Authenticity weakness
  • CWE-346 Origin Validation Error weakness
  • CWE-471 Modification of Assumed-Immutable Data (MAID) weakness
  • CWE-602 Client-Side Enforcement of Server-Side Security weakness