logo

Improper Restriction of Rendered UI Layers or Frames

Incomplete Base
Structure: Simple
Description

The web application does not restrict or incorrectly restricts frame objects or UI layers that belong to another application or domain, which can lead to user confusion about which interface the user is interacting with.

Extended Description

A web application is expected to place restrictions on whether it is allowed to be rendered within frames, iframes, objects, embed or applet elements. Without the restrictions, users can be tricked into interacting with the application when they were not intending to.
Common Consequences 1
Scope: Access Control

Impact: Gain Privileges or Assume IdentityBypass Protection MechanismRead Application DataModify Application Data

An attacker can trick a user into performing actions that are masked and hidden from the user's view. The impact varies widely, depending on the functionality of the underlying application. For example, in a social media application, clickjacking could be used to trik the user into changing privacy settings.
Detection Methods 1
Automated Static AnalysisHigh
Automated static analysis, commonly referred to as Static Application Security Testing (SAST), can find some instances of this weakness by analyzing source code (or binary/compiled code) without having to execute it. Typically, this is done by building a model of data flow and control flow, then searching for potentially-vulnerable patterns that connect "sources" (origins of input) with "sinks" (destinations where the data interacts with external components, a lower layer such as the OS, etc.)
Potential Mitigations 3
Phase: Implementation
The use of X-Frame-Options allows developers of web content to restrict the usage of their application within the form of overlays, frames, or iFrames. The developer can indicate from which domains can frame the content. The concept of X-Frame-Options is well documented, but implementation of this protection mechanism is in development to cover gaps. There is a need for allowing frames from multiple domains.
Phase: Implementation
A developer can use a "frame-breaker" script in each page that should not be framed. This is very helpful for legacy browsers that do not support X-Frame-Options security feature previously mentioned. It is also important to note that this tactic has been circumvented or bypassed. Improper usage of frames can persist in the web application through nested frames. The "frame-breaking" script does not intuitively account for multiple nested frames that can be presented to the user.
Phase: Implementation
This defense-in-depth technique can be used to prevent the improper usage of frames in web applications. It prioritizes the valid sources of data to be loaded into the application through the usage of declarative policies. Based on which implementation of Content Security Policy is in use, the developer should use the "frame-ancestors" directive or the "frame-src" directive to mitigate this weakness. Both directives allow for the placement of restrictions when it comes to allowing embedded content.
Observed Examples 6
CVE-2017-7440E-mail preview feature in a desktop application allows clickjacking attacks via a crafted e-mail message
CVE-2017-5697Hardware/firmware product has insufficient clickjacking protection in its web user interface
CVE-2017-4015Clickjacking in data-loss prevention product via HTTP response header.
CVE-2016-2496Tapjacking in permission dialog for mobile OS allows access of private storage using a partially-overlapping window.
CVE-2015-1241Tapjacking in web browser related to page navigation and touch/gesture events.
CVE-2017-0492System UI in mobile OS allows a malicious application to create a UI overlay of the entire screen to gain privileges.
References 4
Clickjacking For Shells
Andrew Horton
https://www.exploit-db.com/docs/17881.pdf
ID: REF-35
Clickjacking - OWASP
OWASP
https://owasp.org/www-community/attacks/Clickjacking(2023-04-07)
ID: REF-36
SecTheory
Internet Security
https://www.sectheory.com/clickjacking.htm(2023-04-07)
ID: REF-37
Content Security Policy Level 3
W3C
https://w3c.github.io/webappsec-csp/
ID: REF-38
Applicable Platforms
Technologies:
Web Based : Undetermined
Modes of Introduction
Implementation
Related Attack Patterns
Alternate Terms

Clickjacking

UI Redress Attack

Tapjacking

"Tapjacking" is similar to clickjacking, except it is used for mobile applications in which the user "taps" the application instead of performing a mouse click.
Related Weaknesses
ChildOf: Unintended Proxy or Intermediary ('Confused Deputy') (CWE-441)
ChildOf: Externally Controlled Reference to a Resource in Another Sphere (CWE-610)
ChildOf: User Interface (UI) Misrepresentation of Critical Information (CWE-451)