Standardseverity: MediumDraft

CAPEC-386Application API Navigation Remapping

Abstraction
Standard
Status
Draft
Severity
Medium

Description

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.

Related weaknesses· 5

CWE-471CWE-345CWE-346CWE-602CWE-311

Related attack patterns· 1

CAPEC-94 (ChildOf)

Exploits5

TypeTargetConfidenceTier
WeaknessInsufficient Verification of Data Authenticitycwe-345100%live
WeaknessModification of Assumed-Immutable Data (MAID)cwe-471100%live
WeaknessClient-Side Enforcement of Server-Side Securitycwe-602100%live
WeaknessOrigin Validation Errorcwe-346100%live
WeaknessMissing Encryption of Sensitive Datacwe-311100%live

Related by meaning· 6

Nearest entities by semantic similarity across the cs-graph corpus.

CAPEC
Application API Button Hijacking
CAPEC
Navigation Remapping To Propagate Malicious Content
CAPEC
Content Spoofing Via Application API Manipulation
CAPEC
Application API Message Manipulation via Man-in-the-Middle
CAPEC
Transaction or Event Tampering via Application API Manipulation
CAPEC
Action Spoofing
Sourced from MITRE CAPEC. Curated by Adam Lundqvist, SQUR.