CyberRota Analysis
AI-GeneratedThe vulnerability affects MaxKey versions up to 4.1.12, specifically in the DefaultRedirectResolver.hostMatches() function, which fails to properly validate redirect URIs. This allows remote attackers to hijack OAuth 2.0 authorization codes by exploiting crafted redirect URIs, potentially leading to unauthorized access to victims' identities. Organizations using affected versions of MaxKey, particularly those implementing OAuth 2.0 for authentication, should prioritize remediation to mitigate the risk of identity theft and unauthorized access.
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
MaxKey through 4.1.12, fixed in commit ddbb72f, contains an insufficient redirect URI validation vulnerability in DefaultRedirectResolver.hostMatches() that allows remote attackers to hijack OAuth 2.0 authorization codes by supplying a crafted redirect_uri whose hostname suffix matches a registered URI without proper dot-boundary anchoring. Attackers who control a domain ending with the registered redirect URI hostname can social-engineer victims into clicking a crafted authorization URL, causing the authorization code to be issued to the attacker-controlled URI and exchanged for an access token granting access to the victim's identity.