CVE Vulnerabilities

CVE-2020-4547

Improper Restriction of Rendered UI Layers or Frames

Published: Jan 27, 2021 | Modified: Jan 29, 2021
CVSS 3.x
5.4
MEDIUM
Source:
NVD
CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/A:N
CVSS 2.x
3.5 LOW
AV:N/AC:M/Au:S/C:N/I:P/A:N
RedHat/V2
RedHat/V3
Ubuntu

IBM Jazz Foundation products could allow a remote attacker to hijack the clicking action of the victim. By persuading a victim to visit a malicious Web site, a remote attacker could exploit this vulnerability to hijack the victims click actions and possibly launch further attacks against the victim. IBM X-Force ID: 183315.

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
Collaborative_lifecycle_management Ibm 6.0.2 (including) 6.0.2 (including)
Collaborative_lifecycle_management Ibm 6.0.6 (including) 6.0.6 (including)
Collaborative_lifecycle_management Ibm 6.0.6.1 (including) 6.0.6.1 (including)
Engineering_insights Ibm 7.0 (including) 7.0 (including)
Engineering_lifecycle_management Ibm 7.0 (including) 7.0 (including)
Engineering_requirements_management_doors_next Ibm 6.0.2 (including) 6.0.2 (including)
Engineering_requirements_management_doors_next Ibm 6.0.6 (including) 6.0.6 (including)
Engineering_requirements_management_doors_next Ibm 6.0.6.1 (including) 6.0.6.1 (including)
Engineering_requirements_management_doors_next Ibm 7.0 (including) 7.0 (including)
Engineering_test_management Ibm 7.0.0 (including) 7.0.0 (including)
Engineering_workflow_management Ibm 6.0.2 (including) 6.0.2 (including)
Engineering_workflow_management Ibm 6.0.6 (including) 6.0.6 (including)
Engineering_workflow_management Ibm 6.0.6.1 (including) 6.0.6.1 (including)
Engineering_workflow_management Ibm 7.0 (including) 7.0 (including)
Engineering_workflow_management Ibm 7.0.2 (including) 7.0.2 (including)
Global_configuration_management Ibm * *
Rational_engineering_lifecycle_manager Ibm 6.0.2 (including) 6.0.2 (including)
Rational_engineering_lifecycle_manager Ibm 6.0.6 (including) 6.0.6 (including)
Rational_engineering_lifecycle_manager Ibm 6.0.6.1 (including) 6.0.6.1 (including)
Rational_quality_manager Ibm 6.0.2 (including) 6.0.2 (including)
Rational_quality_manager Ibm 6.0.6 (including) 6.0.6 (including)
Rational_quality_manager Ibm 6.0.6.1 (including) 6.0.6.1 (including)
Rhapsody_design_manager Ibm 6.0.2 (including) 6.0.2 (including)
Rhapsody_design_manager Ibm 6.0.6 (including) 6.0.6 (including)
Rhapsody_design_manager Ibm 6.0.6.1 (including) 6.0.6.1 (including)
Rhapsody_design_manager Ibm 7.0 (including) 7.0 (including)
Rhapsody_model_manager Ibm 6.0.2 (including) 6.0.2 (including)
Rhapsody_model_manager Ibm 6.0.6 (including) 6.0.6 (including)
Rhapsody_model_manager Ibm 6.0.6.1 (including) 6.0.6.1 (including)
Rhapsody_model_manager Ibm 7.0 (including) 7.0 (including)

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