CAPEC-386: Application API Navigation Remapping

Overview

CAPEC-386 (Application API Navigation Remapping) is a standard-level attack pattern catalogued by MITRE in the Common Attack Pattern Enumeration and Classification (CAPEC). It describes a recurring method attackers use to exploit software weaknesses.

What the attacker needs

Prerequisites

Targeted software is utilizing application framework APIs

Resources required

A software program that allows the use of adversary-in-the-middle (CAPEC-94) communications between the client and server, such as a man-in-the-middle proxy.

The CWE weaknesses that CAPEC-386 exploits.

How this attack relates to others in the CAPEC hierarchy.

Parent

CAPEC-94: Adversary in the Middle (AiTM)

Child

Frequently asked questions

Common questions about CAPEC-386.

What is CAPEC-386?

An attacker manipulates either egress or ingress data from a client within an application framework in order to change the destination and/or content of links/buttons displayed to a user within API messages. Performing this attack allows the attacker to manipulate content in such a way as to produce messages or content that looks authentic but contains links/buttons that point to an attacker controlled destination. Some applications make navigation remapping more difficult to detect because the actual HREF values of images, profile elements, and links/buttons are masked. One example would be to place an image in a user's photo gallery that when clicked upon redirected the user to an off-site location. Also, traditional web vulnerabilities (such as CSRF) can be constructed with remapped buttons or links. In some cases navigation remapping can be used for Phishing attacks or even means to artificially boost the page view, user site reputation, or click-fraud.

What weaknesses does CAPEC-386 target?

CAPEC-386 exploits 5 CWE weaknesses, including CWE-311 (Missing Encryption of Sensitive Data), CWE-345 (Insufficient Verification of Data Authenticity), CWE-346 (Origin Validation Error), CWE-471 (Modification of Assumed-Immutable Data (MAID)).

How severe is CAPEC-386?

MITRE rates CAPEC-386 as Medium severity.

References

MITRE CAPEC definition (CAPEC-386) (opens in a new tab)

Attack-pattern data is sourced from the MITRE CAPEC catalog (v3.9). Weakness associations link to the corresponding CWE entries on RadicalNotion.AI.