Description (CNA)
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 different concepts, and the audience claim does not describe what a token is allowed to do. A token that grants no relevant permissions can be accepted because its intended recipient value happens to match a configured scope name, granting access that should have been denied. It also hides an identity provider misconfiguration where scopes are not being issued at all. Ensure the identity provider issues a scope claim for all tokens used with Dovecot, and that configured scope names do not match audience values. Update to non-vulnerable version. No publicly available exploits are known.
Affected (CNA)
| Vendor / product | Versions |
|---|---|
| Open-Xchange GmbH / OX Dovecot Pro | affected 2.3.13 before 2.3.22.2; affected 3.0.0 before 3.0.7; affected 3.1.0 before 3.1.6 |
| Open-Xchange GmbH / OX Dovecot CE | affected 2.3.13 before 2.4.5 |
CWE
CWE-287
References
- https://documentation.open-xchange.com/dovecot/security/advisories/csaf/2026/oxdc-adv-2026-0003.json
ADP enrichment
No English description supplied.
No references supplied.