OX Dovecot Pro vulnerabilities
13 known vulnerabilities in OX Dovecot Pro from Open-Xchange. 13 are rated high or critical. Each entry lists the affected versions and the release that fixes it, where the vendor has published one.
Latest first
- 7.4 High severity
OX Dovecot Pro: Improper Authentication
An attacker that holds a token intended for a different purpose can authenticate, because when an OAuth2 token response does not contain a scope claim, the audience claim is used in its place and checked against the configured required scopes. These are differ
- 7.5 High severity
OX Dovecot Pro: Uncontrolled Resource Consumption
An unauthenticated attacker can send an IMAP ID command with a very large number of parameters before logging in, which causes memory and CPU usage to grow disproportionately. The login process can be terminated by the out-of-memory handling, which also termin
- 9.1 Critical severity
OX Dovecot Pro: Use After Free
An attacker that has valid credentials can use a Sieve script with the editheader extension to trigger a use-after-free in the mail editing code, and to write memory contents beyond the intended buffer into the delivered mail. This causes memory leak and oppor
- 7.5 High severity
OX Dovecot Pro: Uncontrolled Resource Consumption
An unauthenticated attacker can crash the ManageSieve login process by sending a small malformed command before authenticating. If running in high-security mode (default for community releases), only the attacker's own connection is terminated. If running in h
- 7.5 High severity
OX Dovecot Pro: Uncontrolled Resource Consumption
An attacker that can send mail to a user can craft a message whose headers contain a very large number of email addresses or MIME parameters, which causes excessive memory usage when the message is later parsed. The message is still delivered, but reading it o
- 9.1 Critical severity
OX Dovecot Pro: Improper Handling of Extra Parameters
When safe filter is used with variable expansion, all following pipelines on the same string are incorrectly interpreted as safe too, enabling unsafe data to be unescaped. This can enable SQL / LDAP injection attacks when used in authentication. Avoid using sa
- 7.5 High severity
OX Dovecot Pro: Uncontrolled Resource Consumption
Attacker can send a specifically crafted message before authentication that causes managesieve to allocate large amount of memory. Attacker can force managesieve-login to be unavailable by repeatedly crashing the process. Protect access to managesieve protocol
- 7.5 High severity
OX Dovecot Pro: Uncontrolled Resource Consumption
Sending "NOOP (((...)))" command with 4000 parenthesis open+close results in ~1MB extra memory usage. Longer commands will result in client disconnection. This 1 MB can be left allocated for longer time periods by not sending the command ending LF. So attacker
- 8.2 High severity
OX Dovecot Pro: Improper Neutralization of Special Elements used in an SQL Command
Dovecot SQL based authentication can be bypassed when auth_username_chars is cleared by admin. This vulnerability allows bypassing authentication for any user and user enumeration. Do not clear auth_username_chars. If this is not possible, install latest fixed
- 7.5 High severity
ManageSieve AUTHENTICATE command crashes when using literal as SASL initial response.
ManageSieve AUTHENTICATE command crashes when using literal as SASL initial response. This can be used to crash ManageSieve service repeatedly, making it unavailable for other users. Control access to ManageSieve port, or disable the service if it's not needed
- 7.5 High severity
When sending invalid base64 SASL data, login process is disconnected from the auth server…
When sending invalid base64 SASL data, login process is disconnected from the auth server, causing all active authentication sessions to fail. Invalid BASE64 data can be used to DoS a vulnerable server to break concurrent logins. Install fixed version or disab
- 7.4 High severity
OX Dovecot Pro: Improper Preservation of Consistency Between Independent Representations of Shared State
When cache is enabled, some passdb/userdb drivers incorrectly cache all users with same cache key, causing wrong cached information to be used for these users. After cached login, all subsequent logins are for same user. Install fixed version or disable cachin
- 7.5 High severity
OX Dovecot Pro: Allocation of Resources Without Limits or Throttling
Very large headers can cause resource exhaustion when parsing message. The message-parser normally reads reasonably sized chunks of the message. However, when it feeds them to message-header-parser, it starts building up "full_value" buffer out of the smaller