Open-Xchange GmbH OX Dovecot Pro
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 versions and mitigation
From the CVE record and the vendor's references.Affected
- >= 2.3.13, < 2.3.22.2
- >= 3.0.0, < 3.0.7
- >= 3.1.0, < 3.1.6
Fixed in 2.3.22.2, 3.0.7, 3.1.6
- >= 2.3.13, < 2.4.5
Fixed in 2.4.5
Mitigation
Upgrade OX Dovecot Pro to 2.3.22.2 or 3.0.7 or 3.1.6 or later.
Upgrade OX Dovecot CE to 2.4.5 or later.
References
Timeline
Days relative to CVE publicationNo public PoC found yet; not in CISA KEV.
PoC repositories
Found on GitHub.No PoC repositories found yet.