CWE-1021 詳細

CWE-1021

Improper Restriction of Rendered UI Layers or Frames
2017-11-08
00h00 +00:00
Incomplete
2026-10-28
00h00 +00:00
特定のCWEの通知
特定のCWEの変更情報をいち早くお届けします。
通知を管理する

名前: Improper Restriction of Rendered UI Layers or Frames

The web application does not restrict or incorrectly restricts frame objects or UI layers that belong to another application or domain.

一般情報

導入モード

Implementation

適用可能なプラットフォーム

言語

クラス: Not Language-Specific (Undetermined)

テクノロジー

クラス: Not Technology-Specific (Undetermined)
クラス: Web Based (Undetermined)

一般的な結果

スコープ 影響 可能性
Access ControlGain Privileges or Assume Identity, Bypass Protection Mechanism, Read Application Data, Modify 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 trick the user into changing privacy settings.

観察された例

参考文献 説明

CVE-2017-7440

E-mail preview feature in a desktop application allows clickjacking attacks via a crafted e-mail message

CVE-2017-5697

Hardware/firmware product has insufficient clickjacking protection in its web user interface

CVE-2017-4015

Clickjacking in data-loss prevention product via HTTP response header.

CVE-2016-2496

Tapjacking in permission dialog for mobile OS allows access of private storage using a partially-overlapping window.

CVE-2015-1241

Tapjacking in web browser related to page navigation and touch/gesture events.

CVE-2017-0492

System UI in mobile OS allows a malicious application to create a UI overlay of the entire screen to gain privileges.

潜在的な緩和策

Phases : Implementation
Use the "frame-ancestors" directive in the Content Security Policy, which is intended to define restrictions when it comes to allowing embedded content [REF-1544].
Phases : Implementation
Phases : Implementation
Phases : Implementation
In addition to frames or iframes as previously mentioned, the web application is expected to place restrictions on whether it is allowed to be rendered within objects, embed, or applet elements.

検出方法

Automated Static Analysis

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.)
有効性 : High

脆弱性マッピングノート

理由 : This CWE entry is at the Base level of abstraction, which is a preferred level of abstraction for mapping to the root causes of vulnerabilities.
コメント : Carefully read both the name and description to ensure that this mapping is an appropriate fit. Do not try to 'force' a mapping to a lower-level Base/Variant simply to comply with this preferred level of abstraction.

関連する攻撃パターン

CAPEC ID 攻撃パターン名
CAPEC-103 Clickjacking
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.
CAPEC-181 Flash File Overlay
An attacker creates a transparent overlay using flash in order to intercept user actions for the purpose of performing a clickjacking attack. In this technique, the Flash file provides a transparent overlay over HTML content. Because the Flash application is on top of the content, user actions, such as clicks, are caught by the Flash application rather than the underlying HTML. The action is then interpreted by the overlay to perform the actions the attacker wishes.
CAPEC-222 iFrame Overlay
In an iFrame overlay attack the victim is tricked into unknowingly initiating some action in one system while interacting with the UI from seemingly completely different system.
CAPEC-504 Task Impersonation
An adversary, through a previously installed malicious application, impersonates an expected or routine task in an attempt to steal sensitive information or leverage a user's privileges.
CAPEC-506 Tapjacking
An adversary, through a previously installed malicious application, displays an interface that misleads the user and convinces them to tap on an attacker desired location on the screen. This is often accomplished by overlaying one screen on top of another while giving the appearance of a single interface. There are two main techniques used to accomplish this. The first is to leverage transparent properties that allow taps on the screen to pass through the visible application to an application running in the background. The second is to strategically place a small object (e.g., a button or text field) on top of the visible screen and make it appear to be a part of the underlying application. In both cases, the user is convinced to tap on the screen but does not realize the application that they are interacting with.
CAPEC-587 Cross Frame Scripting (XFS)
This attack pattern combines malicious Javascript and a legitimate webpage loaded into a concealed iframe. The malicious Javascript is then able to interact with a legitimate webpage in a manner that is unknown to the user. This attack usually leverages some element of social engineering in that an attacker must convinces a user to visit a web page that the attacker controls.
CAPEC-654 Credential Prompt Impersonation
An adversary, through a previously installed malicious application, impersonates a credential prompt in an attempt to steal a user's credentials.

参考文献

REF-1491

Clickjacking
Wikipedia.
https://en.wikipedia.org/wiki/Clickjacking

REF-36

Clickjacking - OWASP
OWASP.
https://owasp.org/www-community/attacks/Clickjacking

REF-35

Clickjacking For Shells
Andrew Horton.
https://www.exploit-db.com/docs/17881.pdf

REF-37

SecTheory
Internet Security.
https://www.sectheory.com/clickjacking.htm

REF-38

Content Security Policy Level 3
W3C.
https://w3c.github.io/webappsec-csp/

REF-1544

Content-Security-Policy: frame-ancestors directive
MDN.
https://developer.mozilla.org/en-US/docs/Web/HTTP/Reference/Headers/Content-Security-Policy/frame-ancestors

REF-1545

Missing X-Frame-Options header? You should be using CSP anyway
Zbigniew Banach.
https://www.invicti.com/blog/web-security/missing-x-frame-options-header

REF-1546

Content Security Policy Level 2
W3C.
https://www.w3.org/TR/CSP2/#directive-frame-ancestors

登録情報

名前 組織 日付 リリース日 Version
CWE Content Team MITRE 2017-08-01 +00:00 2017-11-08 +00:00 2.12

変更履歴

名前 組織 日付 コメント
CWE Content Team MITRE 2019-06-20 +00:00 updated Related_Attack_Patterns, Relationships
CWE Content Team MITRE 2020-02-24 +00:00 updated Applicable_Platforms, Relationships
CWE Content Team MITRE 2020-06-25 +00:00 updated Potential_Mitigations
CWE Content Team MITRE 2020-08-20 +00:00 updated Related_Attack_Patterns
CWE Content Team MITRE 2021-10-28 +00:00 updated Relationships
CWE Content Team MITRE 2023-01-31 +00:00 updated Related_Attack_Patterns
CWE Content Team MITRE 2023-04-27 +00:00 updated Detection_Factors, References, Relationships
CWE Content Team MITRE 2023-06-29 +00:00 updated Mapping_Notes
CWE Content Team MITRE 2025-12-11 +00:00 updated Applicable_Platforms, References, Relationships, Weakness_Ordinalities
CWE Content Team MITRE 2026-04-30 +00:00 updated Common_Consequences, Description, Diagram, Potential_Mitigations
CWE Content Team MITRE 2026-10-28 +00:00 updated Potential_Mitigations, References