Vulnerabilities Allow Hacking of Zimbra Webmail Servers With Single Email
Vulnerabilities in the Zimbra enterprise webmail solution could allow an attacker to gain unrestricted access to an organization’s sent and received email messages, software security firm SonarSource reveals.
A webmail solution popular among enterprises worldwide, Zimbra claims to have more than 200,000 business customers, including over 1,000 government and financial institutions and roughly 500 service providers.
In June, Zimbra released patches for multiple security issues in the webmail solution, including two bugs identified by Simon Scannell, a security researcher with SonarSource. The flaws could allow an unauthenticated attacker to compromise the webmail server of an organization and gain access to all employee email messages.
Tracked as CVE-2021-35208, the first of the vulnerabilities is a DOM-based stored cross-site scripting (XSS) bug that an attacker could trigger when the victim views an incoming email.
The second bug is CVE-2021-35209, an open redirect leading to server-side request forgery (SSRF). An attacker could chain the two vulnerabilities to extract tokens and credentials from “instances within the cloud infrastructure,” the SonarSource researcher says.
Zimbra sanitizes HTML content in incoming emails on the server side, using the OWASP Java-HTML-Sanitizer, which is the correct approach. However, Scannell discovered that it is this approach that allows for the first vulnerability to occur.
Specifically, he explains, Zimbra’s three mail clients (desktop, static HTML, and mobile-optimized clients) “may transform the trusted HTML of an email afterwards to display it in their unique way,” which could lead to corruption of the HTML, opening the door to XSS attacks.
The SSRF issue, on the other hand, was identified in the Webex integration that Zimbra supports, where a proxy forwards all HTTP request headers and parameters to URLs that match the *.webex.com pattern.
“SSRF attacks like the one described above can be mitigated by disallowing the HTTP request handler to follow redirects. It makes sense to validate the value of the Location header of the response and create a new request after it has been validated. This would also protect against Open Redirect vulnerabilities,” Scannell notes.
Both vulnerabilities were patched in late June with the release of Zimbra 9.0.0 P16 and 8.8.15 P23.