TeamViewer Desktop through 14.7.1965 allows a bypass of remote-login access control because the same key is used for different customers' installations. It used a shared AES key for all installations since at least as far back as v7.0.43148, and used it for at least OptionsPasswordAES in the current version of the product. If an attacker were to know this key, they could decrypt protect information stored in the registry or configuration files of TeamViewer. 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). The latest version still uses the same key for OptionPasswordAES but appears to have changed how the Unattended Access password is stored. 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 product does not require that users should have strong passwords, which makes it easier for attackers to compromise user accounts.
| Link | Tags |
|---|---|
| https://community.teamviewer.com/t5/Knowledge-Base/tkb-p/Knowledgebase?threadtype=label&labels=Security | vendor advisory broken link |
| https://whynotsecurity.com/blog/teamviewer/ | third party advisory exploit |
| https://twitter.com/Blurbdust/status/1224212682594770946?s=20 | third party advisory |
| https://community.teamviewer.com/t5/Announcements/Specification-on-CVE-2019-18988/td-p/82264 | vendor advisory |