CyberRota Analysis
AI-GeneratedThe vulnerability arises from improper handling of OAuth2 token responses, where an attacker can exploit the absence of a scope claim, allowing unauthorized access if the audience claim matches a configured scope name. This misconfiguration can lead to significant security risks, as it permits tokens with no relevant permissions to be accepted, potentially exposing sensitive resources. Organizations using Dovecot should prioritize addressing this issue by ensuring that their identity providers issue proper scope claims and by updating to a non-vulnerable version.
Public Exploit Signal
A public exploit, PoC, GitHub repository or Metasploit reference was detected for this CVE.
Note: these links are listed for security research and verification purposes only.
Original NVD Description
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.