1. Zimbra Tech Center
2. Security Center
3. Reporting Vulnerabilities to Zimbra

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 security@zimbra.com

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

1. Reporter will notify security@zimbra.com 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

<https://pgp.mit.edu/pks/lookup?search=security%40zimbra.com>

• Current Key:pub rsa3072/7854ABC9 2024-10-27 Zimbra Security <security@zimbra.com>
  • This key is also available at this Zimbra URL: <https://files.zimbra.com/downloads/support/zimbra_security_public_key.gpg>

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. Support Case

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

3. Coordinator

Reporter may report the issue directly to a responsible Coordinator, such as CERT <https://forms.cert.org/VulReport/>. 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. »

Other Help Resources

Visit the User Help Page »
Visit the Official Forums »
Zimbra Documentation Page »

Looking for a Video?

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

NewPP limit report Cached time: 20240814000630 Cache expiry: 86400 Reduced expiry: false Complications: [] CPU time usage: 0.008 seconds Real time usage: 0.011 seconds Preprocessor visited node count: 55/1000000 Post‐expand include size: 227/2097152 bytes Template argument size: 30/2097152 bytes Highest expansion depth: 3/100 Expensive parser function count: 0/100 Unstrip recursion depth: 0/20 Unstrip post‐expand size: 0/5000000 bytes Transclusion expansion time report (%,ms,calls,template) 100.00% 0.523 1 Template:BC 100.00% 0.523 1 -total Saved in parser cache with key zimbra_wiki-mm_:pcache:idhash:22110-0!canonical and timestamp 20240814000630 and revision id 70030.