While in most cases an attacker requires an existing session on a system, if the registry/configuration keys were stored off of the machine (such as in a file share or online), an attacker could then decrypt the required password to login to the system.
The latest version still uses the same key for OptionPasswordAES but appears to have changed how the Unattended Access password is stored. With versions before v9.x, this allowed for attackers to decrypt the Unattended Access password to the system (which allows for remote login to the system as well as headless file browsing). Complete desktop is transferred over network, while locally computer is locked. When user connect with Remote Desktop, locally computer is locked. I'm asking for the way to do Login function like Remote Desktop does. If an attacker were to know this key, they could decrypt protect information stored in the registry or configuration files of TeamViewer. Screen Capturing is done with Desktop Duplication Api. It used a shared AES key for all installations since at least as far back as v8, and used it for at least OptionsPasswordAES in the current version of the product. TeamViewer Desktop through allows a bypass of remote-login access control because the same key is used for different customers' installations.
0 kommentar(er)
