A Comunidade TeamViewer chega ao Brasil 🎉
Check out our brand-new Portuguese Community 👉 here 👈.
Update now to the most recent TeamViewer version 15.22. See the Change Logs here.
Operating system: Windows
Release date: 2021-08-24
- It's now possible to suppress sending chat messages to a device. This can be achieved by activating the setting for "Disable chat" in the options or via the registry (DisableChat). If disabling chat is activated, the chat tab is no longer visible.
- It is now possible to keep TeamViewer MSI installations up-to-date using automatic updates.
- It is now possible to inherit TeamViewer policies to managed devices via managed groups.
- A new way to display video in meetings is now available: Smart focus, which focuses on your face for better privacy control of your surroundings and more focused meetings!
- Updated UI on media and list view in Meeting, for improved user experience.
- Fixed a bug that would cause the app not to reconnect if the internet connection was lost during a running meeting.
- Fixed a bug in the UI which prevented displaying the "What's New" window.
- CVE-2021-34858: Installations with existing TV recording files (TVS) were vulnerable to a problem in file parsing that could have allowed someone to execute arbitrary code and could have caused the binary to crash. User interaction as well as a third-party vulnerability would have been required for remote exploitation. We don’t have any indication of exploitation in the wild. Our thanks go to Kdot and the Trend Micro Zero Day Initiative for the responsible disclosure.
- CVE-2021-34859: In some circumstances, a problem in shared memory management could have caused the TeamViewer service to perform an out-of-bounds read. Access to the machine would have been required for exploitation. We don’t have any indication of exploitation in the wild. Our thanks go to Mat Powell and the Trend Micro Zero Day Initiative for the responsible disclosure.
- TeamViewer is installed by default in the protected Program Files directory. If a user intentionally had chosen to install it in a different location, someone would have been able to leverage a privilege escalation problem. Access to the machine would have been required for exploitation. We don’t have any indication of exploitation in the wild. Our thanks go to Maciej Miszczyk for the responsible disclosure.