Zoom Security Update

Zoom has been getting a lot of attention from the media and the criminal elements of the Internet due to its sudden, massive surge in popularity–10 million users to 200+ million users. There is not a popular application or operating system out there that has not had its share of major incidents. For example, Microsoft releases security patches at least once every month. Most of the time Microsoft is fixing vulnerabilities that can be used to hijack a computer system. Google regularly issues patches for Google Chrome that fix vulnerabilities that could allow a malicious website to execute code on the computer. Sometimes we get multiple patches a week from Google. Likewise, the same happens to Mozilla Firefox.

Hopefully I am not scaring you away from your computer, but I want to make sure our look at Zoom is taken in context. Where were the news articles about Windows, Chrome, and Firefox? They have a much larger user base than Zoom. Yet these security issues have become so routine, they often only get noticed by IT people like myself that are actively watching for security alerts.

Further, many of the articles we are seeing are from Zoom users doing unwise things that are completely out of the control of Zoom. A recent article I saw was about Zoom users uploading recordings of their Zoom meeting online for everyone on the Internet to see. There is nothing Zoom can do to stop people from uploading files to the Internet so that anyone can see them–these same people probably upload all sorts of files with improper permissions. Another article covered a user that disabled passwords on their Zoom meetings to make it easier for their participants to join–it also makes it easy for the bad guys to join. Most of the Zoombombing incidents have been caused by the host or participants accidentally (or in some cases intentionally) sharing the meeting ID and password publicly for anyone to find. Sometimes this happens because they have set their calendars to be publicly accessible. A lot of this reporting is sensationalism just to get clicks and advertising revenue in a time when web news sites are actually under enormous financial pressure. Most advertisers have been cutting back altogether or rejecting advertising on articles that mention keywords related to the pandemic. This has driven the pay per click/view in advertising way, way down.

However, there is also legitimate criticism of Zoom that has been reported.

  1. Zoom claimed they used AES 256 encryption but in some instances AES 128 would be used. AES 256 is used for Top Secret communications by the government, UNI and most of the Internet actually uses AES 128 for most encryption needs. If Zoom had said they used AES 128 or just simply said AES, it would have been fine. Shortly after discovery, Zoom migrated fully to AES 256.
  2. Zoom claimed to use end-to-end encryption. The traditional tech meaning of end-to-end has been that communications are encrypted by one user and are not decrypted until they get to the other user, so no points in the middle could see unencrypted data. That technique actually does not work well in a large video meeting where the same information needs to be broadcast to multiple users. So they actually encrypt from the client to the server, decrypt there, then encrypt again when the data is sent back to the other clients in the meeting.  The actual video and audio data is encrypted with a shared encryption key used by all users on the same call. This admittedly is a poor implementation of encryption, but it is an efficient way to communicate while still enabling some privacy. WebEx, a competitor to Zoom, does have true end-to-end encryption as an option, but when it is used many features of the software get disabled–so most meetings in WebEx are not end-to-end encrypted either. When pointed out to Zoom, they admitted they were not using the same definition for end-to-end encryption as most tech companies now use. Zoom has announced plans to improve the quality of encryption used in Zoom.
  3. Zoom's lawyers wrote an overly-broad privacy policy to allow them maximum flexibility so nobody could claim they violated the policy. This is a technique I have seen plenty of other Internet companies use and a reasonable legal strategy. With increased scrutiny, they got called out for it and then changed it.
  4. Zoom used an off-the-shelf software development kit (SDK) for mobile apps designed by Facebook to allow Zoom users to use Facebook as their authentication credentials. When the SDK was used, it also sent limited analytics data about the mobile device back to Facebook. Such analytics sharing is very, very common in mobile apps and all over the Internet, but it must be disclosed if you dig into the privacy policies and documentation. When discovered, Zoom removed the SDK and integrated Facebook authentication in a different manner.
  5. Zoom used a workaround on the Mac versions to allow the software to install and run without requiring the user to approve access to the webcam and microphone as Mac OS normally requires now. This was done to make the software easier to use, but legitimate software using such a technique is a major faux pas and opened up the system to other apps being able to gain the same access. This "feature" was removed back in July of 2019.
  6. Zoom had an issue where malicious links sent via chat could cause a user’s computer username and password to be sent to a remote server if the link was clicked. This is as much a flaw in Windows as it is in Zoom. All Zoom did in that instance was pass a server link sent via its chat feature to Windows for processing and Windows decided in its wisdom to send the username and password for the computer to the remote server listed in the link–but this would only happen if the user clicked the link. This issue has since been patched by Zoom.

