Roque Lachica Jr via plug on 4 Apr 2020 18:17:17 -0700 |
[Date Prev] [Date Next] [Thread Prev] [Thread Next] [Date Index] [Thread Index]
[PLUG] Fwd: Zoom bombing |
Clarifying the point. Sorry that I wasn't clearOn Apr 3, 2020, at 3:06 PM, George Zipperlen <George.Zipperlen@mail.com> wrote:Zoom hackers not as 133+ as I thought.Not script kiddies exploiting Zoom's privacy backdoors.Just randos finding re-used meeting ids...The last line had little to do with Zoom specific weaknessesMeeting organizers are re-using the same ids for sequences of meetings,and these meeting ids are being sent, and re-sent through insecure channelsI.e. Zoom telephone number style meeting ids posted on public web pages likeMeetUp, or even Twitter and FeceBook...Meetup seems to [now?] have a mechanism to turn posted online meeting URLsinto "This event has passed"The analogy is apt -- telephone numbers, like e-mail addresses need to bekept from pranksters, spammers, scammers, and phishersSo "PLUGCentralApril2020" is better than "PLUGCentral" (kudos!)and "PLUGCentralApril2020" sent to limited "Plug Mailing List" and word-of-mouth is betterthan announced by Goodyear Blimp and emergency text message to all (kudos again)Getting back to Jitsi vs Zoom, this is why Jitsi suggests those "MangoSerenityForLavenderTractors""ColorlessGreenIdeasSleepFuriously" large search space, one time mnemonic ids.Now returning to Zoom's specific weaknesses:Zoom telephone number style ids are a smaller search space, susceptible to both"knowing the number" and "robocall" attacksResidues linger in browser history, cookies, etc. Including URLs that containhashed (or even unhashed) substringsSo we (anyway) sandbox all browser activity, and all of this browser cruft is more-or-lesswell knownClosed source Apps, are even more opaque than obscure and obscured _javascript_,So, depending on your trust level, they require more severe sandboxingThings like Zoom should be freshly downloaded into a temporary sandbox that is deletedafter each use, So one session has no local knowledge of other sessionsHypothesis here: Zoom grabs data and metadata from #all# your meetings...They have global knowledge of all your sessions that share a fingerprint,either actual login account, or shared characterics such as IP, OS type, etc;When this data is stored in some kind of local cache, it is potentially availableto other sessions, not just Zoom.Hackers thus have multiple paths to this data.Don't these people understand that a 'back door' is not necessarily a one way turnstile,and that even a 'secure turnstile' is easier to pass than a brick wall,,,<Three letter agency sourced elliptic curve parameters...>I need to find that sweet spot between too brief, and TL/DR___________________________________________________________________________
Philadelphia Linux Users Group -- http://www.phillylinux.org
Announcements - http://lists.phillylinux.org/mailman/listinfo/plug-announce
General Discussion -- http://lists.phillylinux.org/mailman/listinfo/plug
___________________________________________________________________________ Philadelphia Linux Users Group -- http://www.phillylinux.org Announcements - http://lists.phillylinux.org/mailman/listinfo/plug-announce General Discussion -- http://lists.phillylinux.org/mailman/listinfo/plug