4.3
Moyenne
CVE-2026-42008 Forwarding information received from a host listed as a trusted proxy is not kept separate from Dovecot's own…
Description
Forwarding information received from a host listed as a trusted proxy is not kept separate from Dovecot's own authentication fields, so a value sent by that host can be injected as an internal authentication field. Any host permitted to act as a trusted proxy can authenticate as any user without knowing that user's password. This affects deployments whose password database honours a field that permits authentication without a password. Deployments that do not configure trusted proxies are not affected. Restrict the list of trusted proxy networks to hosts that are fully under your control. Update to non-vulnerable version. No publicly available exploits are known.
Produits et versions touchés
| Produit | Versions touchées | Corrigé en |
|---|---|---|
| OX Dovecot Pro 3.1 | 3.1.0 → < 3.1.6 | 3.1.6 |
| OX Dovecot Pro 3.0 | 3.0.0 → < 3.0.7 | 3.0.7 |
| OX Dovecot Pro 2.3 | 2.3.4 → < 2.3.22.2 | 2.3.22.2 |
| OX Dovecot CE 2.3 | 2.3.4 → < 2.4.5 | 2.4.5 |
Références
- documentation.open-xchange.com documentation.open-xchange.com
Chronologie
- Publiée
- Dernière modification
Autres CVE de OX Dovecot Pro
Les 44 CVE de OX Dovecot Pro →
CVE-2026-73209
An attacker that has valid credentials can send crafted compressed data that causes the affected process to exhaust…
6.5
Moyenne
CVE-2026-73208
An attacker that holds a token intended for a different purpose can authenticate, because when an OAuth2 token…
7.4
Élevée
CVE-2026-52687
An attacker that has valid credentials can select a compression algorithm for the IMAP connection whose decompression…
6.5
Moyenne
CVE-2026-52681
Sieve CPU resource usage is tracked in the compiled script, so an attacker that has valid credentials can reset the…
3.1
Faible