Skip to main content

Issues with Adobe Connect at ICANN61

I want to share a note I sent to the community earlier today regarding a security issue related to our use of Adobe Connect. Please see below for information regarding this issue.

"Yesterday we were notified by a member of the Security and Stability Advisory Committee of what appears to be a potentially serious security issue affecting our use of Adobe Connect.

In order to protect the members of the multistakeholder community, and out of an abundance of caution, we have suspended our Adobe Connect services. This means that Adobe Connect services will not be available for the rest of ICANN61.

Shortly after receiving this information, we mobilized a cross-functional team led by our Senior Vice President and Chief Information Officer, Ashwin Rangan, to begin an investigation into this matter. We contacted the support teams at Adobe. We also contacted our Adobe Connect cloud services vendor, and the issue has been escalated to their internal team. We are waiting to hear from them.

Concurrently, our team immediately began working to ensure alternative remote participation services are available at ICANN61.

This has not been an easy task. The team worked late into the night and I am pleased to report that some remote participation will continue to be available this week.

We will continue to have Livestream video, multilingual audio, and live scribe feeds in the main meeting rooms. Other rooms will be limited to listen-only audio bridges. Questions and comments from remote participants will also be accommodated via email as best we can.

I will keep you informed as our investigation continues."

 

Comments

    Gangadhar Panday  03:40 UTC on 14 March 2018

    Thanks for the prompt action and alternative measures.

    Timothy Kwadwo Asiedu  03:50 UTC on 15 March 2018

    Thank you for the prompt action.

    Askm  11:47 UTC on 19 March 2018

    Please could you let us know what version of Adobe Connect you are using ? thanks

    haliyikama  01:36 UTC on 20 April 2018

    Thank you for the prompt action.

Domain Name System
Internationalized Domain Name ,IDN,"IDNs are domain names that include characters used in the local representation of languages that are not written with the twenty-six letters of the basic Latin alphabet ""a-z"". An IDN can contain Latin letters with diacritical marks, as required by many European languages, or may consist of characters from non-Latin scripts such as Arabic or Chinese. Many languages also use other types of digits than the European ""0-9"". The basic Latin alphabet together with the European-Arabic digits are, for the purpose of domain names, termed ""ASCII characters"" (ASCII = American Standard Code for Information Interchange). These are also included in the broader range of ""Unicode characters"" that provides the basis for IDNs. The ""hostname rule"" requires that all domain names of the type under consideration here are stored in the DNS using only the ASCII characters listed above, with the one further addition of the hyphen ""-"". The Unicode form of an IDN therefore requires special encoding before it is entered into the DNS. The following terminology is used when distinguishing between these forms: A domain name consists of a series of ""labels"" (separated by ""dots""). The ASCII form of an IDN label is termed an ""A-label"". All operations defined in the DNS protocol use A-labels exclusively. The Unicode form, which a user expects to be displayed, is termed a ""U-label"". The difference may be illustrated with the Hindi word for ""test"" — परीका — appearing here as a U-label would (in the Devanagari script). A special form of ""ASCII compatible encoding"" (abbreviated ACE) is applied to this to produce the corresponding A-label: xn--11b5bs1di. A domain name that only includes ASCII letters, digits, and hyphens is termed an ""LDH label"". Although the definitions of A-labels and LDH-labels overlap, a name consisting exclusively of LDH labels, such as""icann.org"" is not an IDN."