CVE Vulnerabilities

CVE-2022-32919

Improper Restriction of Rendered UI Layers or Frames

Published: Jan 10, 2024 | Modified: Jun 17, 2025
CVSS 3.x
4.7
MEDIUM
Source:
NVD
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:N/I:L/A:N
CVSS 2.x
RedHat/V2
RedHat/V3
4.7 MODERATE
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:N/I:L/A:N
Ubuntu
MEDIUM
root.io logo minimus.io logo echo.ai logo

The issue was addressed with improved UI handling. This issue is fixed in iOS 16.2 and iPadOS 16.2, macOS Ventura 13.1. Visiting a website that frames malicious content may lead to UI spoofing.

Weakness

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

NameVendorStart VersionEnd Version
IpadosApple*16.2 (excluding)
Iphone_osApple*16.2 (excluding)
MacosApple*13.1 (excluding)
Red Hat Enterprise Linux 7 Extended Lifecycle SupportRedHatwebkitgtk4-0:2.48.3-2.el7_9*
Red Hat Enterprise Linux 8RedHatwebkit2gtk3-0:2.40.5-1.el8*
Red Hat Enterprise Linux 9RedHatwebkit2gtk3-0:2.40.5-1.el9*
Qtwebkit-opensource-srcUbuntubionic*
Qtwebkit-opensource-srcUbuntudevel*
Qtwebkit-opensource-srcUbuntuesm-apps/bionic*
Qtwebkit-opensource-srcUbuntuesm-apps/focal*
Qtwebkit-opensource-srcUbuntuesm-apps/jammy*
Qtwebkit-opensource-srcUbuntuesm-apps/noble*
Qtwebkit-opensource-srcUbuntuesm-infra/xenial*
Qtwebkit-opensource-srcUbuntufocal*
Qtwebkit-opensource-srcUbuntujammy*
Qtwebkit-opensource-srcUbuntulunar*
Qtwebkit-opensource-srcUbuntumantic*
Qtwebkit-opensource-srcUbuntunoble*
Qtwebkit-opensource-srcUbuntutrusty*
Qtwebkit-opensource-srcUbuntuupstream*
Qtwebkit-opensource-srcUbuntuxenial*
Qtwebkit-sourceUbuntubionic*
Qtwebkit-sourceUbuntuesm-apps/bionic*
Qtwebkit-sourceUbuntuesm-apps/xenial*
Qtwebkit-sourceUbuntutrusty*
Qtwebkit-sourceUbuntuxenial*
Webkit2gtkUbuntubionic*
Webkit2gtkUbuntudevel*
Webkit2gtkUbuntuesm-infra/bionic*
Webkit2gtkUbuntuesm-infra/focal*
Webkit2gtkUbuntuesm-infra/xenial*
Webkit2gtkUbuntufocal*
Webkit2gtkUbuntujammy*
Webkit2gtkUbuntulunar*
Webkit2gtkUbuntumantic*
Webkit2gtkUbuntunoble*
Webkit2gtkUbuntuupstream*
Webkit2gtkUbuntuxenial*
WebkitgtkUbuntubionic*
WebkitgtkUbuntuesm-apps/bionic*
WebkitgtkUbuntuesm-apps/xenial*
WebkitgtkUbuntutrusty*
WebkitgtkUbuntuxenial*
WpewebkitUbuntubionic*
WpewebkitUbuntuesm-apps/focal*
WpewebkitUbuntuesm-apps/jammy*
WpewebkitUbuntufocal*
WpewebkitUbuntujammy*
WpewebkitUbuntutrusty*
WpewebkitUbuntuupstream*
WpewebkitUbuntuxenial*

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.

References