Reporting Vulnerabilities to Zimbra

Revision as of 09:46, 23 December 2022 by Barry de Graaff (talk | contribs)

Reporting Vulnerabilities to Zimbra

As described in the Zimbra Responsible Disclosure Policy, it is critical that the Reporter please use the following techniques to report the vulnerability responsibly and securely via encrypted mechanisms. In order to fix and communicate the vulnerability safely to the greatest number of commercial and open-source sites, Zimbra seeks to build a partnership with its Researchers to identify, verify, patch and release software in such a way as to allow sites to be protected against a vulnerability prior to the release of public information on the vulnerability. In turn, when the Zimbra Responsible Disclosure Policy is followed by the Reporter, Zimbra will acknowledge the Reporter of the found vulnerability on the Zimbra Security Center.

Reporting Vulnerability Securely to Zimbra

The following methods are acceptable methods of reporting issues securely via encrypted mechanisms:

1. Email

Email can be used for reporting vulnerabilities, but the following steps must be followed:

  1. Reporter will notify that a vulnerability has been identified.
  2. Within seven business days of initial contact by the Reporter, Zimbra should promptly acknowledge, with a personal response rather than an automated message, that it has received the report and is requesting additional details.
  3. Reporter will email the additional details using an encrypted mechanism (see below).
  4. Zimbra will confirm the receipt of the details, and will verify and proceed with the vulnerability response, as defined in the Zimbra Responsible Disclosure Policy.

Our recommended approach for email is to encrypt the details using Zimbra Security's public PGP/GPG key:

Zimbra Security Public PGP/GPG key

The following details should be included in the encrypted email contents:

  • All technical information and related materials the Vendor would need to reproduce the issue.
  • Complete revision information, including his or her implementation’s current version or patch level, and a description of the technology’s environment (e.g. hardware, configuration, other applications installed, relevant details about the network topology, firewall rules, and anything else that may be of use).

2. Bugzilla

Vulnerabilities can also be added directly by Reporter to the Zimbra public Bugzilla system. If reporting via Bugzilla, please be sure that the bug is set to "Make bug visible only to reporter and Zimbra":

  1. File bug at (Reporter will need to create an account on that system if they do not already have one - creating an account can be performed via self-service)
  2. Select the correct product, Zimbra Collaboration ("ZCS") or Zimbra Desktop ("ZD")
  3. Select the Version and Component - as appropriate
  4. Select "Make bug visible only to reporter and Zimbra"
  5. Include reproduction details and/or exploit proof-of-concept
  6. Notify Zimbra via email at that the bug has been filed and provide the bug number.

3. Support Case

For Supported Customers/Partners, open a Support Case with Zimbra Support at or by sending email to support [at] zimbra [dot] com.

4. Coordinator

Reporter may report the issue directly to a responsible Coordinator, such as CERT However, Zimbra would prefer that the vulnerability is initially reported directly to Zimbra and provide us the first opportunity to verify and, if necessary, fix the vulnerability directly in a working partnership with the Reporter.

Try Zimbra

Try now Zimbra Collaboration without any cost with the 60-day free Trial.
Get it now »

Want to get involved?

You can contribute in the Community, in the Wiki, in the Code, or developing Zimlets.
Find out more. »

Looking for a Video?

Visit our YouTube Channel to keep posted about Webinars, technology news, Product overviews and more.
Go to the YouTube Channel »

Jump to: navigation, search