ID CVE-2017-11290
Summary An issue was discovered in Adobe Connect 9.6.2 and earlier versions. A UI Redress (or Clickjacking) vulnerability exists. This issue has been resolved by adding a feature that enables Connect administrators to protect users from UI redressing (or clickjacking) attacks.
References
Vulnerable Configurations
  • cpe:2.3:a:adobe:connect:1.0.0.1:*:*:*:*:*:*:*
    cpe:2.3:a:adobe:connect:1.0.0.1:*:*:*:*:*:*:*
  • cpe:2.3:a:adobe:connect:6.0:*:*:*:*:*:*:*
    cpe:2.3:a:adobe:connect:6.0:*:*:*:*:*:*:*
  • cpe:2.3:a:adobe:connect:6.1:*:*:*:*:*:*:*
    cpe:2.3:a:adobe:connect:6.1:*:*:*:*:*:*:*
  • cpe:2.3:a:adobe:connect:6.2:*:*:*:*:*:*:*
    cpe:2.3:a:adobe:connect:6.2:*:*:*:*:*:*:*
  • cpe:2.3:a:adobe:connect:6.3:*:*:*:*:*:*:*
    cpe:2.3:a:adobe:connect:6.3:*:*:*:*:*:*:*
  • cpe:2.3:a:adobe:connect:7.0:*:*:*:*:*:*:*
    cpe:2.3:a:adobe:connect:7.0:*:*:*:*:*:*:*
  • cpe:2.3:a:adobe:connect:7.2:*:*:*:*:*:*:*
    cpe:2.3:a:adobe:connect:7.2:*:*:*:*:*:*:*
  • cpe:2.3:a:adobe:connect:7.3:*:*:*:*:*:*:*
    cpe:2.3:a:adobe:connect:7.3:*:*:*:*:*:*:*
  • cpe:2.3:a:adobe:connect:7.5:*:*:*:*:*:*:*
    cpe:2.3:a:adobe:connect:7.5:*:*:*:*:*:*:*
  • cpe:2.3:a:adobe:connect:8.0:*:*:*:*:*:*:*
    cpe:2.3:a:adobe:connect:8.0:*:*:*:*:*:*:*
  • cpe:2.3:a:adobe:connect:8.1:*:*:*:*:*:*:*
    cpe:2.3:a:adobe:connect:8.1:*:*:*:*:*:*:*
  • cpe:2.3:a:adobe:connect:8.2:*:*:*:*:*:*:*
    cpe:2.3:a:adobe:connect:8.2:*:*:*:*:*:*:*
  • cpe:2.3:a:adobe:connect:8.2.1:*:*:*:*:*:*:*
    cpe:2.3:a:adobe:connect:8.2.1:*:*:*:*:*:*:*
  • cpe:2.3:a:adobe:connect:8.2.2:*:*:*:*:*:*:*
    cpe:2.3:a:adobe:connect:8.2.2:*:*:*:*:*:*:*
  • cpe:2.3:a:adobe:connect:9.0:*:*:*:*:*:*:*
    cpe:2.3:a:adobe:connect:9.0:*:*:*:*:*:*:*
  • cpe:2.3:a:adobe:connect:9.0.2:*:*:*:*:*:*:*
    cpe:2.3:a:adobe:connect:9.0.2:*:*:*:*:*:*:*
  • cpe:2.3:a:adobe:connect:9.0.3:*:*:*:*:*:*:*
    cpe:2.3:a:adobe:connect:9.0.3:*:*:*:*:*:*:*
  • cpe:2.3:a:adobe:connect:9.1:*:*:*:*:*:*:*
    cpe:2.3:a:adobe:connect:9.1:*:*:*:*:*:*:*
  • cpe:2.3:a:adobe:connect:9.1.2:*:*:*:*:*:*:*
    cpe:2.3:a:adobe:connect:9.1.2:*:*:*:*:*:*:*
  • cpe:2.3:a:adobe:connect:9.2:*:*:*:*:*:*:*
    cpe:2.3:a:adobe:connect:9.2:*:*:*:*:*:*:*
  • cpe:2.3:a:adobe:connect:9.3:*:*:*:*:*:*:*
    cpe:2.3:a:adobe:connect:9.3:*:*:*:*:*:*:*
  • cpe:2.3:a:adobe:connect:9.4.1:*:*:*:*:*:*:*
    cpe:2.3:a:adobe:connect:9.4.1:*:*:*:*:*:*:*
  • cpe:2.3:a:adobe:connect:9.4.2:*:*:*:*:*:*:*
    cpe:2.3:a:adobe:connect:9.4.2:*:*:*:*:*:*:*
  • cpe:2.3:a:adobe:connect:9.5:*:*:*:*:*:*:*
    cpe:2.3:a:adobe:connect:9.5:*:*:*:*:*:*:*
  • cpe:2.3:a:adobe:connect:9.5.2:*:*:*:*:*:*:*
    cpe:2.3:a:adobe:connect:9.5.2:*:*:*:*:*:*:*
  • cpe:2.3:a:adobe:connect:9.5.3:*:*:*:*:*:*:*
    cpe:2.3:a:adobe:connect:9.5.3:*:*:*:*:*:*:*
  • cpe:2.3:a:adobe:connect:9.5.4:*:*:*:*:*:*:*
    cpe:2.3:a:adobe:connect:9.5.4:*:*:*:*:*:*:*
  • cpe:2.3:a:adobe:connect:9.5.5:*:*:*:*:*:*:*
    cpe:2.3:a:adobe:connect:9.5.5:*:*:*:*:*:*:*
  • cpe:2.3:a:adobe:connect:9.5.6:*:*:*:*:*:*:*
    cpe:2.3:a:adobe:connect:9.5.6:*:*:*:*:*:*:*
  • cpe:2.3:a:adobe:connect:9.5.7:*:*:*:*:*:*:*
    cpe:2.3:a:adobe:connect:9.5.7:*:*:*:*:*:*:*
  • cpe:2.3:a:adobe:connect:9.6:*:*:*:*:*:*:*
    cpe:2.3:a:adobe:connect:9.6:*:*:*:*:*:*:*
  • cpe:2.3:a:adobe:connect:9.6.1:*:*:*:*:*:*:*
    cpe:2.3:a:adobe:connect:9.6.1:*:*:*:*:*:*:*
  • cpe:2.3:a:adobe:connect:9.6.2:*:*:*:*:*:*:*
    cpe:2.3:a:adobe:connect:9.6.2:*:*:*:*:*:*:*
