Logo
-

Byte Open Security

(ByteOS Network)

Log In

Sign Up

ByteOS

Security
Vulnerability Details
Registries
Custom Views
Weaknesses
Attack Patterns
Filters & Tools
CAPEC-94:Adversary in the Middle (AiTM)
Attack Pattern ID:94
Version:v3.9
Attack Pattern Name:Adversary in the Middle (AiTM)
Abstraction:Meta
Status:Stable
Likelihood of Attack:High
Typical Severity:Very High
DetailsContent HistoryRelated WeaknessesReports
▼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.

▼Alternate Terms
Man-in-the-Middle / MITM

Person-in-the-Middle / PiTM

Monkey-in-the-Middle

Monster-in-the-Middle

On-path Attacker

▼Relationships
NatureTypeIDName
ParentOfS219XML Routing Detour Attacks
ParentOfS384Application API Message Manipulation via Man-in-the-Middle
ParentOfS386Application API Navigation Remapping
ParentOfS466Leveraging Active Adversary in the Middle Attacks to Bypass Same Origin Policy
ParentOfS662Adversary in the Browser (AiTB)
ParentOfS701Browser in the Middle (BiTM)
CanFollowM216Communication Channel Manipulation
CanFollowS271Schema Poisoning
CanFollowD383Harvesting Information via API Event Monitoring
CanFollowS697DHCP Spoofing
CanPrecedeM151Identity Spoofing
CanPrecedeS668Key Negotiation of Bluetooth Attack (KNOB)
Nature: ParentOf
Type: Standard
ID: 219
Name: XML Routing Detour Attacks
Nature: ParentOf
Type: Standard
ID: 384
Name: Application API Message Manipulation via Man-in-the-Middle
Nature: ParentOf
Type: Standard
ID: 386
Name: Application API Navigation Remapping
Nature: ParentOf
Type: Standard
ID: 466
Name: Leveraging Active Adversary in the Middle Attacks to Bypass Same Origin Policy
Nature: ParentOf
Type: Standard
ID: 662
Name: Adversary in the Browser (AiTB)
Nature: ParentOf
Type: Standard
ID: 701
Name: Browser in the Middle (BiTM)
Nature: CanFollow
Type: Meta
ID: 216
Name: Communication Channel Manipulation
Nature: CanFollow
Type: Standard
ID: 271
Name: Schema Poisoning
Nature: CanFollow
Type: Detailed
ID: 383
Name: Harvesting Information via API Event Monitoring
Nature: CanFollow
Type: Standard
ID: 697
Name: DHCP Spoofing
Nature: CanPrecede
Type: Meta
ID: 151
Name: Identity Spoofing
Nature: CanPrecede
Type: Standard
ID: 668
Name: Key Negotiation of Bluetooth Attack (KNOB)
▼Execution Flow
Explore
1.

Determine Communication Mechanism

The adversary determines the nature and mechanism of communication between two components, looking for opportunities to exploit.

Technique
Perform a sniffing attack and observe communication to determine a communication protocol.
Look for application documentation that might describe a communication mechanism used by a target.
Experiment
1.

Position In Between Targets

The adversary inserts themself into the communication channel initially acting as a routing proxy between the two targeted components.

Technique
Install spyware on a client that will intercept outgoing packets and route them to their destination as well as route incoming packets back to the client.
Exploit a weakness in an encrypted communication mechanism to gain access to traffic. Look for outdated mechanisms such as SSL.
Exploit
1.

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.

Technique
Prevent some messages from reaching their destination, causing a denial of service.
▼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.

▼Resources Required
▼Indicators
▼Consequences
ScopeLikelihoodImpactNote
IntegrityN/AModify DataN/A
ConfidentialityAccess ControlAuthorizationN/AGain PrivilegesN/A
ConfidentialityN/ARead DataN/A
Scope: Integrity
Likelihood: N/A
Impact: Modify Data
Note: N/A
Scope: Confidentiality, Access Control, Authorization
Likelihood: N/A
Impact: Gain Privileges
Note: N/A
Scope: Confidentiality
Likelihood: N/A
Impact: Read Data
Note: N/A
▼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
▼Example Instances
▼Related Weaknesses
IDName
CWE-287Improper Authentication
CWE-290Authentication Bypass by Spoofing
CWE-294Authentication Bypass by Capture-replay
CWE-300Channel Accessible by Non-Endpoint
CWE-593Authentication Bypass: OpenSSL CTX Object Modified after SSL Objects are Created
ID: CWE-287
Name: Improper Authentication
ID: CWE-290
Name: Authentication Bypass by Spoofing
ID: CWE-294
Name: Authentication Bypass by Capture-replay
ID: CWE-300
Name: Channel Accessible by Non-Endpoint
ID: CWE-593
Name: Authentication Bypass: OpenSSL CTX Object Modified after SSL Objects are Created
▼Taxonomy Mappings
Taxonomy NameEntry IDEntry Name
ATTACK1557Adversary-in-the-Middle
OWASP AttacksN/AMan-in-the-middle attack
Taxonomy Name: ATTACK
Entry ID: 1557
Entry Name: Adversary-in-the-Middle
Taxonomy Name: OWASP Attacks
Entry ID: N/A
Entry Name: Man-in-the-middle attack
▼Notes
▼References
Reference ID: REF-553
Title: Computer Security: Art and Science
Author: M. Bishop
Publication:
Publisher:Addison-Wesley
Edition:
URL:
URL Date:
Day:N/A
Month:N/A
Year:2003
Reference ID: REF-633
Title: Man-in-the-middle attack
Author:
Publication:
Publisher:Open Web Application Security Project (OWASP)
Edition:
URL:https://owasp.org/www-community/attacks/Man-in-the-middle_attack
URL Date:2021-02-10
Day:N/A
Month:N/A
Year:N/A
Reference ID: REF-634
Title: What is a man-in-the-middle attack?
Author: Kyle Chivers
Publication:
Publisher:NortonLifeLock Inc.
Edition:
URL:https://us.norton.com/internetsecurity-wifi-what-is-a-man-in-the-middle-attack.html
URL Date:2021-02-10
Day:26
Month:03
Year:2020
Reference ID: REF-635
Title: Man in the middle (MITM) attack
Author:
Publication:
Publisher:Imperva
Edition:
URL:https://www.imperva.com/learn/application-security/man-in-the-middle-attack-mitm/
URL Date:2021-02-10
Day:N/A
Month:N/A
Year:N/A
Reference ID: REF-636
Title: Settling the score: taking down the Equifax mobile application
Author: Jerry Decime
Publication:
Publisher:
Edition:
URL:https://www.linkedin.com/pulse/settling-score-taking-down-equifax-mobile-application-jerry-decime/
URL Date:2021-02-10
Day:13
Month:09
Year:2017
Details not found