Home > CAPEC List > CAPEC-103: Clickjacking (Version 2.11)  

CAPEC-103: Clickjacking

 
Clickjacking
Definition in a New Window Definition in a New Window
Attack Pattern ID: 103
Abstraction: Standard
Status: Draft
Completeness: Complete
Presentation Filter:
+ Summary

In a clickjacking attack the victim is tricked into unknowingly initiating some action in one system while interacting with the UI from a seemingly completely different system. While being logged in to some target system, the victim visits the adversary's malicious site which displays a UI that the victim wishes to interact with. In reality, the clickjacked page has a transparent layer above the visible UI with action controls that the adversary wishes the victim to execute. The victim clicks on buttons or other UI elements they see on the page which actually triggers the action controls in the transparent overlaying layer. Depending on what that action control is, the adversary may have just tricked the victim into executing some potentially privileged (and most certainly undesired) functionality in the target system to which the victim is authenticated. The basic problem here is that there is a dichotomy between what the victim thinks they are clicking on versus what they are actually clicking on.

+ Attack Steps
Experiment
  1. Craft a clickjacking page: The adversary utilizes web page layering techniques to try to craft a malicious clickjacking page

    The adversary leveraged iframe overlay capabilities to craft a malicious clickjacking page

    The adversary leveraged Flash file overlay capabilities to craft a malicious clickjacking page

    The adversary leveraged Silverlight overlay capabilities to craft a malicious clickjacking page

    The adversary leveraged cross-frame scripting to craft a malicious clickjacking page

Exploit
  1. Adversary lures victim to clickjacking page: Adversary utilizes some form of temptation, misdirection or coercion to lure the victim to loading and interacting with the clickjacking page in a way that increases the chances that the victim will click in the right areas.

    Lure the victim to the malicious site by sending the victim an e-mail with a URL to the site.

    Lure the victim to the malicious site by manipulating URLs on a site trusted by the victim.

    Lure the victim to the malicious site through a cross-site scripting attack.

  2. Trick victim into interacting with the clickjacking page in the desired manner: The adversary tricks the victim into clicking on the areas of the UI which contain the hidden action controls and thereby interacts with the target system maliciously with the victim's level of privilege.

    Hide action controls over very commonly used functionality.

    Hide action controls over very psychologically tempting content.

+ Attack Prerequisites
  • The victim is communicating with the target application via a web based UI and not a thick client

  • The victim's browser security policies allow at least one of the following JavaScript, Flash, iFrames, ActiveX, or CSS.

  • The victim uses a modern browser that supports UI elements like clickable buttons (i.e. not using an old text only browser)

  • The victim has an active session with the target system.

  • The target system's interaction window is open in the victim's browser and supports the ability for initiating sensitive actions on behalf of the user in the target system

+ Typical Severity

High

+ Typical Likelihood of Exploit

Likelihood: Medium

+ Methods of Attack
  • Spoofing
  • Social Engineering
+ Examples-Instances

Description

A victim has an authenticated session with a site that provides an electronic payment service to transfer funds between subscribing members. At the same time, the victim receives an e-mail that appears to come from an online publication to which he or she subscribes with links to today's news articles. The victim clicks on one of these links and is taken to a page with the news story. There is a screen with an advertisement that appears on top of the news article with the 'skip this ad' button. Eager to read the news article, the user clicks on this button. Nothing happens. The user clicks on the button one more time and still nothing happens.

In reality, the victim activated a hidden action control located in a transparent layer above the 'skip this ad' button. The ad screen blocking the news article made it likely that the victim would click on the 'skip this ad' button. Clicking on the button, actually initiated the transfer of $1000 from the victim's account with an electronic payment service to an adversary's account. Clicking on the 'skip this ad' button the second time (after nothing seemingly happened the first time) confirmed the transfer of funds to the electronic payment service.

+ Attacker Skills or Knowledge Required

Skill or Knowledge Level: High

Crafting the proper malicious site and luring the victim to this site are not trivial tasks.

+ Resources Required

None: No specialized resources are required to execute this type of attack.

+ Solutions and Mitigations

If using the Firefox browser, use the NoScript plug-in that will help forbid iFrames.

Turn off JavaScript, Flash and disable CSS.

When maintaining an authenticated session with a privileged target system, do not use the same browser to navigate to unfamiliar sites to perform other activities. Finish working with the target system and logout first before proceeding to other tasks.

+ Attack Motivation-Consequences
ScopeTechnical ImpactNote
Confidentiality
Access_Control
Authorization
Gain privileges / assume identity
Integrity
Modify application data
Modify files or directories
Modify memory
Confidentiality
Read application data
Read memory
Read files or directories
Availability
DoS: crash / exit / restart
DoS: instability
+ Relevant Security Requirements

Enforce maximum security restrictions in the browser: JavaScript disabled, Flash disabled, CSS disabled, iFrames forbidden

+ Purposes
  • Exploitation
+ CIA Impact
Confidentiality Impact: HighIntegrity Impact: HighAvailability Impact: Low
+ Technical Context
Architectural Paradigms
Client-Server
Frameworks
All
Platforms
All
Languages
All
+ Content History
Submissions
SubmitterOrganizationDateSource
CAPEC Content TeamThe MITRE Corporation2014-06-23Internal_CAPEC_Team
Modifications
ModifierOrganizationDateCommentsSource
CAPEC Content TeamThe MITRE Corporation2017-08-04Updated Attack_Phases, Description Summary, Examples-Instances, Related_Weaknesses, Resources_RequiredInternal

More information is available — Please select a different filter.
Page Last Updated or Reviewed: July 31, 2017