Forwarding information received from a host listed as a trusted proxy is not kept separate from Dovecot's own authentication fields, so a…
No exploitation in the wild has been reported. EPSS puts the chance of exploitation in the next 30 days at 0%. Fixed in 2.4.5, 2.3.22.2, 3.0.7 and 1 more.
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.
Affected
Vendors, products and packages with version ranges
| Vendor | Product | Versions | Fixed |
|---|---|---|---|
| Open-Xchange | >=2.3.4 <2.4.5, >=2.3.4 <2.3.22.2, >=3.0.0 <3.0.7, >=3.1.0 <3.1.6 | 2.4.5, 2.3.22.2, 3.0.7, 3.1.6 |
Timeline
Every event on this vulnerability
Embed
A live severity badge for an advisory, README or ticket