CAPECattack pattern

CAPEC-103 Clickjacking

High Official page ↗
Abstraction
Standard
Status
Draft
Likelihood of attack
Medium
Typical severity
High
CAPEC version
3.9

Description

An adversary tricks a victim into unknowingly initiating some action in one system while interacting with the UI from a seemingly completely different, usually an adversary controlled or intended, system.

Extended description

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.

Execution flow

1. [Experiment] [Craft a clickjacking page] The adversary utilizes web page layering techniques to try to craft a malicious clickjacking page 2. [Exploit] [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. 3. [Exploit] [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.

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

Skills required

• [High] Crafting the proper malicious site and luring the victim to this site are not trivial tasks.

Consequences

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

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.

Related

Child of · CAPEC (1)

Weakness · CWE (1)

  • CWE-1021 Improper Restriction of Rendered UI Layers or Frames weakness

Referenced by CAPEC · child of (3)

  • CAPEC-181 Flash File Overlay attack pattern
  • CAPEC-222 iFrame Overlay attack pattern
  • CAPEC-587 Cross Frame Scripting (XFS) attack pattern

Referenced by CWE · attack pattern (1)

  • CWE-1021 Improper Restriction of Rendered UI Layers or Frames weakness