Tom Wolters

The issue allows information exposure in responses to mail-gateway REST API calls. This is due to excessive data output by the application when authenticated users search for transactions in the transaction query builder. Exploitation of this issue may allow a remote attacker to gain unauthorized access to confidential information.

The issue allows Information Disclosure via fake or spoofed RT email headers in an email message or a mail-gateway REST API call. This is due to insufficient cleaning of user-provided data when processing email headers. Exploitation of the issue may allow a remote attacker to execute arbitrary HTML code by sending a specially crafted email message.

The issue allows an unauthenticated user to retrieve sensitive information, including password hashes and SNMP community strings.

The issue allows an attacker to perform system commands under the context of the web application. By default, the web server runs as the root user, which can be exploited.

The issue is related to the leakage of sensitive cookie values, including session cookies, to Sentry when using the Django integration of the Sentry SDK in a specific configuration. This can occur when the Sentry SDK configuration has `sendDefaultPII` set to `True`, a custom name is used for either `SESSION COOKIE NAME` or `CSRF COOKIE NAME` in Django settings, and data scrubbing features are not configured to account for the custom cookie names. The leaked cookies could be used by someone with access to Sentry issues to impersonate or escalate privileges within the application.