An attacker could force a victim to send an NTLM authentication request and either relay the request or capture the hash for offline password cracking.

A malicious website could launch TeamViewer with arbitrary parameters, as demonstrated by a teamviewer10: -play URL. TeamViewer Desktop for Windows before 15.8.3 does not properly quote its custom URI handlers. TeamViewer before 4 on Windows loads untrusted DLLs in certain situations. An attacker can leverage this vulnerability to execute code in the context of the current process. The issue results from the lack of proper validation of user-supplied data, which can result in a read past the end of an allocated structure.

The specific flaw exists within the parsing of TVS files. User interaction is required to exploit this vulnerability in that the target must visit a malicious page or open a malicious file. This vulnerability allows remote attackers to execute arbitrary code on affected installations of TeamViewer. An attacker can leverage this in conjunction with other vulnerabilities to execute arbitrary code in the context of SYSTEM. The issue results from the lack of proper validation of user-supplied data, which can result in a read past the end of an allocated array.

The specific flaw exists within the TeamViewer service. An attacker must first obtain the ability to execute low-privileged code on the target system in order to exploit this vulnerability. This vulnerability allows local attackers to disclose sensitive information on affected installations of TeamViewer. Knowledge of the crash event and the TeamViewer ID as well as either possession of the pre-crash connection password or local authenticated access to the machine would have allowed to establish a remote connection by reusing the not properly deleted connection password. TeamViewer Linux versions before 15.28 do not properly execute a deletion command for the connection password in case of a process crash.

Team viewer version 12