CAPECattack pattern

CAPEC-94 Adversary in the Middle (AiTM)

Very High Official page ↗
Abstraction
Meta
Status
Stable
Likelihood of attack
High
Typical severity
Very High
CAPEC version
3.9

Description

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.

Extended description

Whenever one component attempts to communicate with the other (data flow, authentication challenges, etc.), the data first flows through the adversary, who has the opportunity to observe or alter it, before being passed on to the intended recipient as if it was never observed. This interposition is transparent leaving the two compromised components unaware of the potential corruption or leakage of their communications. The potential for these attacks yields an implicit lack of trust in communication or identify between two components. These attacks differ from Sniffing Attacks (CAPEC-157) since these attacks often modify the communications prior to delivering it to the intended recipient.

Execution flow

1. [Explore] [Determine Communication Mechanism] The adversary determines the nature and mechanism of communication between two components, looking for opportunities to exploit. 2. [Experiment] [Position In Between Targets] The adversary inserts themself into the communication channel initially acting as a routing proxy between the two targeted components. 3. [Exploit] [Use Intercepted Data Maliciously] The adversary observes, filters, or alters passed data of its choosing to gain access to sensitive information or to manipulate the actions of the two target components for their own purposes.

Prerequisites

• There are two components communicating with each other. • An attacker is able to identify the nature and mechanism of communication between the two target components. • An attacker can eavesdrop on the communication between the target components. • Strong mutual authentication is not used between the two target components yielding opportunity for attacker interposition. • The communication occurs in clear (not encrypted) or with insufficient and spoofable encryption.

Skills required

• [Medium] This attack can get sophisticated since the attack may use cryptography.

Consequences

• Integrity: Modify Data • Confidentiality, Access Control, Authorization: Gain Privileges • Confidentiality: Read Data

Mitigations

• Ensure Public Keys are signed by a Certificate Authority • Encrypt communications using cryptography (e.g., SSL/TLS) • Use Strong mutual authentication to always fully authenticate both ends of any communications channel. • Exchange public keys using a secure channel

Related

Att&ck technique · MITRE ATT&CK (1)

  • T1557 Adversary-in-the-Middle technique

Can precede · CAPEC (2)

  • CAPEC-151 Identity Spoofing attack pattern
  • CAPEC-668 Key Negotiation of Bluetooth Attack (KNOB) attack pattern

Weakness · CWE (5)

  • CWE-287 Improper Authentication weakness
  • CWE-290 Authentication Bypass by Spoofing weakness
  • CWE-294 Authentication Bypass by Capture-replay weakness
  • CWE-300 Channel Accessible by Non-Endpoint weakness
  • CWE-593 Authentication Bypass: OpenSSL CTX Object Modified after SSL Objects are Created weakness

Referenced by CAPEC · can follow (1)

Referenced by CAPEC · can precede (3)

  • CAPEC-216 Communication Channel Manipulation attack pattern
  • CAPEC-383 Harvesting Information via API Event Monitoring attack pattern
  • CAPEC-697 DHCP Spoofing attack pattern

Referenced by CAPEC · child of (6)

  • CAPEC-219 XML Routing Detour Attacks attack pattern
  • CAPEC-384 Application API Message Manipulation via Man-in-the-Middle attack pattern
  • CAPEC-386 Application API Navigation Remapping attack pattern
  • CAPEC-466 Leveraging Active Adversary in the Middle Attacks to Bypass Same Origin Policy attack pattern
  • CAPEC-662 Adversary in the Browser (AiTB) attack pattern
  • CAPEC-701 Browser in the Middle (BiTM) attack pattern

Referenced by CWE · attack pattern (5)

  • CWE-287 Improper Authentication weakness
  • CWE-290 Authentication Bypass by Spoofing weakness
  • CWE-294 Authentication Bypass by Capture-replay weakness
  • CWE-300 Channel Accessible by Non-Endpoint weakness
  • CWE-593 Authentication Bypass: OpenSSL CTX Object Modified after SSL Objects are Created weakness