Executive Summary

This vulnerability is a reflected cross-site scripting (XSS) issue in MailEnable versions prior to 10.54. It occurs in the AddressesBcc parameter of the /Mondo/lang/sys/Forms/AddressBook.aspx page. The parameter is not properly sanitized when processed via a GET request and is reflected inside a <script> block in a JavaScript variable. An attacker can craft a payload that breaks the existing JavaScript function, injects malicious script, and causes it to execute in the victim's browser when they try to send an email. This allows the attacker to run arbitrary JavaScript code on the victim's browser.

Useful 0 Not Useful 0

Impact Analysis

Exploitation of this vulnerability can allow an attacker to redirect victims to malicious websites, steal non-HttpOnly cookies, and perform actions on behalf of the authenticated user. This can lead to account compromise, data theft, and unauthorized actions within the affected MailEnable environment.

Useful 0 Not Useful 0

Detection Guidance

To detect this vulnerability, you can test the /Mondo/lang/sys/Forms/AddressBook.aspx endpoint by sending a crafted GET request with the AddressesBcc parameter containing a payload that attempts to inject JavaScript code. For example, using curl: curl -v "http://<mailenable-server>/Mondo/lang/sys/Forms/AddressBook.aspx?AddressesBcc=<script>alert(1)</script>" and observe if the response reflects the script unsanitized within the JavaScript variable var sAddrBcc. If the script is reflected and executed in a browser, the vulnerability exists. Additionally, monitoring HTTP traffic for suspicious GET requests with unusual AddressesBcc parameter values may help detect exploitation attempts. [2]

Useful 0 Not Useful 0

Mitigation Strategies

Immediate mitigation steps include upgrading MailEnable to version 10.54 or later, where this vulnerability has been addressed. If upgrading is not immediately possible, consider implementing web application firewall (WAF) rules to block or sanitize requests containing suspicious payloads in the AddressesBcc parameter. Additionally, educate users to be cautious of unexpected redirects or unusual behavior when sending emails, and monitor logs for exploitation attempts. [2, 3]

Useful 0 Not Useful 0