<html xmlns:v="urn:schemas-microsoft-com:vml" xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns="http://www.w3.org/TR/REC-html40"><head><meta http-equiv=Content-Type content="text/html; charset=utf-8"><meta name=Generator content="Microsoft Word 15 (filtered medium)"><style><!--
/* Font Definitions */
@font-face
{font-family:"Cambria Math";
panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
margin-bottom:.0001pt;
font-size:11.0pt;
font-family:"Calibri",sans-serif;}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:blue;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:purple;
text-decoration:underline;}
p.msonormal0, li.msonormal0, div.msonormal0
{mso-style-name:msonormal;
mso-margin-top-alt:auto;
margin-right:0in;
mso-margin-bottom-alt:auto;
margin-left:0in;
font-size:11.0pt;
font-family:"Calibri",sans-serif;}
span.EmailStyle18
{mso-style-type:personal;
font-family:"Calibri",sans-serif;
color:windowtext;}
span.EmailStyle20
{mso-style-type:personal-reply;
font-family:"Calibri",sans-serif;
color:windowtext;}
.MsoChpDefault
{mso-style-type:export-only;
font-size:10.0pt;}
@page WordSection1
{size:8.5in 11.0in;
margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]--></head><body lang=EN-US link=blue vlink=purple><div class=WordSection1><p class=MsoNormal>This is assuredly right. The change from Adobe to Zoom may, or may not, have been right for ICANN and for this group for any number of reasons ranging from cost, to security, to scalability and utility. But let’s not romanticize Adobe. They are not a terribly secure platform generically. As James said, the Zoom response is poor – but we can’t hang that around the neck of ICANN org. <o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>P<o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><div><p class=MsoNormal>Paul Rosenzweig<o:p></o:p></p><p class=MsoNormal><a href="mailto:paul.rosenzweig@redbranchconsulting.com"><span style='color:#0563C1'>paul.rosenzweig@redbranchconsulting.com</span></a><o:p></o:p></p><p class=MsoNormal>O: +1 (202) 547-0660<o:p></o:p></p><p class=MsoNormal>M: +1 (202) 329-9650<o:p></o:p></p><p class=MsoNormal>VOIP: +1 (202) 738-1739<o:p></o:p></p><p class=MsoNormal><a href="http://www.redbranchconsulting.com/"><span style='color:#0563C1'>www.redbranchconsulting.com</span></a><o:p></o:p></p><p class=MsoNormal>My PGP Key: <a href="https://keys.mailvelope.com/pks/lookup?op=get&search=0x9A830097CA066684"><span style='color:#0563C1'>https://keys.mailvelope.com/pks/lookup?op=get&search=0x9A830097CA066684</span></a><o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p></div><p class=MsoNormal><o:p> </o:p></p><div><div style='border:none;border-top:solid #E1E1E1 1.0pt;padding:3.0pt 0in 0in 0in'><p class=MsoNormal><b>From:</b> NCSG-Discuss <NCSG-DISCUSS@LISTSERV.SYR.EDU> <b>On Behalf Of </b>James Gannon<br><b>Sent:</b> Wednesday, July 10, 2019 12:52 AM<br><b>To:</b> NCSG-DISCUSS@LISTSERV.SYR.EDU<br><b>Subject:</b> Re: Zoom Structural Vulnerability Discovered<o:p></o:p></p></div></div><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>Just want to call out that Adobe has likely the worst reputation in the entire tech industry when it comes to security, I really would not hold them out as either prompt or without serious issues (I believe they still hold the record for number of CVSS 9+ vulns).<o:p></o:p></p><p class=MsoNormal>Zooms response is poor I agree, but on a data driven comparison it is a far more secure platform.<o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><div style='border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0in 0in 0in'><p class=MsoNormal><b><span style='font-size:12.0pt;color:black'>From: </span></b><span style='font-size:12.0pt;color:black'>NCSG-Discuss <<a href="mailto:NCSG-DISCUSS@LISTSERV.SYR.EDU">NCSG-DISCUSS@LISTSERV.SYR.EDU</a>> on behalf of Ayden Férdeline <<a href="mailto:icann@FERDELINE.COM">icann@FERDELINE.COM</a>><br><b>Reply-To: </b>Ayden Férdeline <<a href="mailto:icann@FERDELINE.COM">icann@FERDELINE.COM</a>><br><b>Date: </b>Tuesday, 9 July 2019 at 14:13<br><b>To: </b>"<a href="mailto:NCSG-DISCUSS@LISTSERV.SYR.EDU">NCSG-DISCUSS@LISTSERV.SYR.EDU</a>" <<a href="mailto:NCSG-DISCUSS@LISTSERV.SYR.EDU">NCSG-DISCUSS@LISTSERV.SYR.EDU</a>><br><b>Subject: </b>Re: Zoom Structural Vulnerability Discovered<o:p></o:p></span></p></div><div><p class=MsoNormal><o:p> </o:p></p></div><div><p class=MsoNormal>That is true, but note that this security researcher notified Zoom of the exploit and they were in no rush to repair it. Look at the timeline in the Medium post. They only sought to fix it after the vulnerability drew media attention. <o:p></o:p></p></div><div><p class=MsoNormal><o:p> </o:p></p></div><div><p class=MsoNormal>Adobe Connect was not perfect but it met our needs and the occasional security issues that arose were promptly fixed by Adobe and never as serious as this one!<o:p></o:p></p></div><div><p class=MsoNormal><o:p> </o:p></p></div><div id="protonmail_mobile_signature_block"><div><p class=MsoNormal>Best wishes, Ayden<o:p></o:p></p></div></div><div><p class=MsoNormal><o:p> </o:p></p></div><p class=MsoNormal>On Tue, Jul 9, 2019 at 18:07, Adeel Sadiq <<a href="mailto:11beeasadiq@seecs.edu.pk">11beeasadiq@seecs.edu.pk</a>> wrote: <o:p></o:p></p><blockquote style='margin-top:5.0pt;margin-bottom:5.0pt'><div><p class=MsoNormal>Speaking from a technical perspective, no software is perfect or bug-free. Its only a matter of time a loophole is found and exploited and eventually patched up. If you think Adobe Connect or ezTalks were/are free of these architectural issues, think again! That's the way we technical community do things. <o:p></o:p></p><div><p class=MsoNormal><o:p> </o:p></p></div><div><p class=MsoNormal>Regards<o:p></o:p></p></div><div><p class=MsoNormal><o:p> </o:p></p></div><div><p class=MsoNormal>Adeel<o:p></o:p></p></div><div><p class=MsoNormal>Pakistan<o:p></o:p></p></div></div><p class=MsoNormal><o:p> </o:p></p><div><div><p class=MsoNormal>On Wed, Jul 10, 2019 at 1:37 AM Ayden Férdeline <<a href="mailto:icann@ferdeline.com">icann@ferdeline.com</a>> wrote:<o:p></o:p></p></div><blockquote style='border:none;border-left:solid #CCCCCC 1.0pt;padding:0in 0in 0in 6.0pt;margin-left:4.8pt;margin-top:5.0pt;margin-right:0in;margin-bottom:5.0pt'><div><p class=MsoNormal>Unfortunately, uninstalling the application does not rectify the situation, due to poor architecture (acknowledged by Zoom on their blog today). They are working on a fix, now that public scrutiny demands one. So disappointing that ICANN has put us in this terrible situation. <o:p></o:p></p></div><div><p class=MsoNormal><o:p> </o:p></p></div><div id="gmail-m_4892314735287444777protonmail_mobile_signature_block"><div><p class=MsoNormal>Ayden<o:p></o:p></p></div></div><div><p class=MsoNormal><o:p> </o:p></p></div><div><p class=MsoNormal><o:p> </o:p></p></div><p class=MsoNormal>On Tue, Jul 9, 2019 at 16:15, Vaibhav Aggarwal, Catalyst & Group CEO <<a href="mailto:va@BLADEBRAINS.COM">va@BLADEBRAINS.COM</a>> wrote: <o:p></o:p></p><blockquote style='margin-top:5.0pt;margin-bottom:5.0pt'><p class=MsoNormal>Thanks for this. Till the next Update, I have removed the Zoom For Mac Client with immediate effect. <o:p></o:p></p><div><p class=MsoNormal><o:p> </o:p></p></div><div><p class=MsoNormal>Regards,<o:p></o:p></p></div><div><p class=MsoNormal>Vaibhav Aggarwal<o:p></o:p></p></div><div><p class=MsoNormal>New Delhi<o:p></o:p></p></div><div><p class=MsoNormal><a href="http://VaibhavAggarwal.com">VaibhavAggarwal.com</a> <o:p></o:p></p></div><div><p class=MsoNormal><o:p> </o:p></p><div><p class=MsoNormal style='margin-bottom:12.0pt'><o:p> </o:p></p><blockquote style='margin-top:5.0pt;margin-bottom:5.0pt'><div><p class=MsoNormal>On Jul 10, 2019, at 12:30 AM, Michael Karanicolas <<a href="mailto:mkaranicolas@GMAIL.COM">mkaranicolas@GMAIL.COM</a>> wrote:<o:p></o:p></p></div><p class=MsoNormal><o:p> </o:p></p><div><div><p class=MsoNormal>Hey - remember when ICANN switched everyone from Adobe over to Zoom as a way of enhancing information security and data privacy? <o:p></o:p></p><div><p class=MsoNormal><o:p> </o:p></p></div><div><p class=MsoNormal>"A vulnerability in the Mac Zoom Client allows any malicious website to enable your camera without your permission... This vulnerability allows any website to forcibly join a user to a Zoom call, with their video camera activated, without the user's permission. On top of this, this vulnerability would have allowed any webpage to DOS (Denial of Service) a Mac by repeatedly joining a user to an invalid call. Additionally, if you’ve ever installed the Zoom client and then uninstalled it, you still have a localhost web server on your machine that will happily re-install the Zoom client for you, without requiring any user interaction on your behalf besides visiting a webpage. This re-install ‘feature’ continues to work to this day."<o:p></o:p></p></div><div><p class=MsoNormal><o:p> </o:p></p></div><div><p class=MsoNormal>Read more here: <a href="https://medium.com/@jonathan.leitschuh/zoom-zero-day-4-million-webcams-maybe-an-rce-just-get-them-to-visit-your-website-ac75c83f4ef5">https://medium.com/@jonathan.leitschuh/zoom-zero-day-4-million-webcams-maybe-an-rce-just-get-them-to-visit-your-website-ac75c83f4ef5</a><o:p></o:p></p></div></div></div></blockquote></div><p class=MsoNormal><o:p> </o:p></p></div></blockquote><div><p class=MsoNormal><o:p> </o:p></p></div><div><p class=MsoNormal><o:p> </o:p></p></div></blockquote></div></blockquote><div><p class=MsoNormal><o:p> </o:p></p></div><div><p class=MsoNormal><o:p> </o:p></p></div></div></body></html>