Zoom security flaw could let websites turn on your Mac’s webcam without permission

Zoom security flaw could let websites turn on your Mac’s webcam without permission

Zoom security flaw could let websites turn on your Mac’s webcam without permission
Credit: Zoom

A serious zero-day vulnerability has been disclosed in Zoom video conferencing app on the Mac.

Security researcher Jonathan Leitschuh, in a Medium post, detailed the flaw that could let websites hijack your Mac‘s camera and “forcibly” join you to a Zoom call without your permission.

About four million of Zoom’s users are on Mac.

The way the vulnerability works is as follows. Zoom gives users an easy way to dial into video conference calls with the tap of a link — something like https://zoom.us/j/999999999, where ‘999999999’ is a random 9-digit meeting ID that expires once the meeting ends.

This ensures that as long as the Zoom app is running in the background, if you open the meeting link on your browser, it automatically launches the Zoom client on your Mac.

Leitschuh found this functionality was not securely implemented. Not only can a user be auto-joined to a Zoom conference call by merely clicking on the meeting link with the video camera activated, this happens even if you no longer have the Zoom app installed.

It’s because when you install the Zoom app, it also installs a web server locally to accept meeting requests. The troubling part here is that post uninstalling the app, the server still persists and can reinstall Zoom without your intervention.

This effectively means, in order to exploit this vulnerability, all an attacker needs to do is create an invite link through his account on the Zoom website, embed it on a website as a malicious ad, and just lure the target into visiting that website.

The camera, however, can be turned off if you have ticked the option “Turn off my video when joining a meeting.”

Leitschuh originally disclosed the flaw on March 26, 2019, but he mentioned the first actual meeting about how the vulnerability would be patched occurred on June 11, 2019, only 18 days before the end of the 90-day public disclosure deadline.

The timeline in the Medium post shows that Zoom fixed the vulnerability on June 21. But a regression earlier this month caused the bug to resurface again, prompting Zoom to fix the issue yesterday.

“Zoom did end up patching this vulnerability, but all they did was prevent the attacker from turning on the user’s video camera. They did not disable the ability for an attacker to forcibly join to a call anyone visiting a malicious site,” Leitschuh wrote.

The idea that any website you may visit from Mac has the capability to activate your video camera via an unauthorized Zoom call by default is alarming. Zoom has responded that it doesn’t see “video on by default as a security vulnerability,” and that it allows users to set their own video preferences.

Zoom also said it developed the local web server as a workaround to changes that were added in Apple’s Safari browser that prompted Zoom users to confirm if they want to launch the app each time they clicked on a meeting link.

“The local web server automatically accepts the peripheral access on behalf of the user to avoid this extra click before joining a meeting,” the company said.

As a solution, the company — which went public earlier this April — plans to roll out an update this month that will save users’ and administrators’ preferences to turn on/off video when they first join a call.

But users who choose to keep the video option on will continue to be susceptible to malicious third parties as the company isn’t looking to fundamentally change the app’s behavior on Macs.

Instead the onus will be on you to turn your camera off by default.

It’s clear that Zoom has a tough problem on its hands as far as its Mac users are concerned — but it clearly isn’t doing a good job of keeping them safe from unsolicited calls, as bad actors could trick them into clicking links and enabling their video streams.

The company would do well to think of a better way to address this than leaving it up to users to prevent this from happening.