CVSS
Base: 4.3 (as of 03-10-2019 - 00:03)
Impact:
Exploitability:
CWE CWE-1021
CAPEC
  • iFrame Overlay
    In an iFrame overlay attack the victim is tricked into unknowingly initiating some action in one system while interacting with the UI from seemingly completely different system. While being logged in to some target system, the victim visits the attackers' malicious site which displays a UI that the victim wishes to interact with. In reality, the iFrame overlay page has a transparent layer above the visible UI with action controls that the attacker wishes the victim to execute. The victim clicks on buttons or other UI elements they see on the page which actually triggers the action controls in the transparent overlaying layer. Depending on what that action control is, the attacker may have just tricked the victim into executing some potentially privileged (and most undesired) functionality in the target system to which the victim is authenticated. The basic problem here is that there is a dichotomy between what the victim thinks he or she is clicking on versus what he or she is actually clicking on.
  • Task Impersonation
    An adversary, through a previously installed malicious application, monitors the task list maintained by the operating system and waits for a specific legitimate task to become active. Once the task is detected, the malicious application launches a new task in the foreground that mimics the user interface of the legitimate task. At this point, the user thinks that they are interacting with the legitimate task that they started, but instead they are interacting with the malicious application. This type of attack is most often used to obtain sensitive information (e.g., credentials) from the user. Once the adversary's goal is reached, the malicious application can exit, leaving the original trusted application visible and the appearance that nothing out of the ordinary has occurred.
  • Flash File Overlay
    An attacker creates a transparent overlay using flash in order to intercept user actions for the purpose of performing a clickjacking attack. In this technique, the Flash file provides a transparent overlay over HTML content. Because the Flash application is on top of the content, user actions, such as clicks, are caught by the Flash application rather than the underlying HTML. The action is then interpreted by the overlay to perform the actions the attacker wishes.
  • Tapjacking
    An adversary, through a previously installed malicious application, displays an interface that misleads the user and convinces him/her to tap on an attacker desired location on the screen. This is often accomplished by overlaying one screen on top of another while giving the appearance of a single interface. There are two main techniques used to accomplish this. The first is to leverage transparent properties that allow taps on the screen to pass through the visible application to an application running in the background. The second is to strategically place a small object (e.g., a button or text field) on top of the visible screen and make it appear to be a part of the underlying application. In both cases, the user is convinced to tap on the screen but does not realize the application that they are interacting with.
  • Clickjacking
    In a clickjacking attack the victim is tricked into unknowingly initiating some action in one system while interacting with the UI from a seemingly completely different system. While being logged in to some target system, the victim visits the adversary's malicious site which displays a UI that the victim wishes to interact with. In reality, the clickjacked page has a transparent layer above the visible UI with action controls that the adversary wishes the victim to execute. The victim clicks on buttons or other UI elements they see on the page which actually triggers the action controls in the transparent overlaying layer. Depending on what that action control is, the adversary may have just tricked the victim into executing some potentially privileged (and most certainly undesired) functionality in the target system to which the victim is authenticated. The basic problem here is that there is a dichotomy between what the victim thinks they are clicking on versus what they are actually clicking on.
Access
VectorComplexityAuthentication
NETWORK MEDIUM NONE
Impact
ConfidentialityIntegrityAvailability
NONE PARTIAL NONE
cvss-vector via4 AV:N/AC:M/Au:N/C:N/I:P/A:N
refmap via4
bid 101838
confirm https://helpx.adobe.com/security/products/connect/apsb17-35.html
sectrack 1039799
Last major update 03-10-2019 - 00:03
Published 09-12-2017 - 06:29
Last modified 03-10-2019 - 00:03
Back to Top