TeamViewer, as one of the most deployed remote-desktop products, has drawn scrutiny and shipped vulnerabilities in two classes relevant to an attacker. Authentication and permission flaws have allowed connecting or performing actions without the proper authorisation the password model intends. And client-side code-execution issues (including URI-handler and parsing flaws, and privilege issues in the Windows client) have allowed executing code through the application. Both are version-specific, so the approach is to fingerprint the TeamViewer build and match the advisory, giving access or execution independent of session-password strength.
Subtopics#
- TeamViewer auth bypass: connecting or acting without proper authorisation.
- TeamViewer RCE: code execution through the client.