CVE Vulnerabilities

CVE-2020-1728

Improper Restriction of Rendered UI Layers or Frames

Published: Apr 06, 2020 | Modified: Nov 07, 2023
CVSS 3.x
5.4
MEDIUM
Source:
NVD
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:L/I:L/A:N
CVSS 2.x
5.8 MEDIUM
AV:N/AC:M/Au:N/C:P/I:P/A:N
RedHat/V2
RedHat/V3
4.8 LOW
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:L/A:N
Ubuntu

A vulnerability was found in all versions of Keycloak where, the pages on the Admin Console area of the application are completely missing general HTTP security headers in HTTP-responses. This does not directly lead to a security issue, yet it might aid attackers in their efforts to exploit other problems. The flaws unnecessarily make the servers more prone to Clickjacking, channel downgrade attacks and other similar client-based attack vectors.

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

Name Vendor Start Version End Version
Keycloak Redhat * 10.0.0 (excluding)
Red Hat build of Quarkus 1.7.5 RedHat keycloak *
Red Hat Runtimes Spring Boot 2.2.10 RedHat keycloak *
Red Hat Single Sign-On 7.4.2 RedHat keycloak *
Red Hat Single Sign-On 7.4 for RHEL 6 RedHat rh-sso7-keycloak-0:9.0.5-1.redhat_00001.1.el6sso *
Red Hat Single Sign-On 7.4 for RHEL 7 RedHat rh-sso7-keycloak-0:9.0.5-1.redhat_00001.1.el7sso *
Red Hat Single Sign-On 7.4 for RHEL 8 RedHat rh-sso7-keycloak-0:9.0.5-1.redhat_00001.1.el8sso *
Text-Only RHOAR RedHat *

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