问题原文
原帖链接 · 200_success · CC BY-SA 3.0
In light of mounting allegations that TeamViewer has been hacked, and that criminals are somehow gaining unauthorized access to TeamView-enabled workstations, we would like to block TeamViewer altogether.
How doe the TeamViewer session-establishment protocol work? What firewall rules or other measures can we use to prevent all workstations within our network from being controlled through TeamViewer?
We have a heterogeneous environment; controls would have to be done at the network level, and not through anything like a Group Policy.
已采纳解答
原帖链接 · Esa Jokinen · CC BY-SA 3.0
Just for completeness, TeamViewer uses three different ports in specific order.
- TCP/UDP port
5938is the primary port TeamViewer prefers to use. This is also currently the only port used by Android, Windows Mobile and BlackBerry clients. - If connection fails, TeamViewer tries TCP
443next. This is actually the most problematic part, because blocking the default HTTPS port443will block all secure web sites. Tampering with the data would involve using fake root CA and decrypting the data, and without that it's really hard to detect whether it's TeamViewer traffic or just normal TLS encrypted HTTPS. - Default HTTP port, TCP
80is the third alternative. That would be easy to block e.g. by using a transparent proxy, but is totally unnecessary, because the443is used before this.
Therefore, blocking the connections on network level from any client (incl. BYOD) would involve:
Faking or blocking DNS queries for
*.teamviewer.com. This should actually be the most efficient way, if you trust the TeamViewer GmbH's word (for the opposite purposes):The TeamViewer software makes connections to our master servers located around the world. These servers use a number of different IP address ranges, which are also frequently changing. As such, we are unable to provide a list of our server IPs. However, all of our IP addresses have PTR records that resolve to
*.teamviewer.com. You can use this to restrict the destination IP addresses that you allow through your firewall or proxy server.Additionally, blocking TeamViewer's known IP address ranges, but as we can soon see, this may be problematic and hard to maintain:
178.77.120.0/25;DE-HE-MASTER-EXT; TeamViewer GmbH159.8.209.208/28;NETBLK-SOFTLAYER-RIPE-CUST-SS30641-RIPE; TeamViewer GmbH- Some in
92.51.156.64/26; owned by Host Europe GmbH; risk for false positives... - etc.; also risk for false positives and need for removals in the future.
- In addition, very paranoid administrators could utilize some Deep Packet Inspection.
If you don't trust TeamViewer GmbH, and as TeamViewer works on ports 443 and 80 with a standalone TeamViewerQS.exe, the Group Policy (e.g. Software Restriction Policies) would be a good addition that increases protection on Windows machines joined to an AD domain.
摘自公开归档,保留原文语言,版式经整理,外部媒体与邮箱地址已移除。
