TeamViewer 10.x through 13.x allows remote attackers to bypass the brute-force authentication protection mechanism by skipping the "Cancel" step, which makes it easier to determine the correct value of the default 4-digit PIN. Exploitation requires that an attacker be able to create a new file in the TeamViewer application directory directory permissions restrict that by default. Published: Febru11:15:10 AM -0500Ī DLL side loading vulnerability in the Windows Service in TeamViewer versions up to 22 (fixed in 97), 68 (fixed in 99), 5 (fixed in 6), and (fixed in ) on Windows could allow an attacker to perform code execution on a target system via a service restart where the DLL was previously installed with administrative privileges. 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). If an attacker were to know this key, they could decrypt protect information stored in the registry or configuration files of TeamViewer. 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. This affects teamviewer10, teamviewer8, teamviewerapi, tvchat1, tvcontrol1, tvfiletransfer1, tvjoinv8, tvpresent1, tvsendfile1, tvsqcustomer1, tvsqsupport1, tvvideocall1, and tvvpn1. 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.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |