MaxKey 4.1.12 DefaultRedirectResolver OAuth Authorization Code Theft
Default status is the baseline for the product, each version can override it (e.g. patched versions marked unaffected).
| Vendor | Product | Default status | Versions | |||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|
| dromara | MaxKey | unaffected |
|
No data.
No data.
| Vendor | Product | Versions | ||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Dromara | Maxkey |
|
No CVSS v3.0
No CVSS v2
This CVE is not in the KEV list.
Exploit prediction score: < 1% (0.565% probability within 30 days)
| Type | Values Removed | Values Added |
|---|---|---|
| First Time appeared |
Maxkey
Maxkey maxkey |
|
| CPEs | cpe:2.3:a:maxkey:maxkey:*:*:*:*:*:*:*:* | |
| Vendors & Products |
Maxkey
Maxkey maxkey |
| Type | Values Removed | Values Added |
|---|---|---|
| Metrics |
ssvc
|
| Type | Values Removed | Values Added |
|---|---|---|
| First Time appeared |
Dromara
Dromara maxkey |
|
| Vendors & Products |
Dromara
Dromara maxkey |
| Type | Values Removed | Values Added |
|---|---|---|
| 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. | |
| Title | MaxKey 4.1.12 DefaultRedirectResolver OAuth Authorization Code Theft | |
| Weaknesses | CWE-183 | |
| References |
| |
| Metrics |
cvssV3_1
|