Goal Reached Thanks to every supporter — we hit 100%!

Goal: 1000 CNY · Raised: 1359 CNY

100%

CWE-1021 (不当限制渲染UI层或帧) — Vulnerability Class 130

130 vulnerabilities classified as CWE-1021 (不当限制渲染UI层或帧). AI Chinese analysis included.

CWE-1021 represents a critical web application weakness where the system fails to properly restrict frame objects or user interface layers belonging to external applications or domains. This vulnerability is typically exploited through clickjacking attacks, where malicious actors embed the target application within an invisible or deceptive iframe on a different domain. By tricking users into interacting with hidden UI elements, attackers can perform unauthorized actions, such as transferring funds or changing account settings, without the user’s explicit consent or awareness. To mitigate this risk, developers must implement robust security headers, specifically the Content-Security-Policy (CSP) frame-ancestors directive, which explicitly defines which origins are permitted to embed the application. Additionally, setting the X-Frame-Options header to DENY or SAMEORIGIN provides an effective defense by preventing the browser from rendering the page within any frame unless it originates from the same domain, thereby neutralizing the attack vector.

MITRE CWE Description
The web application does not restrict or incorrectly restricts frame objects or UI layers that belong to another application or domain.
Common Consequences (1)
Access Control Gain 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…
Mitigations (4)
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 multip…
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 no…
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 weakne…
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.

Vulnerabilities classified as CWE-1021 (不当限制渲染UI层或帧) represent 130 CVEs. The CWE taxonomy describes the weakness; review individual CVEs for product-specific impact.