CVE Vulnerabilities


Improper Restriction of Rendered UI Layers or Frames

Published: Feb 13, 2020 | Modified: Feb 19, 2020
CVSS 3.x
CVSS 2.x

It is possible for a malicious application to construct a TYPE_TOAST window manually and make that window clickable. This could lead to a local escalation of privilege with no additional execution privileges needed. User action is needed for exploitation.Product: AndroidVersions: Android-8.0 Android-8.1 Android-9 Android-10Android ID: A-128674520


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.

Affected Software

Name Vendor Start Version End Version
Android Google 8.0 8.0
Android Google 8.1 8.1
Android Google 9.0 9.0
Android Google 10.0 10.0

Potential Mitigations

  • 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.
  • 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.