Synopsis
Tenable discovered a flaw in Zoom's thick client that allows attackers to hijack control of presenters’ desktops, spoof chat messages, and kick attendees out of Zoom calls. The flaw is due to the lack of message validation. An attacker can spoof Zoom server messages to invoke restricted functionalities reserved for Zoom servers.
In order to successfully exploit this vulnerability the attacker needs know the IP address of an attendee or a Zoom server IP address. Also, the attacker needs to know the attendees meeting attendee IDs, but they can be trivially brute forced.
Because Zoom seems to accept unencrypted UDP messages even when encrypted sessions are enabled, an attacker can exploit this vulnerability without authentication or knowledge of the encryption key.
A full proof of concept can be found in our GitHub repository. A video of the exploit can be found on our blog.
Solution
- On Windows upgrade to Zoom client 4.1.34814.1119 or later.
- On Mac OS upgrade to Zoom client 4.1.34801.1116 or later.
- On Linux upgrade to Zoom client 2.5.146186.1130 or later.
Additional References
https://support.zoom.us/hc/en-us/sections/201214205-Release-Noteshttps://github.com/tenable/poc/tree/master/Zoom
Disclosure Timeline
All information within TRA advisories is provided “as is”, without warranty of any kind, including the implied warranties of merchantability and fitness for a particular purpose, and with no guarantee of completeness, accuracy, or timeliness. Individuals and organizations are responsible for assessing the impact of any actual or potential security vulnerability.
Tenable takes product security very seriously. If you believe you have found a vulnerability in one of our products, we ask that you please work with us to quickly resolve it in order to protect customers. Tenable believes in responding quickly to such reports, maintaining communication with researchers, and providing a solution in short order.
For more details on submitting vulnerability information, please see our Vulnerability Reporting Guidelines page.
If you have questions or corrections about this advisory, please email [email protected]