Now, all of the above criticisms of Zoom are valid. However, I have seen plenty of other software programs and websites make the exact same or similar mistakes. Here are a couple examples, but this list could be endless.

  1. Microsoft added intensive analytics and data gathering to Windows 10 and then back-ported the analytics to their older versions of Windows in an automatic update without adequate disclosure to the users.
  2. The privacy policy for a common grammar and spell check plug-in for web browsers and Microsoft Office allows them unlimited access and permission to all data the user types–even things started to be typed and then deleted before submitting. They claim they do not access this information regularly, but grant themselves the permission to do so in an unlimited fashion and to make commercial use of the data the users provide.

Again, I am not saying that Zoom did no wrong, just that it is entirely typical in how the modern tech community regularly sidelines the privacy and security of users in the name of innovation. We are aware of what Zoom really is doing and view it as no more risky than any other communications and educational platform we regularly use.

As for what you should do to protect yourself when using Zoom, the same advice for Zoom also applies to email, web links, etc. Do not click on links unless you absolutely trust the person that sent it. Likewise, only accept file transfers within Zoom from users you absolutely trust. Whenever possible, do not disable the security features UNI has set as defaults for Zoom. If problems with participants are anticipated, contact the IT Service Desk for advice on configuring Zoom to minimize possible disruptions. Like any other application, Zoom should be updated when security updates come out. Zoom has been quick to patch as issues have been identified.

Likewise, you should keep your operating system, browsers, and other software up-to-date. Many attacks actually use multiple vulnerabilities strung together.  Further, you should be vigilant when using the computer. Watch out for things that just do not make sense. Many attacks still require user participation in some fashion–approving an application to run, manually starting an application that was downloaded, allowing a program administrative rights, downloading a suspicious attachment, etc. Be skeptical of anything that seems out of the ordinary. Certainly never trust pop-ups and websites that claim your computer is "infected" or that direct you to call a number to have your computer fixed. Please watch out for phishing attacks, see our website at https://it.uni.edu/phishing for more details about them.

The last thing I will point out is to keep a perspective on other technologies we use all the time and compare their security to that of Zoom. For example, most people do not hesitate to use email, but depending on who you send your email to or how it is routed over the Internet, it is completely possible for it to travel entirely unencrypted over the public Internet. Even if it is encrypted, each mail server along the path will have access to the decrypted contents. Yet we use email all the time for private conversations, online password resets, etc. Social network sites are gathering all types of data from all over the Internet. Google is gathering data from most websites, from its search, from email, and even partnering with credit card companies to link purchases to people to deliver targeted advertising. Many phone conversations, but not all, are routed over the public Internet with minimal security. Yet most of us use these technologies all the time. As such, we should all be more aware of the risks our data and information are subject to all the time, and be vigilant about protecting information we would prefer to be kept private.

I do not have any concerns using Zoom and see it as a perfectly acceptable technology to use in higher education, but I am aware of its limitations. There is always a trade-off between usability and security that must be balanced. In fact, for home users Zoom recently changed that balance towards more secure defaults to protect their novice users. Like any technology, some responsibility lies on the users to properly use the software. That said, I certainly would never use Zoom as the British government did for a cabinet meeting–there the security implications are significant enough to warrant end-to-end encryption with unique login credentials for each user. But admittedly, that would have been much more difficult to set up on short notice.

Let IT-Information Security know if you have any further questions or concerns. We will be happy to address them. We can be reached at security@uni.edu. Also, I will fully admit there is room for debate about when a tech company actually "crosses-the-line." Many of us would draw the line in different spots, so there is room for healthy debate in my assessment.

Eric Lukens, IT-Information Security

  • ITTC 36
  • (319) 273-5555
  • Service Hub